Pizza Bot: a local-first inbox for long-running AI agents

Amazon released Pizza Bot, an open-source, local-first inbox for long-running AI agents, under the Apache 2.0 license. The tool runs on a stateful DeepAgents/LangGraph runtime with an Electron desktop app, browser client, and terminal CLI that all communicate with an api-server over HTTP/SSE, and it supports model providers including Amazon Bedrock, Anthropic, Google Gemini, OpenAI, OpenRouter, and Ollama. Pizza Bot requires Node.js 24 or newer, ships signed and notarized macOS installers plus unsigned Windows and Linux builds with a SHA256SUMS file, and grants no default home-directory access.

Pizza Bot is an inbox for long-running AI work. Start or schedule a task, return to your day, and let completed work collect in Unread while runs waiting for your decision collect in Action . Agents keep working when you navigate away or disconnect; the api-server process must remain running. Pizza Bot uses a stateful DeepAgents/LangGraph runtime with the same React experience in Electron and the browser. The desktop app, web app, and terminal CLI all communicate with the api-server over HTTP/SSE. Pizza Bot was developed at Amazon and is released under the Apache 2.0 license. - Work asynchronously. Switch conversations without stopping their runs. - Return to the right queue. Completed work lands in Unread; durable approval requests land in Action. - Organize conversations. Group threads into folders without hiding matching work from the global Unread and Action queues. - Resume real work. Checkpointed runs survive client disconnects, and cron or webhook triggers can start work without an open conversation. - Delegate to specialists. Skills become tool-scoped workers whose progress appears in the Activity panel. - Bring your model provider. Amazon Bedrock, Anthropic, Google Gemini, OpenAI, OpenRouter, and Ollama are supported. - Keep control of consequential actions. Human-in-the-loop approvals, long-term memory, file attachments, and desktop notifications are built into the workflow. - Grant local access explicitly. Add individual read-only or writable folders under Settings Files ; Pizza Bot receives no default home-directory access. Installers for macOS Intel and Apple silicon , Windows, and Linux x64 and arm64 are attached to every release /pizza-bot-app/pizza-bot/releases , with a SHA256SUMS to check a download against. The macOS builds are signed and notarized; the Linux packages are not signed, so verify them against the checksums. Node.js 24 or newer is required. npm install npm run build npm run dev npm run dev starts the Vite frontend and Electron desktop shell. The shell forks and supervises its own api-server, matching the packaged application's process model. Configure a model under Settings Providers before starting a live run. See Running from source /pizza-bot-app/pizza-bot/blob/main/docs/RUNNING.md for isolated data roots, browser and CLI development, desktop packages, and remote backends. | Experience | Best for | Start here | |---|---|---| | Electron desktop | Local inbox with an embedded backend | npm run dev | | Browser | Web development or static deployment | Browser development /pizza-bot-app/pizza-bot/blob/main/docs/RUNNING.md browser-development | | Terminal CLI | Scripts, terminals, and remote backends | CLI /pizza-bot-app/pizza-bot/blob/main/docs/RUNNING.md cli | | Standalone backend | Remote Electron, browsers, containers, or Linux services | Backend guide /pizza-bot-app/pizza-bot/blob/main/docs/STANDALONE BACKEND.md | A running api-server needs access to at least one model provider; HTTP clients do not. Configure Amazon Bedrock, Anthropic, Google Gemini, OpenAI, OpenRouter, or Ollama in Settings Providers . Bedrock accepts an AWS profile, AWS access keys, or a Bedrock API key, with an optional region override; otherwise AWS REGION or us-west-2 is used. Bedrock combines its native catalog with the regional Mantle catalog and routes models through Converse, OpenAI Responses or Chat Completions, or Anthropic Messages according to their advertised API family. OpenAI and Anthropic also accept custom base URLs for compatible endpoints; OpenAI can explicitly select Responses or Chat Completions, and Anthropic supports x-api-key or bearer authentication. Select a model with PIZZA MODEL=<provider :<id . The desktop protects entered secrets with Electron safeStorage ; server configuration persists only environment-variable references. Add MCP servers from the UI or <PIZZA DATA ROOT /.mcp.json . Add Agent Skills under <PIZZA DATA ROOT /skills , or install plugins that package MCP servers and skills together. Skills become available after their declared tools are enabled and connected. A custom skill can replace a Built-in or Plugin skill with the same id without modifying the original; removing the customization reveals the Built-in or Plugin version again. The Built-in Pizza Bot Guide can explain features, suggest workflows, help with setup, and point to project documentation. See Extending Pizza Bot /pizza-bot-app/pizza-bot/blob/main/docs/EXTENDING.md for configuration, environment references, skill authoring, approval gates, and plugin installation. apps/ api-server Hono | cli | desktop-shell Electron | web React packages/ core | runtime-langgraph | inference-providers | plugin-api | plugin-sdk | storage | logging plugins/ bundled Plugin packages and their packaging workspace skills/ optional Built-in Agent Skills tests/ LangGraph compatibility and protocol conformance The production graph engine is isolated to packages/runtime-langgraph ; frontends consume protocol projections rather than importing runtime or model bindings. - Running /pizza-bot-app/pizza-bot/blob/main/docs/RUNNING.md - desktop, browser, CLI, and package commands. - Extending /pizza-bot-app/pizza-bot/blob/main/docs/EXTENDING.md - MCP servers, skills, and plugins. - Architecture /pizza-bot-app/pizza-bot/blob/main/docs/ARCHITECTURE.md - system boundaries, event model, persistence, transports, and design decisions. - Standalone backend /pizza-bot-app/pizza-bot/blob/main/docs/STANDALONE BACKEND.md - authentication, remote Electron, static browser deployment, Docker, Compose, and Kubernetes. - Contributing /pizza-bot-app/pizza-bot/blob/main/CONTRIBUTING.md - development setup, CI checks, worktrees, releases, and layering rules. - Security /pizza-bot-app/pizza-bot/blob/main/SECURITY.md - network defaults, credentials, local data, and plugin trust. - Logging /pizza-bot-app/pizza-bot/blob/main/docs/LOGGING.md - diagnostics, retention, viewing, and redaction. - Roadmap /pizza-bot-app/pizza-bot/blob/main/ROADMAP.md - exploratory directions and the principles used to evaluate them. - Code of Conduct /pizza-bot-app/pizza-bot/blob/main/CODE OF CONDUCT.md - community participation expectations. - Local-first by default. The api-server binds to 127.0.0.1 ; non-loopback binding requires authentication and an explicit origin allowlist. - Application state stays local. Threads, checkpoints, memories, attachments, and logs live under <PIZZA DATA ROOT ~/.pizza-bot-oss by default . Model and tool requests go to the providers and endpoints you configure. - Local folders require an explicit grant. Each folder added under Settings Files is read-only unless you allow writes. Remote grants name paths on the backend host. - MCP servers and plugins are trusted. Their commands and materializers can execute with your user account's permissions. Install only sources you trust. See SECURITY.md /pizza-bot-app/pizza-bot/blob/main/SECURITY.md for the complete security model and vulnerability reporting process. Pizza Bot was designed, built, and brought into the open by its Executive Chefs and Sous Chefs: Pizza Bot was also shaped by more than 2,000 users across Amazon who tested earlier versions and shared feedback from real-world use. Their bug reports, ideas, and candid input helped make Pizza Bot ready for a broader community. Thank you to everyone who contributed. Apache-2.0 /pizza-bot-app/pizza-bot/blob/main/LICENSE . See NOTICE /pizza-bot-app/pizza-bot/blob/main/NOTICE for attribution notices.