Live data from Hacker News

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

github.com

51–57 of 57 posts

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

#52
post #24

It'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…

if youre still looking, curious about scope

is this weekend project or bigger? approach changes a lot.

james.exec@proton.me

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

#55

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: AI slop - What does this mean in practice? Better "system" prompts?

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

#56

Earlier 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

Re: AI slop - What does this mean in practice? Better "system" prompts?

Not just system prompts. Everything on Broccoli goes through multiple rounds of design critiques, and then multiple rounds of code review
Post reply on HN