Agent Inbox

AI agents can call tools and APIs but often need to reach actual people, for things like one-time codes, approvals, verification links, or follow-up questions, across whatever channel that person uses, email, Slack, or Telegram. Without a shared system, an agent would need separate integrations for each channel and would lose track of a conversation if a person switched from email to Slack mid-thread. The page frames this as a gap for browser agents doing sign-ups, personal assistant agents coordinating with people, agents working as teammates with humans, product agents handling many users, and support agents answering across channels.

Agent Inbox is a CLI (and MCP server) that gives an agent one inbox backed by an email address, and optional Telegram and Slack connections, all unified into a single thread regardless of which channel a reply comes in on. Commands include agentinbox setup to create the inbox, agentinbox send to start a new message (optionally via a specific channel), agentinbox reply to answer within an existing conversation, agentinbox list to see what arrived, and agentinbox contact invite/list to manage the people the agent communicates with. Flags let a caller attribute a message to a bot name, set a time-to-live or timeout on how long a request stays answerable, run async instead of blocking, or request structured JSON output. It lists integration guides for hosts such as Claude Code, Codex, OpenCode, Cursor, Hermes, OpenClaw, Claude, ChatGPT, and Grok Bot, and is built by Novu and described as open source.