What is this?
An open-source, local-first inbox for long-running AI agent work, built with DeepAgents and LangGraph. You start or schedule a task, walk away, and come back to finished work in an Unread queue and decisions waiting in Action.
An open-source, local-first inbox for long-running AI agent work, built with DeepAgents and LangGraph. You start or schedule a task, walk away, and come back to finished work in an Unread queue and decisions waiting in Action.Is it a desktop app or something I open in a browser?Both, plus a terminal CLI. One stateful DeepAgents/LangGraph runtime serves the same React experience in Electron and the browser, and the desktop app, web app, and CLI all talk to the api-server over HTTP/SSE.
Both, plus a terminal CLI. One stateful DeepAgents/LangGraph runtime serves the same React experience in Electron and the browser, and the desktop app, web app, and CLI all talk to the api-server over HTTP/SSE.How do I get it running?Grab an installer from the releases page (.dmg/.zip for macOS, -setup.exe for Windows x64, .deb/.rpm for Linux) or run npm run dev with Node.js 24+. Then configure a model under Settings > Providers before your first live run.
Grab an installer from the releases page (.dmg/.zip for macOS, -setup.exe for Windows x64, .deb/.rpm for Linux) or run npm run dev with Node.js 24+. Then configure a model under Settings > Providers before your first live run.Do I need to bring my own model provider or API key?Yes. A running api-server needs at least one provider — Amazon Bedrock, Anthropic, Google Gemini, OpenAI, OpenRouter, or Ollama — configured under Settings > Providers; the browser and CLI clients themselves need none.
Yes. A running api-server needs at least one provider — Amazon Bedrock, Anthropic, Google Gemini, OpenAI, OpenRouter, or Ollama — configured under Settings > Providers; the browser and CLI clients themselves need none.What happens if I close the app while an agent is mid-task?The run keeps going: agents continue when you navigate away or disconnect, and checkpointed runs survive client disconnects. Only the api-server process must stay running, and cron or webhook triggers can even start work with no conversation open.
The run keeps going: agents continue when you navigate away or disconnect, and checkpointed runs survive client disconnects. Only the api-server process must stay running, and cron or webhook triggers can even start work with no conversation open.Is this an Amazon internal tool, or can anyone use it?Anyone. It was developed at Amazon, where more than 2,000 employees tested earlier versions, and it is now open-sourced under Apache 2.0 with signed installers for macOS, Windows, and Linux.
Anyone. It was developed at Amazon, where more than 2,000 employees tested earlier versions, and it is now open-sourced under Apache 2.0 with signed installers for macOS, Windows, and Linux.Where does my data end up?Stays local by default: the api-server binds to 127.0.0.1, and threads, checkpoints, memories, attachments, and logs live under ~/.pizza-bot-oss. Only requests to the providers and endpoints you configure leave the machine; non-loopback binding requires authentication.
Stays local by default: the api-server binds to 127.0.0.1, and threads, checkpoints, memories, attachments, and logs live under ~/.pizza-bot-oss. Only requests to the providers and endpoints you configure leave the machine; non-loopback binding requires authentication.How do I extend it with new tools or agents?Add MCP servers from the UI or a .mcp.json file, drop Agent Skills under /skills, or install plugins that bundle MCP servers and skills together. Skills become tool-scoped subagents whose progress shows up in the Activity panel.
Add MCP servers from the UI or a .mcp.json file, drop Agent Skills under /skills, or install plugins that bundle MCP servers and skills together. Skills become tool-scoped subagents whose progress shows up in the Activity panel.Can the agent read my files?Only folders you explicitly grant under Settings > Files, and each stays read-only unless you allow writes. There is no default home-directory access, and remote grants name paths on the backend host.
Only folders you explicitly grant under Settings > Files, and each stays read-only unless you allow writes. There is no default home-directory access, and remote grants name paths on the backend host.Why call it an inbox instead of a chat app?Because results and decisions queue up for you: completed work lands in Unread, durable approval requests land in Action, and you can group threads into folders without hiding matching work from those global queues.
Because results and decisions queue up for you: completed work lands in Unread, durable approval requests land in Action, and you can group threads into folders without hiding matching work from those global queues.How are my provider API keys stored?The desktop protects entered secrets with Electron safeStorage, and server-side configuration persists only environment-variable references rather than the keys themselves.
The desktop protects entered secrets with Electron safeStorage, and server-side configuration persists only environment-variable references rather than the keys themselves.What are similar projects?qwen-code, agentscope, opensquilla, hive, evenfire, turnstone, ruflo, brigade
qwen-code, agentscope, opensquilla, hive, evenfire, turnstone, ruflo, brigadeWhich topics is it in?deepagents, langgraph, human-in-the-loop, ollama, electron, agentic-ai, gemini, anthropic, multi-agent, local-first, openai, react
deepagents, langgraph, human-in-the-loop, ollama, electron, agentic-ai, gemini, anthropic, multi-agent, local-first, openai, react