Broccoli
A tool that turns a Linear ticket into a finished pull request automatically — assign an issue to it like you'd assign it to a teammate, and it goes off, writes the code, tests it, and opens a PR for someone to review, all inside your own cloud account.
🔗 Visit Broccoli
Description
Engineering teams manage backlogs of small, well-defined tickets — a bug fix here, a minor feature there — that someone eventually has to actually implement. Broccoli works like assigning that ticket to a very fast, very literal junior developer who never needs a stand-up: you hand it a Linear issue, it goes and reads the code, makes the change, runs the tests, and comes back with a pull request instead of a status update, ready for a human to inspect before it merges.
Technically, Broccoli gives each assigned task its own isolated cloud sandbox, checks out the target repo, and uses Claude or OpenAI Codex to plan and implement the change, run tests and review loops, and open a PR — all deployed on your own Google Cloud project (optionally with Blaxel for sandboxing) rather than a third-party's infrastructure, backed by PostgreSQL for job state and driven by GitHub/Linear webhooks. It's MIT licensed and open source; you pay only your own GCP compute costs, with a documented ~30-minute setup via one bootstrap script, one config file, and two webhooks.
💬 Our review
The short version: this is a legitimate, no-vendor-lock-in way to automate routine tickets if your team already runs on Linear + GitHub + GCP, but it demands real infrastructure comfort that a hosted competitor would otherwise handle for you.
Against Devin or Cognition, which sell autonomous coding agents as a managed SaaS with a support relationship, Broccoli's whole pitch is the opposite: self-hosted, no third-party control plane, no data leaving your tenancy — a real advantage for teams with compliance concerns about code leaving their infrastructure. Against Cursor's background agents or GitHub Copilot Workspace, which are tightly integrated into an existing editor/platform experience, Broccoli is more of a headless automation layer that plugs into your existing Linear/GitHub workflow rather than a new place to work. The trade-off is support: there's no vendor to call when the sandbox misbehaves, and running it well requires someone on the team who's genuinely comfortable operating GCP infrastructure, not just writing code.
📊 Global score
🤖 AI-enriched data
MIT, gratuit. Coûts limités à votre propre facturation GCP (et Blaxel en option pour le sandboxing).
Pros
Self-hosted, aucune donnée ne quitte votre tenant
Gratuit, open source, coûts limités à GCP
Tickets Linear → PR GitHub automatisés
Setup documenté ~30 minutes
Cons
Exige des compétences d'exploitation GCP réelles
Aucun support fournisseur en cas de problème
Lié spécifiquement à Linear + GitHub
Moins mature que les alternatives commerciales type Devin