AWS Open-Sources Pizza Bot to Manage AI Agents Outside the Chat Window

AWS has open-sourced Pizza Bot, a self-hosted application that treats long-running AI work less like a chat and more like email. Users can hand an agent a task, leave it running, then return to completed results or requests for a decision. The design makes delegation easier, but it also moves oversight from the moment work happens to the moment a person opens the queue.

Pizza Bot organizes work into All, which holds task history; Unread, for finished work awaiting review; and Action, for tasks paused for input or approval. Its Activity panel shows how an agent handled a task, including its transcript. That is a deliberate contrast with a conventional chat interface, where work and supervision typically occupy the same live exchange.

The work can be started manually, on a cron schedule, or by webhook. Checkpoints preserve agent messages, tool activity and current state, so a task can pause and resume after a client disconnects while its backend stays running. Pizza Bot offers Electron desktop, browser and command-line clients, all communicating with its API server over HTTP and server-sent events.

Pizza Bot is not simply a desktop app that keeps working after it closes. Closing a client does not stop a run when the backend remains active, but an always-on backend is required for work to continue after the embedded desktop server exits. The distinction matters for anyone expecting a laptop app to provide unattended automation by itself.

The release supports Amazon Bedrock, Anthropic, Google Gemini, OpenAI, OpenRouter and local models through Ollama. It can be extended with Agent Skills, plugins and Model Context Protocol servers, which can expose external tools. Those capabilities widen what an agent can do, but they make configuration central: tool-specific policies can require a user to approve, edit or reject a proposed action.

The project’s default server binding is local-only, at 127.0.0.1. Reaching it over a non-loopback network address requires authentication and an explicit origin allowlist. Users must also explicitly grant folder access; added folders are read-only unless write access is allowed. Pizza Bot warns that MCP servers and plugins are trusted components whose commands can run with the user account’s permissions.

AWS developed Pizza Bot at Amazon and released it under the Apache 2.0 license; the project says more than 2,000 Amazon users tested earlier versions. That internal use gives the product a practical origin, but it does not remove the work of deploying it elsewhere. Analysts told InfoWorld that enterprise teams may still need to build, secure and maintain connectors for systems such as CRM, email and ERP.

The strongest case for Pizza Bot is that a person need not watch every intermediate step. One analyst said an inbox can bring people back only when judgment is needed and can make scheduled work easier to review. The counterargument is operational: a stream of background threads can hide bad work until it is finished, while repeated approval requests can encourage cursory sign-offs or authorize actions based on information that has gone stale.

That tension likely explains the analysts’ expectation that early users will be individual technologists and small platform teams, rather than regulated industries or less technical business users. Pizza Bot is a useful attempt to give persistent agents an operating surface beyond chat. Whether it becomes an enterprise tool will depend on how well teams design the integration, monitoring and approval process around it.