Show HN: Pizza Bot – An inbox for AI agents that work in the background
Recorded: Sept. 15, 2026, 10 p.m.
| Original | Summarized |
GitHub - pizza-bot-app/pizza-bot: A local-first inbox for long-running AI agents, built with DeepAgents and LangGraph. · GitHub Skip to content Navigation MenuSign inAppearance settingsPlatformAI CODE CREATIONGitHub CopilotWrite better code with AIGitHub Copilot appDirect agents from issue to mergeMCP RegistryIntegrate external toolsDEVELOPER WORKFLOWSActionsAutomate any workflowCodespacesInstant dev environmentsIssuesPlan and track workCode ReviewManage code changesCode QualityEnforce quality at mergeAPPLICATION SECURITYGitHub Advanced SecurityFind and fix vulnerabilitiesCode securitySecure your code as you buildSecret protectionStop leaks before they startEXPLOREWhy GitHubDocumentationBlogChangelogMarketplaceView all featuresSolutionsBY COMPANY SIZEEnterprisesSmall and medium teamsStartupsNonprofitsBY USE CASEApp ModernizationDevSecOpsDevOpsCI/CDView all use casesBY INDUSTRYHealthcareFinancial servicesManufacturingGovernmentView all industriesView all solutionsResourcesEXPLORE BY TOPICAISoftware DevelopmentDevOpsSecurityView all topicsEXPLORE BY TYPECustomer storiesEvents & webinarsEbooks & reportsBusiness insightsGitHub SkillsSUPPORT & SERVICESDocumentationCustomer supportCommunity forumTrust centerPartnersView all resourcesOpen SourceCOMMUNITYGitHub SponsorsFund open source developersPROGRAMSSecurity LabMaintainer CommunityGitHub StarsArchive ProgramREPOSITORIESTopicsTrendingCollectionsEnterpriseENTERPRISE SOLUTIONSEnterprise platformAI-powered developer platformAVAILABLE ADD-ONSGitHub Advanced SecurityEnterprise-grade security featuresCopilot for BusinessEnterprise-grade AI featuresPremium SupportEnterprise-grade 24/7 supportPricingSearch/Sign inSign upAppearance settings You signed in with another tab or window. Reload to refresh your session. Dismiss alert Uh oh! There was an error while loading. Please reload this page. pizza-bot-app pizza-bot Public
Notifications
Fork
Star Code Issues Pull requests Discussions Actions Security and quality Insights
Additional navigation options
Code Issues Pull requests Discussions Actions Security and quality Insights
mainBranchesTagsGo to fileCodeOpen more actions menuLatest commit History79 Commits79 CommitsFolders and filesNameNameLast commit messageLast commit date.github.github appsapps assetsassets docsdocs examples/pluginsexamples/plugins packagespackages pluginsplugins scriptsscripts skillsskills tests/langgraph-compattests/langgraph-compat .dockerignore.dockerignore .env.example.env.example .gitignore.gitignore .worktreeinclude.worktreeinclude AGENTS.mdAGENTS.md CLAUDE.mdCLAUDE.md CODE_OF_CONDUCT.mdCODE_OF_CONDUCT.md CONTRIBUTING.mdCONTRIBUTING.md DockerfileDockerfile LICENSELICENSE NOTICENOTICE README.mdREADME.md ROADMAP.mdROADMAP.md SECURITY.mdSECURITY.md docker-compose.ymldocker-compose.yml eslint.config.jseslint.config.js package-lock.jsonpackage-lock.json package.jsonpackage.json tsconfig.base.jsontsconfig.base.json tsconfig.jsontsconfig.json turbo.jsonturbo.json vitest.config.tsvitest.config.ts View all filesRepository files navigationREADMECode of conductContributingApache-2.0 licenseSecurityMore itemsPizza Bot OSS Pizza Bot uses a stateful DeepAgents/LangGraph runtime with the same React Work asynchronously. Switch conversations without stopping their runs. Download Experience Electron desktop Browser Terminal CLI Standalone backend A running api-server needs access to at least one model provider; HTTP clients The production graph engine is isolated to packages/runtime-langgraph; Running - desktop, browser, CLI, and package commands. Security and data Local-first by default. The api-server binds to 127.0.0.1; non-loopback See SECURITY.md for the complete security model and vulnerability Sous Chefs Pizza Bot was also shaped by more than 2,000 users across Amazon who tested Footer © 2026 GitHub, Inc. Footer navigation Terms Privacy Security Status Community Docs Contact Manage cookies Do not share my personal information You can’t perform that action at this time. |
Pizza Bot functions as a local-first inbox designed specifically for managing long-running artificial intelligence agents, leveraging the integration of DeepAgents and LangGraph to manage complex asynchronous workflows. The core purpose of the system is to allow users to initiate tasks, detach from the process, and resume work seamlessly, ensuring that agent execution persists even when client connections are lost. This is achieved by maintaining a stateful runtime that allows agents to continue processing tasks, with completed work archived in an Unread queue and pending approval requests managed in an Action queue for user intervention. The system is architected to be accessible across multiple interfaces, utilizing the same underlying process model for communication via HTTP and SSE. This unified system is rendered through a desktop Electron application, a web application built with React, and a command-line interface for terminal access, enabling flexible interaction with the agent workflows. The design prioritizes operational flexibility, allowing users to manage conversations by grouping threads into folders without obscuring concurrent work in the global queues. A critical feature is the ability to resume work, as checkpoints for agent runs survive client disconnections, and external triggers like cron jobs or webhooks can initiate new tasks without requiring an active conversation. Furthermore, the agents can be delegated to specialists through the concept of agent skills, where these skills function as tool-scoped subagents whose progress is visible in an Activity panel. This structure facilitates a sophisticated delegation of tasks. To support external capabilities, Pizza Bot integrates support for various model providers, including Amazon Bedrock, Anthropic, Google Gemini, OpenAI, OpenRouter, and Ollama. The system handles interactions with these providers by configuring model selections, where a specific model is selected using a format that specifies the provider and ID. The architecture incorporates human-in-the-loop controls, long-term memory storage, file attachments, and desktop notifications directly into the workflow design, ensuring that consequential actions are overseen by the user. Security and data handling are fundamental to the design, adhering to a local-first philosophy. The application state, including threads, checkpoints, memories, attachments, and logs, is stored locally under a designated root directory. Access to local folders requires explicit permission settings, meaning the system does not default to accessing the user's home directory. The api-server binds locally, and remote access necessitates explicit authentication and an origin allowlist. The system trusts external extensions, such as MCP servers and plugins, which can execute commands and materializers with the user’s permissions, necessitating careful management of trusted sources. The project structure is modular, separating concerns into distinct directories such as apps, packages, plugins, skills, and tests, with the core graph engine isolated within packages/runtime-langgraph. This separation ensures that frontends consume protocol projections rather than direct model or runtime bindings, promoting modularity. The documentation further details the architecture, system boundaries, event models, persistence strategies, and security protocols, alongside guidance on running the system, extending its capabilities through skills and plugins, and contributing to the codebase. |