Works from a shell
Scripts, cron jobs and CI steps call the CLI and read the exit code.
If your agent can run a shell command or connect to an MCP server, it can have its own email address.
npx @agentinbox/cli setup email
Two ways in, and one inbox behind both.
Scripts, cron jobs and CI steps call the CLI and read the exit code.
Any client that supports remote MCP with OAuth sign-in connects to https://mcp.agentinbox.md.
Agents that read Agent Skills learn when to reach you and how to read the answer.
Set up with the CLI, then ask from code, or connect over MCP instead.
$ npm i -g @agentinbox/cliEverything your agent gets on Email.
From the exit code: 0 approved or answered, 10 denied, 11 the wait ran out with the question still open, 12 expired, 1 an error. Add --json for the full result.
Yes. Connect the CI job with a one-time code from agentinbox.md, or give it the INBOX_SECRET_KEY environment variable.
Any agent that follows the Agent Skills format, including Claude Code, Codex, OpenCode, Cursor, GitHub Copilot, Gemini CLI, Hermes and OpenClaw. Install them with npx skills add agentinboxhq/skills.
Free for 100 conversations a month. No credit card required.
npx @agentinbox/cli setup email
Asks you before it acts, and a message can start it
Checks in with you before it ships changes
Asks from the terminal, you answer from anywhere
Lets its agents ask you instead of guessing
Reports back from wherever it runs
Your personal assistant, reachable when you're away
Reaches people for you from the chat
Sends messages and gets answers from the chat
Asks you before it acts on your behalf