contrabass vs fabro
Terminal-first orchestrator for issue-driven AI coding-agent runs — polls Linear/GitHub, runs Codex/OpenCode in git worktrees with retries and verification. Go/Charm rebuild of OpenAI's Symphony. — versus — Rust 'software factory' for coding agents: define the SDLC as a graph, agents execute it through verification gates, you intervene only at the stages that matter. Server, runs board, sandboxes.
Both run coding agents through gated, verified pipelines instead of a REPL. Contrabass is terminal-first and issue-driven (poll Linear/GitHub, worktrees, branch-advance checks); Fabro is a server with workflow graphs, ensemble models and cloud sandboxes.
| contrabass | fabro | |
|---|---|---|
| Stars | 202 | 1.4k |
| Forks | 24 | 155 |
| Language | Go | Rust |
| License | Apache-2.0 | MIT |
| Last activity | 6 days ago | today |
| Topics | coding, orchestration | coding, orchestration |
| Curated connections | 7 | 2 |
contrabass — the curator's take
Pick it when your work already lives in Linear or GitHub issues and you want local coding agents (Codex, OpenCode, oh-my-*) burning down the backlog unattended — worktree per issue, branch-advance verification so 'success' means commits actually landed, stall detection, deterministic retries, and a Bubble Tea TUI plus embedded web dashboard for visibility. Skip it for single interactive sessions (just run the agent CLI) or if you want cloud-hosted execution — pullfrog is the GitHub-Actions version of this job. Young Symphony reimplementation: the workflow parser accepts more fields than the runtime consumes, and the default team mode needs tmux.
fabro — the curator's take
For the team past the babysit-or-rubber-stamp dilemma: encode your process as a version-controlled workflow graph — implement with one model, cross-critique with another, gate on verification — and let the API server run it 24/7, locally or in isolated cloud sandboxes. CSS-like stylesheets for model routing is a genuinely clever cost lever. NOT a quick add-on: this is infrastructure with a server, a web wizard and a process philosophy — solo devs wanting lighter structure should look at terminal-first orchestrators first. Young project; the 'dark factory' ambition is ahead of the ecosystem's verification reality, so keep the gates strict.