A developer email inbox per project.
None of it in your personal mailbox.
Create a receiving address for a project and point your services at it: uptime alerts, cron reports, backup results, the signup email your app just sent. Everything lands in AgentsRoom, next to the code it is about.
The address is made of the inbox name and a long secret, so nobody guesses it and you can replace it the day it leaks. Messages are shown as plain text, kept on the server, and readable from your desktop and your phone.
cron@billing-api06:00
Nightly invoicing report
412 invoices sent, 0 failed
Every service sends to the project address, every message lands in the same searchable inbox.
Every project ends up sending email somewhere. The uptime monitor, the backup script, the payment provider, the error tracker that only knows SMTP, the welcome email you need to check after each deploy. It usually all goes to your personal address, buried between newsletters, and you search for it the day something breaks.
The developer email inbox gives each project, or your whole account, its own receiving address. Paste it into any service that can send an email notification and the messages arrive in the Mail tab of AgentsRoom, sorted by inbox, separate from your real mailbox.
It is built for reading, not for writing: no sending, no replies, no HTML rendering, no tracking pixels. Just the sender, the subject and the text, stored on the server for 90 days and searchable from any of your devices.
An inbox made for machine email
What you need to read alerts and reports quickly, and nothing that turns it into a second mailbox to manage.
A dedicated address per inbox
Each inbox gets its own address, built from its name and a 48-character secret. Create one for your account or one per project.
Plain text, safe to open
Messages show the sender, the subject and the text. HTML is not rendered, remote tracking pixels are never loaded and attachments are ignored.
Search and read state
Search the history, open a message, and keep your own read state. Each teammate on a shared inbox has theirs.
Replace a leaked address
Regenerate the address and the old one stops accepting mail immediately. Revoke it to stop receiving altogether. Messages already received stay readable.
A JSON endpoint as a fallback
No SMTP in your tool? Post the same message with cURL: title, sender, body and link, with a send-only key in the Authorization header.
Shared only when you decide
Inboxes are private by default. In a Team or a Pro group, share one with the teammates you choose. Only the owner changes the settings.
An address to paste, or a request to send
Both are in the inbox settings, with your real values already filled in.
SMTP / POST /mailbilling-api-3f9c0a7e1b42d6c58e09f1a2b7d4c6e8a0f3b5d7c9e1a2b4@inbox.example.comcurl -X POST https://agentsroom.dev/api/dev-inboxes/INBOX_ID/mail \
-H 'Authorization: Bearer SENDING_KEY' \
-H 'Content-Type: application/json' \
-d '{"title":"Nightly report","sender":"cron@billing-api",
"body":"412 invoices sent, 0 failed"}'The address is a secret: anyone who has it can send to the inbox. Keep it out of public repositories and regenerate it if it ever appears somewhere it should not.
From zero to the first email
Three steps, no DNS to configure on your side.
Open Mail and create an inbox
In a project, click Mail in the project dock, or open it from the notification settings. Pick your account or the current project, and start from the Service report template if you like.
Copy the address
Connection & settings shows the receiving address and the JSON endpoint. Copy the address into your monitoring tool, your cron job, your test account or any service that sends email notifications.
Read it anywhere
New messages appear in the Mail tab on desktop and in the AgentsRoom mobile app. Search, open, mark as read, and delete what you no longer need.
Where a project address pays off
Anything that emails you about a project, rather than about you.
Service and uptime alerts
Monitoring tools, error trackers and status pages that can only notify by email get one address per project, so an outage is never lost among newsletters.
Check the emails your app sends
Sign up with the project address and confirm that the welcome, verification or password reset email actually leaves, with the right subject and text.
Cron and backup reports
Nightly jobs that end with an email report land in one place, with a history you can search when you need to know which night went wrong.
Third-party notices
Billing alerts, API deprecation notices and quota warnings from the services a project depends on, kept with that project.
Read-only by design
The inbox never sends and never replies, so it cannot be used to impersonate you. It only receives, and only at an address that contains a 192-bit secret.
Messages are displayed as plain text. HTML is not rendered, remote images and tracking pixels are not fetched, and attachments are dropped on arrival. Senders cannot tell whether you opened their email.
Treat incoming content as untrusted, including when an agent reads it for you: AgentsRoom gives it to agents as data, never as instructions.
Let your agent read the reports
dev_inboxes_listdev_inbox_createdev_inbox_configuredev_inbox_membersdev_inbox_messagesdev_inbox_testYour AI coding agents can list inboxes, create one for the project and read its messages with the AgentsRoom MCP tools, whatever their CLI. Ask "check this morning's backup report" and the agent reads it instead of you.
The agent asks before it changes a setting or shares an inbox, and it never writes the address into a public repository.
Discover AgentsRoom MCPMonthly email allowance
Counted per calendar month, across all your inboxes. Push has its own separate allowance.
Guest
10
per month
Free
100
per month
Plus
200
per month
Pro
500
per month
Team seats include Pro. Messages are kept for 90 days, and deleting one does not give back its email.
You need your phone to buzz when a script finishes, not just a message to read later? Send a push instead.
Push notification APIDeveloper email inbox: questions
What is a developer email inbox?
A receiving-only email address dedicated to a project or to your account. Services, scripts and test accounts send to it, and you read the messages in the Mail tab of AgentsRoom on desktop and mobile, apart from your personal mailbox.
Can I send emails or reply from it?
No. The inbox only receives developer notifications. It does not send, does not reply and does not replace your email account.
Are HTML and attachments displayed?
No. Messages are shown as plain text with the sender and the subject. HTML is not rendered, remote images and tracking pixels are not loaded, and attachments are ignored.
What does the address look like?
The inbox name followed by a 48-character secret, at the AgentsRoom receiving domain. Treat it like a password: anyone who has it can send to the inbox.
What if the address leaks?
Regenerate it in the inbox settings and the old address stops accepting mail immediately. Messages already received remain readable until you delete them or until their 90 days of retention end.
Can I post a message without sending an email?
Yes. Each Mail inbox also has a JSON endpoint: send a POST request with a title, a body and optionally a sender and a link, using the send-only key in the Authorization header.
Does it work when my computer is off?
Yes. Reception and storage happen on AgentsRoom's servers. The messages wait in the inbox and you can read them from the mobile app at any time.
How many emails can I receive?
Per calendar month and across all your inboxes: 10 as a guest, 100 with a free account, 200 with Plus and 500 with Pro. Team seats include Pro. Push notifications have their own allowance.
Related features
Push Notification API
Send a push notification to your iPhone or Android phone from cURL, a CI job or a cron script. One HTTPS request, a send-only key, works with your computer off.
Triggers: webhook mode
Trigger an AI coding agent from a webhook instead of a clock. Paste one public URL into GitHub, GitLab, Slack, Linear, Sentry or any service that can POST JSON, and AgentsRoom starts an agent the moment the event lands: a pull request opened, a build failed, an issue created, an alert fired. Signature checked, optional payload filter, burst limit, and the payload becomes prompt variables. An agent that polls costs tokens on every loop; a webhook trigger costs nothing until something happens.
Scheduled Tasks: cron for AI agents
Schedule recurring AI agents and development workflows without writing a single cron expression. Run a Claude Code or Codex session every morning to review pull requests, scan crash logs every night, check dependencies every Monday, generate a weekly changelog or run a QA pass after every deploy. Pick a frequency (every N minutes, hourly, daily once or twice a day, weekly, monthly, or on your AI plan's quota window), a prompt and an agent role. AgentsRoom launches it for you, catches up missed runs on next launch and keeps a reopenable run history.
Mobile Companion
Dictate prompts and attach files from your phone. Share screenshots on iOS or Android, choose a project and send to an agent or save in its backlog.
Give your project its own inbox
Download AgentsRoom, create a Mail inbox and paste its address into your first service.
Companion app: monitor your agents on the go
Bring your own: Claude, Codex, Antigravity CLI, or other AI provider.
Push bugs and requests straight to your public backlog.