Run background agents with an email-style approval inbox
An inbox for long-running AI work. Task: Pizza Bot provides an inbox for long-running AI tasks where agents continue working even if the client disconnects, requiring only the api-server to remain active. Users start or schedule tasks asynchronously, with completed work appearing in an 'Unread' queue and pending decisions in an 'Action' queue for human review. The system supports various model providers and allows delegation to specialized subagents via skills, while maintaining local-first data storage and explicit file access controls.; tools: custom-built or unnamed agent. Human role: The original post does not say how a person stayed involved.; limitations: Requires Node.js 24 or newer and a running api-server process for background tasks to persist. Users must configure at least one model provider (e.g., Amazon Bedrock, OpenAI) and explicitly grant file access permissions. MCP servers and plugins are trusted and can execute with user permissions, posing security risks if untrusted sources are installed. Local data storage is default, but remote setups require authentication and origin allowlists..
Tools
custom-built or unnamed agent
Published on Agent Work Atlas:
Overview
An inbox for long-running AI work.
Workflow
Pizza Bot provides an inbox for long-running AI tasks where agents continue working even if the client disconnects, requiring only the api-server to remain active. Users start or schedule tasks asynchronously, with completed work appearing in an 'Unread' queue and pending decisions in an 'Action' queue for human review. The system supports various model providers and allows delegation to specialized subagents via skills, while maintaining local-first data storage and explicit file access controls.
Reported result
The source does not report specific measured outcomes, success rates, or business impact metrics for Pizza Bot. It describes the intended workflow of asynchronous task management and human-in-the-loop approvals but lacks evidence of actual execution results or performance data. No failures or specific user achievements are documented in the provided text.
Human role
The original post does not say how a person stayed involved.
Limitations
Requires Node.js 24 or newer and a running api-server process for background tasks to persist. Users must configure at least one model provider (e.g., Amazon Bedrock, OpenAI) and explicitly grant file access permissions. MCP servers and plugins are trusted and can execute with user permissions, posing security risks if untrusted sources are installed. Local data storage is default, but remote setups require authentication and origin allowlists.
Try it
I want to set up Pizza Bot for asynchronous task management. First, install Node.js 24+ and clone the repository. Run 'npm install' and 'npm run dev' to start the Electron desktop shell and api-server. Configure a model provider in Settings > Providers using my [API_KEY] for [PROVIDER_NAME]. Create a test task that requires a decision, such as drafting an email to [RECIPIENT_EMAIL] about [TOPIC]. Ensure the task is scheduled or started, then disconnect the client. Reconnect and check the 'Action' queue for the pending approval. Review the draft, approve or reject it, and verify the result in the 'Unread' queue. Do not send any real emails until I explicitly confirm the draft is correct. If the task fails to persist after disconnect, check if the api-server process is still running. Report the status of the task persistence and the approval workflow.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.