Do you have a list of a few mcp servers or other tools you would add to help with the pizza-bot specific workflow? For example, how would you enforce structured output, should that be an mcp server, a plugin, already in the box?
This looks great. I've been playing around with GrokBot, and like a lot of what it does, but would much, much prefer an open source project to manage various asynchronous tasks.<p>What I like about GrokBot is the combination of freeform agent discussions, scheduled jobs, agent-to-agent communication, per-agent memory, and the fact that they all get a sandboxed instance with a browser. It's very well implemented. I think they have a very similar vision to yours.
Thanks for the feedback! I’ll give GrokBot a closer look. We’re focused on being open source and decoupled from any particular model provider, but it’s great to see a lot of capable tools popping up in this space.<p>We do ship a QuickJS code interpreter, but otherwise, sandboxing is something we deferred until after launch to make sure we have time to get it right. LangGraph / DeepAgents, which we’re built on, already have the right hooks in place, though. :)
Why does it have to be a desktop app vs a self hostable web app?<p>That way it can truly run asynchronously, even with the computer switched off.
It’s both! The Releases page indeed links to the Electron app so it’s easy to get started, but you can also run just the backend and web app separately. I have it running in a Docker container on my home network that I connect to from my phone using Tailscale. Check out the docs here: <a href="https://github.com/pizza-bot-app/pizza-bot/blob/main/docs/STANDALONE_BACKEND.md" rel="nofollow">https://github.com/pizza-bot-app/pizza-bot/blob/main/docs/ST...</a>
Why not use real email?
congrats on the public launch! it's been clear to me for a while now that agents will need their own ways to communicate and an asynchronous inbox/task system is a necessity already. will point my agents at the repo to see how we can leverage
I have a more basic question; I am trying to understand its purpose.<p>How does this compare with connecting your agent to your ticket tracker, e.g., <a href="https://linear.app/build" rel="nofollow">https://linear.app/build</a> ?<p>If it is about local work, how does it compare with simply having your agent monitor a directory for ticket files?
Thanks for the question!<p>Think of Pizza Bot as the "harness"/interface your agents actually run in. You'd still hook up Linear via their MCP server (<a href="https://linear.app/docs/mcp" rel="nofollow">https://linear.app/docs/mcp</a>) for "what needs doing." Pizza Bot is what handles the run itself (scheduling the interaction, routing tool-call approvals to you, and holding conversation/agent state).<p>The part that's actually different from "agent in a terminal" or "agent posting to Slack" is that it's built for having a bunch of these running at once. Instead of N terminal tabs or N ticket comment threads to figure out which agent is stuck waiting on you, they land in one inbox — jump between threads, see which ones are paused on an approval or a question, answer, and move on.<p>Let me know if that helps to clarify things!
[dead]