jd_

4 ms·

1. 1.▲
   by jd_ 8d ago

   Quick update that I added issues for both the README update and overriding the model that a skill's subagent will use: - https://github.com/pizza-bot-app/pizza-bot/issues/99 - https://github.c
2. 2.▲
   by jd_ 8d ago

   Quick update. This doesn't work out of the box, but I've created an issue to enable this here: https://github.com/pizza-bot-app/pizza-bot/issues/98
3. 3.▲
   by jd_ 10d ago

   Totally agree! I’ve got scheduled agents that run (a little slowly) overnight using Qwen 3.8 27B that are ready for me by the morning. :)
4. 4.▲
   by jd_ 10d ago

   Thanks for the question! I could maybe see that being the case for LangChain, specifically, if you’re just thinking about abstracting the LLM provider’s APIs. But here, we’re specifically using LangGraph to handle checkpointing and state ma
5. 5.▲
   by jd_ 11d ago

   Oh neat - thank you for sharing! I hadn’t seen this before, but we were definitely inspired by a post LangChain made about “ambient agents”: https://www.langchain.com/blog/introducing-ambient-agents It seemed fitting t
6. 6.▲
   by jd_ 11d ago

   Thanks! I think it depends on how well Pizza Bot aligns with your mental model. Despite living in Claude Code for many things, I find the email-like UX we built for Pizza Bot matches my intuition for how I want to interact with agents beyon
7. 7.▲
   by jd_ 11d ago

   Thanks for the question! Similar to another user’s comment about Paperclip, Herdr looks to provide a layer on top of existing agent harnesses, whereas with Pizza Bot, we run the execution loops for each agent ourselves (built on LangGraph &
8. 8.▲
   by jd_ 11d ago

   Ah, this may actually work out of the box if you tell Pizza Bot to use its `task` tool to dynamically launch a subagent (which maps 1:1 with a Skill), and provide it with a `responseSchema`. I’ll test this when I’m back at a computer and r
9. 9.▲
   by jd_ 11d ago

   Author here - thanks so much for the great questions! Our post on the AWS Open Source blog has more screenshots and an architecture diagram if you want to give it a skim: https://aws.amazon.com/blogs/opensource/int
10. 10.▲
    by jd_ 11d ago

    Thanks so much for the feedback! The README arguably needs a diagram that shows the orchestrator-subagent delegation pattern and how they map to Skills, since you’re right - it’s not intuitive without reading the docs, and it’s somewhat uni
11. 11.▲
    by jd_ 11d ago

    @aaronax had a similar thought! In our case, we wanted to borrow the UX of email (to be intuitive to knowledge workers) but not necessarily the implementation. Full control of your data was a design principle from the beginning, including b
12. 12.▲
    by jd_ 11d ago

    Love it. Maybe "inbox zero" for agents would have been a better tagline! :)
13. 13.▲
    by jd_ 11d ago

    Thanks! I'm not overly familiar with Paperclip, but from the website, it looks to provide orchestration over a fleet of existing agent harnesses, whereas with Pizza Bot, we run the execution loops for each agent ourselves (built on L
14. 14.▲
    by jd_ 11d ago

    There are so many! Personally, I’ve been able to get remarkably far with the built-in filesystem tools (courtesy of DeepAgents) paired with a web search MCP (Kagi is great!). Were there any particular workflows you had in mind?
15. 15.▲
    by jd_ 11d ago

    You mean giving each agent its own real email address? Startups like AgentMail are certainly doing that! In our case, we wanted to borrow the UX of email (to be intuitive to knowledge workers) but not necessarily the implementation. Was the
16. 16.▲
    by jd_ 11d ago

    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. We do ship a QuickJS code
17. 17.▲
    by jd_ 11d ago

    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 ph
18. 18.▲
    by jd_ 11d ago

    Thanks for the question! Think of Pizza Bot as the "harness"/interface your agents actually run in. You'd still hook up Linear via their MCP server ( https://linear.app/docs/mcp ) for "what needs
19. 19.▲
    by jd_ 11d ago

    Thanks! I was pleasantly surprised with how naturally a lot of email idioms seemed to align here. In retrospect, it makes sense if you think of human-to-agent communication as another form of asynchronous communication.
20. 20.▲
    by jd_ 11d ago

    Thanks! Just posted more details here: https://news.ycombinator.com/item?id=49713894
21. 21.▲
    by jd_ 11d ago

    Posted some thoughts here: https://news.ycombinator.com/item?id=49713894
22. 22.▲
    Show HN: Pizza Bot – An inbox for AI agents that work in the background(github.com)

    35 points by jd_ 11d ago|20 comments
23. 23.▲
    by jd_ 12d ago

    Author here - thanks for posting this! I’m planning to make a Show HN post tomorrow with lots of HN-friendly details. :)
24. 24.▲
    by jd_ 15d ago

    Author here - thanks for posting this! Some context for the HN crowd -- Pizza Bot started as a hacky Playwright script I wrote at Amazon to stop manually logging CRM activities. It eventually grew into an internal tool with a couple thousan