Skip to content
nofeb

Solutions / Personal assistants

Email for personal and executive assistants

For builders of personal and executive assistant agents

An assistant needs an address of its own to act from, and a safe way to see the mail its person already gets.

The problem

Connecting an assistant straight to a person's own mailbox gives it everything, including the ability to send as them. Most people want the assistant to see some mail, prepare replies, and never send without asking.

How it runs on nofeb

  1. Give the assistant its own inbox, set to draft_only or send_with_approval, so nothing goes out without its person.
  2. Create a forwarding address for the person. They set their own mailbox to forward the mail they want handled; the address accepts it only from their own addresses, delivers it byte for byte with the original sender, and surfaces the forwarding-confirmation code so the agent can finish the setup itself.
  3. The inbox has a calendar. Invitations that arrive by email land on it, the assistant answers them, and it can find a free slot across its person's working hours and book a meeting that sends the invitations, each one under the inbox's autonomy tier like any other send.
  4. The assistant writes replies as drafts; the person edits and sends them from the webmail, or from any mail client.
  5. The person can read the assistant's inbox in the mail app they already use, over IMAP with an app password for that inbox, or with a JMAP client, and see drafts, flags and folders exactly as the agent left them.
  6. Keep what the assistant knows about each thread (who, what is owed, by when) as typed metadata, with follow_up_at for reminders.
  7. If the person lets the assistant send on its own, turn on AI disclosure so recipients see which messages an agent wrote. Mail the person sends from the webmail never carries it.

Where nofeb stops

  • nofeb does not act inside the person's own Gmail or Outlook mailbox; the assistant works on the mail forwarded to it.

Status of everything this relies on

CapabilityWhat it doesStatus
Unlimited inboxes Create as many inboxes as the work needs, with a generated or chosen address and an idempotent client reference. Shipped
safe_body for untrusted mail The message's new text with zero-width and direction-altering characters, hidden HTML and forgeable quoted history removed, wrapped in a provenance header that tells the model whose words these are. Shipped
Autonomy tiers enforced by the server Every inbox carries a sending policy, from read-only to autonomous, enforced on the server for every surface that sends, so switching from the API to MCP cannot bypass it. Shipped
Human approval of held sends A held send waits with status awaiting_approval until a human approves or rejects it; both steps emit events. The approval queue lists every held send with its recipients (each marked if new to the conversation), the reasons it was held and who submitted it. Approving needs the separate send:approve scope, which keys from agent self-signup never hold, so an agent cannot approve its own send. Shipped
Typed metadata on messages, threads and inboxes Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. Shipped
Forward to an agent Per-person forwarding addresses that bring someone's own mail into their agent's inbox byte for byte, accepting only mail traceable to the senders you allow. Gmail and Outlook forwarding-confirmation codes and links are recognised and surfaced, and each address can be rotated or revoked. Shipped
Drafts Agents write drafts that a person edits and sends, over the API, MCP, JMAP, IMAP and the webmail. It is the documented path for draft-only inboxes: sending a draft needs the approval permission agents do not hold. Shipped
Calendar per inbox A calendar on every inbox: events with recurrence and time zones, invitations, updates, cancellations and replies by email, auto-accept rules, free/busy, availability and booking that sends the invitations, MCP tools for scheduling, and CalDAV and JMAP Calendars for standard clients. Invitations an agent sends follow its inbox's autonomy tier. Shipped
IMAP and POP3 IMAP4rev2 (with IMAP4rev1 compatibility, IDLE, CONDSTORE and QRESYNC) and POP3 on every inbox, over TLS only, signed in with the inbox address and an API key or a revocable per-inbox app password. Shipped
JMAP JMAP Mail, submission, vacation responses and push, one account per inbox a key can see, sharing one change history with the API and IMAP, with extensions for typed metadata and approvals. A send over JMAP meets the same autonomy tiers as any other. Shipped
Webmail for the humans in the loop A full webmail and calendar on the same mailboxes the agents use, with an agent-activity timeline, the approval queue, a per-thread driver lock and a metadata panel, signed in through the same accounts as the console. It opens with hosted access. Shipped
AI-generated disclosure Per organization, pod or inbox, mail an agent sends carries AI-Generated and AI-Disclosure headers and an optional footer. Mail a person sends from the console or the webmail never does. Shipped