# Agent Inbox: give your AI agent a way to reach you > Agent Inbox is now available. Give your AI agent its own email address, Telegram bot and Slack app, set it up in one command, and connect it over CLI or MCP. Canonical: https://www.novu.co/changelog/agent-inbox-give-your-ai-agent-a-way-to-reach-you/ Markdown: https://www.novu.co/changelog/agent-inbox-give-your-ai-agent-a-way-to-reach-you.md Last updated: 2026-11-02T14:19:00.000Z Agent Inbox is now available. Give your AI agent its own email address, Telegram bot and Slack app, set it up in one command, and connect it over CLI or MCP. Published: 2026-11-02T14:19:00.000Z Give your agent its own name, email address and contact card, plus its own Telegram bot and Slack app, so it can reach people and people can reach it. Agent Inbox is now available. It works with the agent you already run, whether that's Claude Code, Codex, Cursor, ChatGPT, OpenClaw, Hermes, or anything that can run a CLI or connect to MCP. Your agent can ask a question, request an approval or offer a choice, then wait for the answer and carry on. People and services can write to it directly, so verification codes, receipts and replies reach the agent instead of your inbox. ## Create an inbox in one command Run the setup command, choose a name for your agent and pick its address. Availability is checked as you type, and `--agent-handle` sets the address up front in scripts. ```bash npx @agentinbox/cli setup ``` You don't need an account to start. The inbox receives email straight away and works as a free demo until you claim it with `login`. If setup stops partway, your inbox is kept, and running it again picks up where it left off. The email you sign up with on the dashboard counts as confirmed, so you're only asked to confirm the addresses that need it. ## Connect the agent you already run Onboarding gives each way to connect its own tab. It recognizes agents you've already connected, opens desktop apps when they're installed, and moves on by itself once the connection works. Claude, ChatGPT, Cursor and Hermes connect over MCP at `https://mcp.agentinbox.md`, with guided sign-in. Coding agents like Claude Code and Codex use the CLI, plus skills that teach them when to reach you and when to just ask in the chat. To use the same agent on another computer, connect it with a one-time code from the dashboard. ## Ask, approve and choose, then carry on Your agent can involve a person in four ways: ask a free-text question, request an approval, offer a choice of up to 10 options, or send an update that needs no reply. Conversation commands run directly, without an `inbox` group: ```bash npx @agentinbox/cli send approve "Deploy v2.4.1 to production?" --ttl 2h npx @agentinbox/cli send choose "Pick a rollout" --option canary --option blue-green npx @agentinbox/cli list --filter unread npx @agentinbox/cli reply conv_123 "Yes, it's live." ``` Every answer comes back with who gave it and when. Exit codes tell your script what happened (0 approved, 10 denied, 11 still waiting, 12 expired), so the same command can gate a deploy step in CI. You can rename the Approve and Deny buttons, add extra buttons, and add a subtitle and body to give the person context. `show`, `read` and `resolve` work the same way as the commands above. ## Start Claude Code when a message arrives Coding agents only read their inbox while someone is running them. Run `listen` in a project folder, and a message from you, or from a contact you choose, starts Claude Code there to handle the conversation and reply in it. ```bash npx @agentinbox/cli listen claude-code ``` You approve listening before it starts, and strangers' messages never start a run. Anything outside the project, like a command its settings don't allow or messaging someone else, asks you first on your phone. `listen` runs in the background and starts again after a restart. Check it with `listen status` and turn it off with `listen stop`. ## Reach the right person Questions go to you by default. Invite a teammate with a link, and they connect the channel they prefer. Then send a question with `--to` to reach them, or to several people at once, where the first valid answer wins. ## Reach people on Telegram and Slack Email works as soon as the inbox exists. Apps connected over MCP can add Telegram and Slack themselves, and setup links open the Agent Inbox connection page for your site, including custom and self-hosted addresses. Every agent gets a default avatar on Telegram and Slack, so it's recognizable from the first message. ## Decide who can reach your agent Choose whether anyone can write to your agent or only your contacts. Messages from people who aren't contacts are labelled as strangers. Your agent can reply to them but never message them first, and it treats what they write as information, never as instructions. You can pause the agent at any time: it stops reading and sending, and messages wait until you resume. ## Share your agent with a card Each agent and contact has a card with a scannable QR code that opens the public card, so people find every way to reach your agent in one place. Get started with the [Agent Inbox quickstart](), or run `npx @agentinbox/cli setup`.