News confirmed medium confidence

AWS Releases Pizza Bot, an Inbox for Background AI Tasks

The self-hosted community application separates finished work from approval requests, while leaving deployment and connected-tool choices to users.

Edited by Tyronne Panaino

AWS announced Pizza Bot on September 10 as an open-source application that puts background AI work in an inbox. It gives people delegating longer tasks a place to review completed results and answer requests for approval, without keeping a chat window open.

The release is a community project rather than an AWS service. Its maintainers describe a self-hosted application with a choice of model provider; users remain responsible for running, backing up and updating it.

Completed tasks and approvals have separate queues

The launch account describes All as thread history, Unread as completed work and Action as tasks awaiting a decision. Tasks can start manually, on a schedule or through a webhook.

Closing a thread does not end server-side work. Quitting the desktop application does stop the server it started and its active runs, although checkpoints preserve the thread. That distinction matters when deciding where scheduled work should run.

Local storage still has an outbound boundary

The project's security document says prompts, attachments and tool payloads go to configured model providers and endpoints. Self-hosting therefore does not mean all processing remains on the machine.

The documented default binds the server to loopback. Remote binding requires a token and allowed origins, while the API's plain HTTP listener requires protected transport for remote use. The maintainers discourage public-internet exposure and describe a shared token with full API access.

Folder access requires an explicit grant, with write access a separate choice. The security document also warns that installing MCP servers or plugin hooks can run code with the user's permissions. Application-level folder grants should not be mistaken for operating-system confinement of those processes.

Verify a workflow before relying on it

For an initial trial, use a limited task and inspect its result, approval pause and configured destinations. This is an evaluation recommendation. This coverage has not tested the application, its security controls or its recovery behavior.

Status

Confirmed release; medium internal confidence. The launch account and project documentation provide an interested-actor account, without independent operational validation.

Sources

Update note: Last reviewed September 16, 2026. Project changes or independent testing may refine this coverage.

Sources

Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.

More News coverage