Email

Email is where the platform's inbound work becomes tractable: a full mail cockpit for your own accounts, a triage queue that survives between sessions, and an agent that reads the queue, researches answers, and drafts replies — all under a rule that never bends. Nothing addressed to another human is sent without your approval.

The view sits in the sidebar under Mission Control, below Calendar. Both carry scheduled and queued outbound work.

Accounts

Command Center speaks plain IMAP and SMTP, so it works with any provider that does — there is no integration to buy and no mailbox to migrate. You can configure several accounts and pick a default.

Account setup lives at Settings ▸ Email, which is the single place accounts are created and edited; this view only reads them. Passwords are never stored in your configuration file: each account names the environment variable that holds its password, and an account whose password does not resolve is treated as disabled rather than failing mid-send.

The four tabs

Mail — the working cockpit: folder list, message list, reading pane, with compose, reply, forward, the usual message actions (move, delete, mark read or unread), and attachment download. This is ordinary mail work, in the same window as everything else you operate.

Queue — the shared triage queue. The inbox watcher and the email agent both write rows here; you triage them by status, classification and notes. Classification is deliberately free text rather than a fixed list, and the filter offers whatever classifications actually exist in your queue instead of a guessed set.

Agent — the dispatch surface for the email agent. Run it on demand or on a cadence, watch queued and running state live, and read the last run's summary. Its Drafts awaiting approval card is the human gate made concrete: each draft the agent produced opens in the composer, addressed and pre-filled, for you to edit, send, or discard. It also carries a checklist of the identity files the agent writes from — a draft is only as good as the company identity behind it.

Email Reports — the run reports, grouped by day, with outcome chips (drafts, errors, empty runs), search across both filenames and report bodies, and a per-run drill-down that joins the drafts that run produced.

The monitor

The inbound watcher is the control in the top-right of the tab bar: the switch is in the bar itself, and clicking it reveals status — whether it is running, the poll interval, the last error if any. It polls your mailbox and files new mail into the queue so triage work accumulates while you are elsewhere instead of restarting from an inbox scan each session. It runs no model and costs nothing to leave on.

Where the human gate sits

Every outbound path in this view ends at you:

• The agent drafts; it does not send. Approval happens in the composer, per message.
• Scheduled sends you compose yourself are visible on the Calendar and can be cancelled before they go.
• The agent-facing mail tools mirror this split — an agent can read, search, triage and save drafts, but the send action is a decision you make in the app.

This is the same unconditional gate the operator model describes, and scheduling, automation, and agent dispatch all inherit it.

Where to go next

• email server — the same mailbox surface as agent tools
• Calendar — scheduling a message to send later
• Company Identity — the files the email agent writes from
• Routines & automation — running the agent on a cadence