fabro vs fractal
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. — versus — Hierarchical agent loops: nodes iterate toward a goal in their own git worktree and spawn children for subtasks — the tree grows to fit the problem. Hard caps, SQLite run log, live TUI.
Opposite philosophies of unattended multi-agent coding: Fabro encodes the process up front as a workflow graph with verification gates; fractal lets the process emerge recursively under resource caps. Predefine vs self-organize.
| fabro | fractal | |
|---|---|---|
| Stars | 1.4k | 614 |
| Forks | 154 | 44 |
| Language | Rust | Python |
| License | MIT | Apache-2.0 |
| Last activity | yesterday | today |
| Topics | coding, orchestration | coding, orchestration |
| Curated connections | 3 | 3 |
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.
fractal — the curator's take
The self-organizing answer to multi-agent coding: no fixed pipeline — a node that finds a separable subtask spawns a child for it, bounded by hard caps on depth, children, iterations, cost and time, with an operator able to steer or kill any loop from the TUI. The README's warning deserves framing: every seeded config DISABLES the agent's approval gate (bypassPermissions, danger-full-access, --yolo) because unattended loops can't stop to ask — and worktrees isolate the branch, NOT the filesystem or network. Treat that as a hard requirement to run it inside real isolation, not a footnote. NOT for work needing deterministic process: if you want the same stages every run, you want a workflow graph, not a fractal. 614 stars — early.