Show HN: Broccoli, one shot coding agent on the cloud

(github.com)

22 points by yzhong943 hours ago

7 comments

sinansaka54 minutes ago
nice work! I built a similar system at my previous company. It was built on top of github. agent was triggered by the created issue, run in actions, save state in PR as hidden markdown.<p>It worked great but time to first token was slow and multi repo PRs took very long to create (30+ mins)<p>Now im working on my standalone implementation for cloud native agents
- yzhong9452 minutes ago
  Why was the time to first token slow? Was it because of the spin up time for containers? That was an issue for us when we were running on Google's Cloud Run. We switched to Blaxel and it's much faster now. The hibernate feature has been great for comment iteration.
throwaway77831 hour ago
Cool! We have a similar setup,connected to JIRA, but it stops at analysis and approach to solution. I'm taking inspiration from this now to take it to the next level!
- yzhong9458 minutes ago
  I'd pay special attention to the harness that goes from plan to execute. We spent a lot of time ensuring this can produce high quality code that we feel good about in production instead of AI slop.<p>As for Jira, would love it if you contribute that integration to us! Someone asked for it in this thread :D
orliesaurus1 hour ago
I use the Codex integration in Linear, can you tell me more about the differences please?
- yzhong941 hour ago
  Tell me more about your workflow! For us, the workflow is, we'd assign the ticket to a bot user we create (broccoli in this case), and broccoli will go spin up a sandbox and do the execution. Do you trigger the task execution from Codex by giving it a linear ID? That was Broccoli v0 but of course still requires you to setup Codex with all the right keys.
  - orliesaurus2 minutes ago
    They say it better than me: <a href="https://linear.app/integrations/codex" rel="nofollow">https://linear.app/integrations/codex</a>
dbmikus2 hours ago
Like the detailed setup instructions in the readme!<p>Also agree that teams should invest in their own harness (or maybe pedantically, build a system on top of harness likes Claude Code, Codex, Pi, or OpenCode)
- yzhong942 hours ago
  Yes! Broccoli is triggering Codex CLI and Claude Code CLI.
  - deaux1 hour ago
    Does that mean you're using API pricing rather than subscription? Seems like itd get expensive very quickly for a small team.
    - yzhong9451 minutes ago
      It's a bit of trade-off. If we spin up a new container every time (which we do when we were using Google Cloud Run), we had to pay API pricing. However, with Blaxel, we can set containers to hibernate which also gives us the ability to use subscription
Jayakumark2 hours ago
Thanks for making it open source, Jira Support would be good
- yzhong942 hours ago
  Good point! Adding that to our list of to-dos - we don't use Jira but I guess it's still very popular!
hizihic2 hours ago
[dead]
bellowsgulch44 minutes ago
[dead]
- jdlyga18 minutes ago
  Broccoli has been around since the 6th century BC
- carabiner13 minutes ago
  Naming software has gotten so much worse. We're just at full on random words now. Looking forward to next project management software called "Dumbbell" or something.
- yzhong9431 minutes ago
  different flavors :D