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.

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.

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

We’re a small team, and our main company supplies voice data. But we kept running into the same problem with coding agents. We’d have a feature request, a refactor, a bug, and some internal tooling work all happening at once, and managing that through local agent sessions meant a lot of context switching, worktree juggling, and laptops left open just so tasks could keep running.

So we built Broccoli. Each task gets its own cloud sandbox to be executed end to end independently. Broccoli checks out the repo, uses the context in the ticket, works through an implementation, runs tests and review loops, and opens a PR for someone on the team to inspect.

Over the last four weeks, 100% of the PRs from non-developers are shipped via Broccoli, which is a safer and more efficient route. For developers on the team, this share is around 60%. More complicated features require more back and forth design with Codex / Claude Code and get shipped manually using the same set of skills locally.

Our implementation uses:

1. Webhook deployment: GCP 2. Sandbox: GCP or Blaxel 3. Project management: Linear 4. Code hosting & CI/CD: Github

Repo: https://github.com/besimple-oss/broccoli

We believe that if you should invest in your own coding harness if coding is an essential part of your business. That’s why we decided to open-source it as an alternative to all the cloud coding agents out there. Would love to hear your feedback on this!

Comments URL: https://news.ycombinator.com/item?id=47865642

Points: 48

# Comments: 33

We built IntelliAgent because deep research agents from ChatGPT / Gemini / Perplexity are hard to customize beyond some prompt improvement, which means: 1/ Often returning results I was not looking for, including wrong sources, missing sources, and wrong directions. 2/ Cannot be modified during the search process, so I end up waiting for 15min+ only to modify the prompt again

What it does: 1/ Prompt improvement via clarifying questions 2/ Editable pre‑flight search plan you can modify before starting 3/Step‑by‑step execution that automatically pivots or extend directions as results come in

Try it out! https://myintelliagent.com/intelliagent

Comments URL: https://news.ycombinator.com/item?id=44977567

Points: 3

# Comments: 0