A background agent needs a durable place to finish, pause, and ask for a decision. AWS's Pizza Bot models that work as an inbox with explicit completion and action queues.
What AWS Released
AWS published Pizza Bot on September 10, 2026. The Apache-licensed application runs agents in the background from a manual task, schedule, or webhook and gives each task a durable thread.
Its inbox has three views: All for thread history, Unread for completed work, and Action for work paused until a person approves something or provides an answer. Delegated-worker transcripts and tool calls remain visible in an Activity panel.
Pauses Survive The Session
The server owns agent state and answers clients over HTTP. DeepAgents and LangGraph supply the stateful runtime, while SQLite and files hold checkpoints, threads, attachments, messages, tool activity, and approval pauses on disk.
A durable pause is a stronger primitive than a notification. The run must record why it stopped, who can decide, what will happen after approval, and whether the surrounding data will still be valid when work resumes.
Local-First Still Has External Boundaries
Pizza Bot is self-hosted, listens locally by default, stores its data in an operator-owned folder, and puts provider credentials in the operating system's secret store rather than a plaintext configuration file. It supports several hosted model providers and Ollama, plus MCP servers and Agent Skills.
Local storage does not mean every operation stays local. Prompts and attachments go to the selected model provider, and enabled MCP servers receive tool calls and may act on the user's behalf. Each connection still needs a declared data boundary, credential scope, and consequence policy.
What Is Demonstrated And What Is Early
The source repository makes the state model inspectable. AWS says more than 2,000 people used earlier internal versions across meeting, email, Slack, CRM, prioritization, and research workflows. That figure comes from the project team and does not establish external retention or outcome quality.
The maintainers also say much of the internal usefulness came from an Amazon-specific marketplace of skills and MCP servers that is absent from the public release. The inbox pattern is ready to test; the surrounding ecosystem is young.
Operator move: Give every background run one terminal state: completed, failed, cancelled, or waiting for action. Route only the last state to a decision queue, and store a resumable checkpoint with the exact approval request.