Skip to content
nofeb

Product / Human inbox

A real inbox for the humans in the loop

Agents do the routine work; people handle the exceptions. The webmail puts both on the same mailbox, so a person can see what an agent did, approve what it wants to send, and take a thread over without copying it anywhere.

What the webmail is for

  • Activity timeline. What each agent did on a thread, in order: replies, metadata changes, held sends, decisions and handovers, each with who did it.
  • Approval queue. Sends held by an inbox's policy, with the message as written, the reasons it was held, recipients new to the conversation marked, and approve or reject in one click.
  • Driver lock. A per-thread handover: a person takes the wheel, the agent's sends on that thread are held or refused, and the person hands it back when done.
  • Metadata panel. The thread's working state (stage, owner, follow-up time, decisions) visible and editable beside the mail, validated against the declared types.
  • Drafts in the loop. An agent writes the draft, a person edits and sends it.
  • Calendar. The inbox's calendar beside its mail, including the invitations an agent answered.

Built on an open protocol

The webmail talks JMAP to the same engine the API uses, so anything it can do, a JMAP client or your own code can do too. There is no private back door for the first-party app: it signs in with OAuth like any other client, and people sign in to it through the same accounts as the console, with single sign-on where the organization requires it.

It opens with hosted access, like the API. Everything it does is also reachable through the API, MCP and JMAP.

Approve from wherever people already are

Every held send can be approved or rejected over the API or MCP, by a key holding the send:approve scope that agents never hold. The approval queue lists each one with the inbox, thread, subject, a preview, every recipient marked if they are new to the conversation, the reasons it was held and who submitted it.

Approvers can also decide outside nofeb. A Slack approver posts each held send with Approve and Reject buttons, verifies every click with your Slack app's signing secret, can be limited to named people, and updates the message in place. An email approver receives a signed, single-use link that expires; the page it opens decides only when the person clicks, so link scanners cannot approve.

The approval queue, and a Slack approver
GET /v1/sends?status=held&inbox_id=inb_...

POST /v1/approvers
{ "kind": "slack", "scope": "inbox", "inbox_id": "inb_...",
  "webhook_url": "https://hooks.slack.com/services/...",
  "signing_secret": "...", "allowed_user_ids": ["U024BE7LH"] }

Take a thread over

A person sets themselves as the driver of a thread, with a note for the agent. Until they hand it back, the agent's sends on that thread are held for approval or refused, whichever the person chose, and thread.driver_changed tells every agent watching. The same lock works from the API, MCP, JMAP and the webmail.

Take over, then hand back
POST /v1/threads/{thread_id}/driver
{ "driver": "human", "agent_sends": "hold", "note": "I'll handle pricing" }

POST /v1/threads/{thread_id}/driver
{ "driver": "agent" }

Drafts a person sends

Drafts are the path for draft_only inboxes. An agent creates and edits drafts over the API or MCP; they are ordinary messages in the Drafts folder, so a person sees the same draft in the webmail, a JMAP client or an IMAP client. On a draft_only inbox only a person, or a key with the send:approve scope, can send one, and sending it is the approval.

Bring a person's own mail to their agent

A forwarding address gives each person a private address that delivers their own mail into their agent's inbox byte for byte, with the original sender and signatures intact. It accepts only mail traceable to the senders that person forwards from, so a stranger who learns the address cannot use it. Gmail and Outlook send a confirmation before they forward; nofeb recognises it and surfaces the code and link on the address and as a forward.confirmation event, so the agent can finish the setup. Rotate or revoke an address at any time.

A forwarding address for one person
POST /v1/inboxes/{inbox_id}/forwarding-addresses
{ "person_email": "ana@example.com", "label": "Ana" }

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
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
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
Approvals in Slack and by email link Approve or reject a held send from a Slack message with Approve and Reject buttons, or from a signed, single-use, expiring link in an email. Slack requests are verified with your app's signing secret and can be limited to named people; the email link decides only on an explicit click, so link scanners cannot approve. Shipped
Take a thread over from the agent A person takes a thread over; until they hand it back, the agent's sends on that thread are held for approval or refused, and an event records who is driving. Works over the API, MCP, JMAP and the webmail. 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
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
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
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
SSO and SCIM Single sign-on to the console and the webmail with OIDC (Google Workspace, Microsoft Entra ID, Okta or any issuer) or SAML 2.0, verified domains that route sign-in to your identity provider, optional just-in-time accounts and an enforce switch, and SCIM 2.0 provisioning with group-to-role mapping. Deprovisioning ends the person's sessions and disconnects their apps. Included on plans whose row says SSO. Shipped
Byte-exact raw messages Download any stored message exactly as it was received. Shipped