Live data from Hacker News

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

github.com

11–20 of 57 posts

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

#11

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!

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.

As for Jira, would love it if you contribute that integration to us! Someone asked for it in this thread :D

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

#12
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.

It worked great but time to first token was slow and multi repo PRs took very long to create (30+ mins)

Now im working on my standalone implementation for cloud native agents

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

#13

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. It worked great but time to first token was slow and multi repo PRs took very long to create (30+ mins) Now im working on my standalone implementation for cloud native agents

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.

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

#14
post #7
post #5

Earlier quoted context omitted.

Yes! Broccoli is triggering Codex CLI and Claude Code CLI.

Does that mean you're using API pricing rather than subscription? Seems like itd get expensive very quickly for a small team.

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

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

#19

I use the Codex integration in Linear, can you tell me more about the differences please?

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.

They say it better than me: https://linear.app/integrations/codex

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

#20

Earlier quoted context omitted.

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.

They say it better than me: https://linear.app/integrations/codex

Oh got it! In this case, the main difference is that we go through a flow from design to implement using our own prompts, and uses both Codex and Claude Code so they can improve off of each other.
Post reply on HN