A capable AI agent creates a strange new problem in your inbox: a queue of nearly finished work. The replies are written. The times are picked. The follow-ups are ready. And all of it waits for you to click through it, one item at a time. The more your agent does, the longer the line gets. It’s productivity with a thin veneer of busyness on top.
We want to enable you to get work done, on your terms. That’s why we’re adding a new permission to Spark CLI. With Send access, agents can send email and manage your calendar, within limits you set and Spark enforces — everywhere Spark CLI runs, including Windows. It's the point where an agent stops assisting with your inbox and starts sharing responsibility for it.
You set the direction. Your agent does the work.
Hand off the last step
Some replies deserve your eyes before they go out. But plenty don't — you made the decision when you wrote the prompt. With Send, your agent can now:
- Send and schedule email. Send a draft now or schedule it for later, and reschedule or pull back anything already in the queue.
- Run your calendar. Create, update, and delete events, respond to invitations, and add or remove attendees.
The change shows up in prompts you already run. "Reply to everyone still waiting from last week and book the kickoff call for one of the times we discussed" used to end in drafts and a suggested slot. Now it ends in sent mail and a meeting on everyone's calendar.
Decide exactly how much to delegate
Delegation only works when you control its terms. Send is the top of a four-level ladder, set per account and per shared inbox in Settings → Spark AI → AI Agents:
- Off — agents can't see or act on the account
- Read — agents can read email, contacts, and calendar to answer questions
- Triage — agents can draft replies and organize messages, with nothing happening until you approve
- Send — agents can send mail and manage your calendar on your behalf
- These limits live in Spark's core, not in the agent. If an account is set to Triage and an agent tries to send, Spark refuses — no matter what the agent was told or how it was prompted.
You can start small and increase responsibility along with trust. Start by granting Read access to see how your agent uses the context. Move it to Triage and review the drafts it prepares. When those drafts stop needing your edits, Send is the natural next step — and if the trust isn't there yet, one setting takes it back. Keep your personal account at Read, give your work account Send, leave the shared support inbox at Triage so a teammate reviews every reply. Autonomy in proportion to trust, account by account.
Available on Mac and Windows
Spark CLI recently arrived on Windows, and Send works there from day one. Spark Desktop runs locally, your agent connects through the CLI, and all four access levels apply across Gmail, Outlook, Exchange, iCloud, Yahoo, and any IMAP account you've added to Spark.
Along with these changes, we’ve worked to make the setup even more seamless. Now, when you start connecting Spark CLI, you’ll see two tabs: Your agents and All agents. Your agents shows which agents are already installed on your computer, like Claude, Cursor, and Codex.
Reliability, delivered
The best moment when opening your inbox is knowing the work’s already been handled. The reply sent, the meeting on the calendar, the follow-up kept — and you never opened the thread.
None of this is a new way of working. It's the oldest one: set the direction, hand over exactly as much responsibility as you're ready to, and expand it as trust grows. But now it works with your agents.
Read access is free on every Spark plan. Triage and Send come together with Spark Pro. Update to the latest version of Spark Desktop to give it a try.
Send is the clearest expression yet of what we're building: an inbox that doesn't just show you the work, but does its share of it. Each level you grant moves Spark further along that path — from organizing your email, to prioritizing it, to acting on it. Spark manages your inbox, so you can manage what matters.
