m1guelpf/Exo
ProductivityA native macOS Gmail client written in Rust that connects directly to Gmail with your own OAuth client.
What it is
Exo is a macOS Gmail client written in Rust. It connects to Gmail directly rather than through third-party servers, and is meant to feel fast and native compared with Electron- or webview-based mail apps. It also requests Calendar and People API access, so the client covers mail, calendars and contacts.
The project is for macOS users who want a local desktop Gmail client and are willing to set up their own Google OAuth client for it. It is explicitly inspired by Superhuman and is very early-stage.
Quick start
- Download the
.dmgfrom the latest release and drag Exo into Applications. - In the Google Cloud console, create a project and enable the Gmail API, Google Calendar API and People API.
- Configure the app in Google Auth Platform: set branding in Branding, publish the app under Audience to avoid a 7-day sign-out, and create a Desktop app client in Clients.
- Download the client JSON and move it into place:
mkdir -p ~/Library/Application\ Support/Exo
mv ~/Downloads/client_secret_*.json ~/Library/Application\ Support/Exo/google-oauth-client.json
- Open Exo, sign in with Google, accept the unverified-app warning, and allow all requested permissions. Unticking any permission causes sign-in to fail.
To build from source you need Rust 1.98+, Xcode 27 and Ruby 4.0 with Bundler, then run bundle install, bundle exec fastlane build and open target/release/Exo.app see the build instructions. Tests run with cargo test --workspace against a mock Gmail server.
Constraints
- macOS only; the distribution format is a
.dmgand the build relies on Xcode and Fastlane. - The app requires OAuth access to Gmail, Calendar and People, including mail sending, filters and signatures, calendar management, contact and directory reading.
- You must supply and maintain your own Google Cloud project and OAuth client; Exo ships no shared credentials.
- Local builds are ad hoc signed, so macOS may ask for Keychain access after each rebuild; set
EXO_SIGN_IDENTITYto use a signing identity. - The author states the code was generated almost entirely by automated tools, mainly Claude Opus 5.5, and has not been reviewed by a human for correctness or security see the note.
- Licensed under MIT; bundled assets and ported code are documented in THIRD_PARTY_NOTICES.md.
HotRepo's take
Exo entered HotRepo's new-project list on 2026-11-22 in the Rust list, gaining 12 stars over roughly one hour (114 to 114 in the recorded window), with no daily all-language ranking yet. That is a very short observation window, so it supports only the fact of early interest, not a trend. The README's candid note about AI-generated, unreviewed code makes the project's stage and the accompanying trust questions the main things to weigh before using it for real mail.
Written by AI from the project's public information and HotRepo's records, updated . The project's own docs are the source of truth.