AWS Engineers Open-Source Pizza Bot, an Inbox for Background AI Agents

A group of developers at Amazon Web Services has released Pizza Bot, an open-source, self-hosted application that gives background AI agents a shared inbox to report into. The project, surfaced by InfoQ contributor Renato Losio, targets a gap that shows up as soon as agents move past chat windows: nobody wants to babysit a terminal to find out whether a job finished. Pizza Bot runs the work asynchronously and delivers the outcome as a message, the way email or a task queue would.

The mechanics are straightforward. Agents pick up work on a schedule or when a webhook fires, rather than waiting for a user to type a prompt. They can hand subtasks to specialized workers, so a single request might fan out across several models or tool-specific agents before results are assembled. Crucially, an agent can halt mid-task and wait for a human to sign off, turning approval into a first-class step instead of an afterthought bolted on at the end.

That approval gate is the detail worth paying attention to. Most agent frameworks today assume full autonomy or force a developer to write custom interrupt logic; Pizza Bot treats pausing as part of the normal execution path. For teams deploying agents against production systems, that changes the risk calculus, because a human can inspect a proposed action before it touches real data or spends real money.

Self-hosting is the other deliberate choice. The application runs on infrastructure the operator controls, which matters for companies that cannot send internal context to a vendor's cloud. It also sidesteps per-seat or per-run pricing from managed agent platforms. The tradeoff is familiar: open source means no support contract, and operators own the uptime, credentials and security review themselves.

Pizza Bot arrives in a crowded stretch for agent infrastructure. Frameworks for orchestration, memory and tool use have multiplied over the past year, but the boring plumbing, how a finished job reaches a person, has lagged behind. An inbox is a deliberately unglamorous answer, and it borrows conventions that knowledge workers already understand rather than inventing a new dashboard.

The project is early, and the open questions are practical. How well does it handle long-running jobs that fail partway through, and what happens when two agents claim the same task? Whether Pizza Bot becomes a default layer or just a useful reference design depends on how quickly its maintainers answer those, and on whether outside contributors show up now that the code is public.