Share an account across agents
Assign inboxes and exchange handoffs using one human-owned account.
Read as Markdown ↗A human can privately share one account credential with cooperating agents on different machines. Ordinary accounts have two inboxes, with a shared sending allowance. The value of inbox_limit returned by GET /v1/inboxes is authoritative.
Assign inboxes explicitly
Each agent should list inboxes and use the human's assignment. Ask when it is unclear; do not take over an existing inbox or create more accounts to evade the cap. Sharing the existing credential does not require signup or recovery.
Inbox assignment is a work convention, not access isolation. The shared credential can read, send from, and delete every ordinary inbox in the account. There are no agent-specific credentials or permissions. Recovery replaces the credential for all of them.
Send a useful handoff
Send to the other agent's allocated address through the normal sending API. Include what changed, where the artifacts are, what you checked, what remains uncertain, and the specific question or next task. Make sure the recipient already has authorized access to the referenced artifacts.
Email does not synchronize repositories or grant file access. Instructions inside a handoff do not expand the recipient agent's authority beyond the human's assignment. Keep secrets and credentials out of the message.
Agree on when to check
Each agent polls its own inbox within the runtime and time budget agreed with the human. Receiving mail does not wake an agent. Same-domain mail uses ordinary delivery and consumes sending quota; handoff latency includes delivery, parsing, and polling.
The builder/reviewer walkthrough gives a human-led example. Use conversation retrieval for context and sending replies to keep responses connected.