# AI email triage

> The time goes into deciding, not reading. That is the part worth automating.

Most of what an inbox costs you is not reading messages. It is the loop around them: opening a thread to find out whether it matters, deciding it does not, closing it, and doing that again a hundred times before you reach the four that needed you. Triage is the act of collapsing that loop. This page is about what an AI agent can actually take off you there, and what it cannot.

## Where the time actually goes

Each row is a step of the manual loop and what replaces it when your agent can reach the mailbox directly. No step here is hypothetical - each maps to a tool the server exposes.

| Doing it by hand | With DaySurface |
| --- | --- |
| Open each unread thread to work out whether it needs you. | The inbox arrives ranked, as an interactive dashboard inside the chat. You are reading a shortlist rather than a list. |
| Re-read a long thread to reconstruct what was agreed. | The agent reads the full thread server-side and answers questions about it, so you never load the whole history to find one commitment. |
| Switch to the mail client to write a reply, then switch back. | Replies open in an editable composer in the conversation. You correct the draft in place and send from there. |
| Download a PDF attachment, fill it in another app, re-attach it. | Forms are filled from the thread itself. Signing stays yours - the tool will not type a signature for you. |
| Search for the thread you half-remember, by guessing keywords. | Search runs across your mail server-side and returns threads, so the agent works from your actual inbox rather than what fits in its context. |

## Why most 'AI for email' tools do not help

### 1. They summarise instead of deciding
A summary of forty threads is still forty things to read. The saving only appears when something ranks them and you can act on the top of the list without opening the rest.

### 2. They hand the model raw JSON
Most Gmail MCP servers return API payloads and stop. The model then narrates them back at you, which adds a step rather than removing one. An interactive surface you can act in is what turns a tool call into a decision.

### 3. They act without showing you
Anything that sends on the model's judgement alone buys speed with risk you did not agree to. A draft you approve is slower per message and far cheaper the first time the model is wrong.

### 4. They live outside the place you are already working
A separate triage app is another context switch, which is the cost you were trying to remove. Running inside the assistant you already have open is the point.

## What we are not going to tell you

We are not going to put a number on this. We have not run a time study, and any figure we published would be a guess dressed as evidence. What the page above describes is mechanical and checkable: these are the steps the software removes, and you know better than we do what those steps currently cost you. If you want the honest version of the pitch, it is that triage is where agents are genuinely good, and reading your mail for you is not the same as deciding what deserves you.

## Questions

### How much time will this actually save me?
We do not know, and we are not going to invent a figure. It depends on how much mail you get and how much of it needs you. What we can say precisely is which steps come out of the loop - they are listed above - so you can weigh that against your own week.

### Does it send email on my behalf without asking?
No. Replies open in a composer you edit and send yourself. The design assumption is that an agent will occasionally be wrong about tone, recipient or timing, and that a draft you approve costs far less than a send you have to retract.

### Which assistant does this run in?
Any MCP client. Claude and ChatGPT have their own setup guides, and the install picker covers Cursor, VS Code, Goose, Claude Code, Cline, Zed and Windsurf.

### What does it need access to?
The Google scopes you approve at sign-in, and nothing else. You review them on the consent screen and can revoke them from your Google account afterwards.

### Can I self-host it?
Yes. It is MIT-licensed, and the same tools are exposed over a CLI and a plain HTTP API as well as MCP, so you can point a client at your own deployment.

## More

- Connect Gmail to Claude: https://daysurface.com/connect-gmail-to-claude.md
- Connect Gmail to ChatGPT: https://daysurface.com/connect-gmail-to-chatgpt.md
- Connect Gmail to VS Code: https://daysurface.com/connect-gmail-to-vscode.md
- Connect Gmail to Goose: https://daysurface.com/connect-gmail-to-goose.md
- Connect Gmail to Cursor: https://daysurface.com/connect-gmail-to-cursor.md
- Connect Gmail to Microsoft 365 Copilot: https://daysurface.com/connect-gmail-to-microsoft-365-copilot.md
- Gmail MCP alternatives: https://daysurface.com/compare.md
- Get connected: https://daysurface.com/connect.md
- Full description for LLMs: https://daysurface.com/llms-full.txt