this is exactly what I was looking for! can't wait to try it out
Show HN: Broccoli, one shot coding agent on the cloud
21–30 of 57 posts
Re: Show HN: Broccoli, one shot coding agent on the cloud
#22this is exactly what I was looking for! can't wait to try it out
let us know if you have any feedback!
Re: Show HN: Broccoli, one shot coding agent on the cloud
#23How does this compare to using Claude Web with connectors to build the same feature?
On a separate note, READMEs written by AI are unpleasant to read. It would be great if they were written by a human for humans.
Re: Show HN: Broccoli, one shot coding agent on the cloud
#24It's interesting that you’re using Linear tickets as the primary context source. From my experience so far, one of the biggest issues with coding agents is context drift. Ticket says one thing, but the codebase has changed since it was written. How did you solve? fresh RAG pass or use something like ctags to map the repo before it starts the implementation, or does it rely entirely on the LLM's provided context window?
Re: Show HN: Broccoli, one shot coding agent on the cloud
#25How does this compare to using Claude Web with connectors to build the same feature? On a separate note, READMEs written by AI are unpleasant to read. It would be great if they were written by a human for humans.
The main difference is that you have full control over this!
Re: Show HN: Broccoli, one shot coding agent on the cloud
#26Fair play for launching this, it looks like a neat project.
However I feel it will be an uphill battle competing with OpenAI and Anthropic, I doubt your harness can be better since they see so much traffic through theirs.
So this is for those who care about the harness running on their own infra? Not sure why anyone would since the LLM call means you are sending your code to the lab anyway.
Sorry I don’t want to sound negative, I am just trying to understand the market for this.
Good luck!
Re: Show HN: Broccoli, one shot coding agent on the cloud
#27Cool! 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
Yeah. We also use gitlab instead of github. I'll check this out later.
We also have set it up to work with multiple repos to truly understand context (we have frontend, backend, some tooling etc, an MCP server etc all in different repos).
Re: Show HN: Broccoli, one shot coding agent on the cloud
#28Fair play for launching this, it looks like a neat project. However I feel it will be an uphill battle competing with OpenAI and Anthropic, I doubt your harness can be better since they see so much traffic through theirs. So this is for those who care about the harness running on their own infra? Not sure why anyone would since the LLM call means you are sending your code to the lab anyway. Sorry I don’t want to soun…
We are not trying to compete with OpenAI and Anthropic! We open source it because there's interest from other startups.
Teams would use Anthropic and OpenAI, but they shouldn't just use Anthropic or OpenAI. We see much better results from calling the models independently and do adversarial review and response.
This doesn't replace your need for the models, but you certainly don't need to rely on any of the cloud agent solutions out there that call these models underneath the hood.
Re: Show HN: Broccoli, one shot coding agent on the cloud
#29It's interesting that you’re using Linear tickets as the primary context source. From my experience so far, one of the biggest issues with coding agents is context drift. Ticket says one thing, but the codebase has changed since it was written. How did you solve? fresh RAG pass or use something like ctags to map the repo before it starts the implementation, or does it rely entirely on the LLM's provided context windo…
We don’t believe PM or eng can write the best prompt or spec, so we don’t ask them to.
One real Linear ticket from a few months back that we assigned to broccoli:
Store post-processing run outcomes in a versioned, append-only audit trail so re-running the same processor on the same audio file produces a complete history (who/when/what changed), while keeping an easy “latest result” view. Add an admin-only UI.
That’s it. As a part of the sketch step, broccoli does its own repo discovery and online research before planning the execution.
Re: Show HN: Broccoli, one shot coding agent on the cloud
#30Earlier quoted context omitted.
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
Yeah. We also use gitlab instead of github. I'll check this out later. We also have set it up to work with multiple repos to truly understand context (we have frontend, backend, some tooling etc, an MCP server etc all in different repos).
We also have a multi-repo setup, to trigger it you can just tag two repos in the Linear label!