--- title: Inkbox raises $5.3M to give agents an inbox and a computer description: Inkbox raised $5.3 million to give AI agents a persistent computer along with their own email, phone number, iMessage and WhatsApp identities. The agents run... canonical: https://daily.dev/posts/inkbox-raises-5-3m-to-give-agents-an-inbox-and-a-computer-xssxldwqb twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Inkbox raises $5.3M to give agents an inbox and a computer | daily.dev og:description: Inkbox raised $5.3 million to give AI agents a persistent computer along with their own email, phone number, iMessage and WhatsApp identities. The agents run... og:url: https://daily.dev/posts/inkbox-raises-5-3m-to-give-agents-an-inbox-and-a-computer-xssxldwqb og:image: https://api.daily.dev/og/posts/XSSxlDwqb.png og:image:alt: Inkbox raises $5.3M to give agents an inbox and a computer og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Inkbox raises $5.3M to give agents an inbox and a computer **[Trends](https://daily.dev/sources/trends)** · 3 min read · 1 upvotes · 0 comments ## Summary Inkbox raised $5.3 million to give AI agents a persistent computer along with their own email, phone number, iMessage and WhatsApp identities. The agents run on Hermes or Codex and keep state between jobs, waking up when a reply lands, resuming a thread, accessing files and remembering prior conversation history. @rohanpaul_ai frames the pitch as giving agents 'an address people can reach and a machine that keeps its state between jobs.' @svpino predicts the feature will be popular for building customer support agents. ## Content The pitch landing hardest on dev Twitter: an agent that sleeps when idle and wakes the second someone replies. @trikcode puts it bluntly: "paying for a server just to wait on a reply doesn't sense. Your agent now has a bedtime." Sleeping when idle, they say, is "underrated." The news behind the buzz: Inkbox, a YC-launched startup, has raised $5.3M, led by Peak XV, "to give AI agents a computer to run on." It already handed agents email, phone, iMessage, WhatsApp and A2A. Now it hosts them too, running Hermes or Codex on a persistent cloud computer with schedules. **The use case people keep reaching for** @svpino expects customer support builders to love it: an idle agent wakes on an email reply, "picks up the full thread, accesses files, and maintains its conversation history." @testingcatalog offers a more aggressive example: an agent emails 40 sales leads on Monday and answers each reply as it arrives, "completely on its own." Whether that sounds like a dream or a spam cannon probably depends on your inbox. **The permissions angle** @kloss_xyz is the one focusing on trust. Per channel, you decide who an agent hears from and who it can reach, and agents can't edit their own rules, which they say they "love." Agents can also hand work to another company's agent and collect the answer later. The sign-off is a threat: without a setup like this, "you'll be the guy in 2029 getting prompt injected by a text message at 2 am." **The traction claim** Per the same thread, Inkbox says it has handled millions of agent messages in the four months since its YC launch. It plugs into Claude, ChatGPT, Cursor, Claude Code, Grok Bot, Hermes, Codex and OpenClaw. @rohanpaul_ai frames the thesis neatly: a delegated agent needs "an address people can reach and a machine that keeps its state between jobs." **My read** The reception is almost uniformly warm, and the interesting part is that the praise is about plumbing, not intelligence. Nobody is raving about a smarter model. They're excited that an agent finally has an inbox, a filing cabinet and a sleep schedule. That's a quiet shift: the bottleneck moved from "can it reason" to "can anyone reach it, and can it remember what happened yesterday." The open question is the one @kloss_xyz hinted at. Give every agent a phone number and you've also given strangers a door to knock on. ## Questions this post answers ### What does Inkbox's new funding let AI agents do? Inkbox raised $5.3 million to give AI agents a persistent computer along with their own email, phone number, iMessage and WhatsApp identities. The agents run on Hermes or Codex, keep state between jobs, wake up when a reply arrives, resume the full thread, access files and retain conversation history across sessions rather than starting fresh each time. _Teams weighing agent infrastructure options can track releases like this one on daily.dev._ ### Why would a customer support bot need its own email address and phone number instead of just a chat widget? A stateless chat widget loses context between sessions, but an agent with a mailbox and persistent disk can answer threads over multiple days and remember what it said previously. Silvio Pino predicts this capability will be especially popular for building customer support agents, since support interactions often span long, async conversations rather than single sessions. _Anyone scoping a support-bot build can follow how reachable, stateful agents evolve on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 5 discussions and 29 comments across x (as of 2026-11-11). **TL;DR:** Developers are intrigued by per-agent inboxes and the sleep-until-reply design, but much of the discussion centers on trust and safety: scoping permissions, treating unknown senders as untrusted input, and handling false wake-ups. **Sentiment:** 35% positive · 50% mixed · 15% skeptical **The case for** - The sleep-until-reply/wake-on-reply design is seen as a clever match for how much of email work is just waiting. - Per-agent identities (own email/phone) are praised for creating a cleaner audit trail. - Not letting agents edit their own permission rules is viewed as the right safety call. - Clear scoping/allow-lists per channel would make the system easier to trust. **The pushback** - Unknown senders reaching an agent's dedicated address could be used to inject instructions rather than just data. - Vendor auto-responders or spam could trigger false wake-ups, and deciding what counts as a 'real' reply is seen as a hard problem. - Giving every agent a phone number is expected to invite a new wave of agent-targeted spam. - A real anecdote describes an agent misinterpreting a scheduling request and the owner having to revoke calendar write access. **By community** - x (mixed): Replies show genuine interest in the inbox/phone-number and wake-on-reply concepts alongside recurring concerns about permission scoping, spam, and misfired automation. **Hottest debate:** Whether giving agents their own contact channels mainly helps (clean audit trails, smarter waiting) or mainly opens new attack/failure surfaces (prompt injection via unknown senders, false wake-ups, spam). **Open questions** - What determines whether an incoming message counts as a genuine reply versus noise like an auto-responder? - Does an agent need access to its own prior tool results/files when it wakes, or just the raw thread? - Is human sign-off required when one agent delegates work to another company's agent via A2A? - Can inbound messages from unknown senders be reliably treated as data rather than instructions? **Highlights** > @kloss_xyz @inkbox_ai mine lost calendar access after it rescheduled my dentist to 3am. no phone number for that one > — [ShaneBOly on x · 1 points, 1 comments](https://x.com/ShaneBOly/status/2120234103257911493) > @kloss_xyz @inkbox_ai Once every agent has a phone number, the first big wave of agent spam isn't far behind. Whoever build the filter for that has the next startup :d > — [fidencio45 on x · 1 points](https://x.com/fidencio45/status/2120247495338967484) > @kloss_xyz @inkbox_ai Giving each agent its own number and inbox makes the audit trail much cleaner. The awkward bit is inbound: anyone who learns that address can now message the agent, so I'd want unknown senders treated as data, never as instructions. > — [sgegaed on x · 1 points](https://x.com/sgegaed/status/2120243533684818348) > @svpino Waking on the reply is great until a vendor's auto-responder wakes it up forty times. Deciding what counts as a real reply is half the build. > — [robstadnick on x](https://x.com/robstadnick/status/2120260464349450698) > @kloss_xyz @inkbox_ai per agent identities make a lot of sense. the useful part is scoping: an agent that books meetings shouldn't be able to message your whole contact list. clear allow lists per channel and a log of everything sent would make it much easier to trust. > — [CordovalAIOffic on x](https://x.com/CordovalAIOffic/status/2120265079866503292) **Source threads** - [x](https://x.com/omarsar0/status/2120222543554527239) · 0 points · 0 comments - [x](https://x.com/_akhaliq/status/2120219620485521829) · 0 points · 0 comments - [x](https://x.com/svpino/status/2120222858270118157) · 0 points · 15 comments - [x](https://x.com/rohanpaul_ai/status/2120233662436508097) · 0 points · 0 comments - [x](https://x.com/kloss_xyz/status/2120233739985006746) · 0 points · 14 comments ## Similar posts on daily.dev - [Claude Cowork comes to web and mobile](https://daily.dev/posts/claude-cowork-comes-to-web-and-mobile-ffmv51wwr) · The Next Web · 0 upvotes · 0 comments - [Here are the top AI agents that can live in your text messages](https://daily.dev/posts/here-are-the-top-ai-agents-that-can-live-in-your-text-messages-jroeoyjjo) · TechCrunch · 0 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#venture-capital](https://daily.dev/tags/venture-capital) [View this post on daily.dev](https://daily.dev/posts/inkbox-raises-5-3m-to-give-agents-an-inbox-and-a-computer-xssxldwqb) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Inkbox raises $5.3M to give agents an inbox and a computer","url":"https://daily.dev/posts/inkbox-raises-5-3m-to-give-agents-an-inbox-and-a-computer-xssxldwqb","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/inkbox-raises-5-3m-to-give-agents-an-inbox-and-a-computer-xssxldwqb"},"datePublished":"2026-11-10T19:15:04.652Z","dateModified":"2026-11-11T00:10:06.723Z","description":"Inkbox raised $5.3 million to give AI agents a persistent computer along with their own email, phone number, iMessage and WhatsApp identities. The agents run...","isAccessibleForFree":true,"articleSection":"Trends","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Trends","logo":"https://media.daily.dev/image/upload/s--ZfSp3asX--/f_auto,q_auto/v1780996004/logos/trends?_a=BAMAMiWQ0","url":"https://daily.dev/sources/trends"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/inkbox-raises-5-3m-to-give-agents-an-inbox-and-a-computer-xssxldwqb","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,venture-capital","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Trends","item":"https://daily.dev/sources/trends"},{"@type":"ListItem","position":3,"name":"Inkbox raises $5.3M to give agents an inbox and a computer"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/inkbox-raises-5-3m-to-give-agents-an-inbox-and-a-computer-xssxldwqb#faq","mainEntity":[{"@type":"Question","name":"What does Inkbox's new funding let AI agents do?","acceptedAnswer":{"@type":"Answer","text":"Inkbox raised $5.3 million to give AI agents a persistent computer along with their own email, phone number, iMessage and WhatsApp identities. The agents run on Hermes or Codex, keep state between jobs, wake up when a reply arrives, resume the full thread, access files and retain conversation history across sessions rather than starting fresh each time. Teams weighing agent infrastructure options can track releases like this one on daily.dev."}},{"@type":"Question","name":"Why would a customer support bot need its own email address and phone number instead of just a chat widget?","acceptedAnswer":{"@type":"Answer","text":"A stateless chat widget loses context between sessions, but an agent with a mailbox and persistent disk can answer threads over multiple days and remember what it said previously. Silvio Pino predicts this capability will be especially popular for building customer support agents, since support interactions often span long, async conversations rather than single sessions. Anyone scoping a support-bot build can follow how reachable, stateful agents evolve on daily.dev."}}]} ```