Gmail in Aino Desktop

Aino Desktop brings local Markdown notes, tasks and an optional mail application into one workspace. The mail application can connect to Gmail, show your inbox and attachments, and let you reply while keeping the original message visible.

Mail is an experimental feature and is disabled by default. From Desktop 1.4.30-beta.1, Gmail connects using your own Desktop OAuth client by default, with an option to reuse your calendar client. Shared Aino Google sign-in remains disabled for public users while Gmail permission verification is pending.

Aino Desktop reading a sample email with an attachment

The sidebar groups all connected accounts. Read a message on the right, download an attachment you choose to keep, and use Reply to compose below the original message. Review the recipient, subject, message and attachments before confirming a send.

Connect Gmail

  1. In a supported build, enable the experimental mail application in settings.
  2. Open Mail, then Manage accounts at the bottom of the sidebar to reach settings.
  3. Choose the Gmail tab. Enter your own Google Desktop OAuth Client ID and Client Secret, or choose to reuse the client configured for your calendar. Then connect your account.
  4. Google explains the requested permissions. Authorize only the account you intend to connect; you can cancel without enabling mail.

Permissions and data

Aino requests gmail.readonly to read the inbox, message headers, message bodies and attachments, and gmail.send to send messages and replies that you confirm. It does not request permission to delete or modify Gmail messages.

Your desktop connects directly to Google. The mail application does not route your messages or Google authorization tokens through an Aino server. Credentials, drafts and sending records are encrypted using the operating system's secure storage and saved locally; reading and synchronization caches are temporary in-memory data. Aino does not use mail data for advertising or training general-purpose AI models.

Optional email AI

For Desktop 1.4.30-beta.1 and compatible clients, attaching an email does not send a model request. Before authorizing transmission in an app session, review the provider, model, endpoint and data categories, and confirm that training and optional data sharing are disabled for your API account. Aino cannot independently inspect your provider account settings.

Email conversations support only the official OpenAI and Anthropic commercial APIs, using your own API key on each device. CLI providers, custom gateways, tools and automatic background continuation are blocked for tracked email contexts. AI history is encrypted with an independent recovery key; save it separately and enter it again after restarting or on another device. Removing a mailbox does not delete existing AI conversations.

Older versions may use different providers and history formats. Upgrade compatible clients together. Records that already lost mail provenance cannot reliably be identified automatically. See the Privacy Policy for data categories, migration, retention and deletion limits.

Disconnect in mail settings to remove local credentials, drafts, sending records and caches. Disconnecting does not revoke the Google grant: you can also remove Aino in Google Account third-party connections.

Read the Privacy Policy and Terms of Service. For support or privacy questions, contact [email protected]. The screenshot uses fictional sample mail.

Explore Aino Desktop · Public downloads