# Glassmail on Mac: What Local AI Does and What Connected Agents Can Read

Understand Glassmail's on-device assistant, the shared mailbox boundary for connected AI apps, and a safer first test.

By Paras Madan | 2026-11-22


If you keep client and personal email in one Mac app, a workspace switch can make them look separate without separating what a connected AI tool can read. Glassmail's maker answered that exact question at launch. A connected work agent does not automatically lose access to personal mail just because you are looking at a work workspace.

That matters more than the headline about local AI. Glassmail's built-in assistant and an external assistant connected to the mailbox are two different ways of handling the same message.

## Start with the built-in assistant

In the [maker's launch post and replies](https://www.producthunt.com/products/glassmail), Glassmail is described as a native Mac email client for Gmail, iCloud, Outlook and other supported mail providers. The maker says the app connects directly to the provider and runs its own AI on the Mac, using Apple Intelligence or a downloaded model. It can summarize a thread and draft a reply.

If those are the only two things you want, I would start there and leave external agents unconnected. Use an ordinary test conversation with a date, a question and an unresolved decision. Ask for a summary, then check whether it preserves what is undecided. For a reply draft, verify the recipient, date and any commitment yourself rather than evaluating it only on tone.

## Hide whole accounts before trying an external agent

The maker says Claude, Codex and other connected AI apps can search and read mail through Glassmail. They see the same eligible mail: the current workspace does not scope them, and there is no separate mailbox selection for each AI app. In **Settings > Agents > Hide from agents**, you can exclude an account from all connected agents. The maker says its messages then do not appear in searches, threads or counts.

If you need the work assistant to see work mail but not personal messages, hide the personal account before connecting an agent. If you need two different assistants to have different mailbox access, the control described at launch does not give you that split. I would also avoid relying on it to separate two clients whose messages are in the same account.

## Test reading and changes separately

Start with two non-sensitive test messages, one in the account you want an agent to see and one in an account you hide. Give each a distinctive subject line. Ask the connected agent to locate the visible message, then ask it to find the hidden one. A positive result for the first message and no result for the second gives you a practical check of that setup. It is not an independent audit of the product.

The maker says an external agent can request changes such as archiving or saving a draft, with approval, but cannot send or delete mail. That action boundary does not make read access harmless. If an external AI client handles retrieved text through a hosted model, do not assume the text stays on your Mac because Glassmail's built-in summarizer runs locally. Check the external client's data handling and your organization's rules before connecting it to real mail.

## Decide which workflow you actually need

Use the built-in assistant if all you want is a summary or a draft alongside your inbox. Consider the external connection only if another tool genuinely needs mail context, and only after checking which accounts it can reach. If different clients need different access, keep them disconnected rather than treating the workspace switch as a permission setting.

I'm Paras. I work across AI, engineering and distribution.

I help technical teams write setup guides that make a product's trade-offs clear before rollout.

[Book a 30-minute call](https://cal.com/paras-madan/30min).
