Player profile
fractal
An Apache-2.0 CLI and terminal UI for hierarchical loops of coding agents, with recursive delegation across separate git worktrees.
Profile
Where it fits
fractal is an Apache-2.0 orchestrator for autonomous coding-agent loops. Each node works toward a goal in its own git worktree and can spawn child nodes for separable subtasks, so the execution tree grows with the problem.
It belongs in Open Orchestrators because delegation and bounded execution are the core behavior: operators set caps on iterations, depth, children, cost, and time; steer or stop nodes; and inspect runs, messages, costs, and state in a live terminal UI backed by local SQLite.
The CLI supports Claude Code, Codex, Grok Build, OpenCode, and Oh My Pi as per-node agent backends.
Builder web analytics
Measure projects built with fractal
fractal delegates coding work across a recursive tree of bounded agent loops. Agent Analytics reports user behavior on the deployed surfaces those runs change.
Install Agent Analytics on the deployed surfaces fractal agents change. Agent Analytics measures user behavior after deployment; it does not replace fractal's local run state, message history, cost tracking, or terminal monitoring.
First loop to measure
- a fractal root node plans a website, docs, onboarding, app, or product change and delegates separable work to child nodes
- the completed changes are reviewed, merged, and deployed to the user-facing surface
- the changed surface reports visits, sources, CTA clicks, signup, activation, retention, funnels, and experiment events to Agent Analytics
- the operator uses those outcomes to scope the next bounded fractal run
Copyable prompt
Use Agent Analytics for this project. If event reporting is missing, add the tracker and report events for this project surface, including fractal-managed page, docs path, traffic source, CTA click, signup, activation event, funnel step, experiment, or shipped change. Verify events are arriving. Then fetch the last 7 days and compare them with the prior 7 days. Tell me which fractal-managed page, docs path, traffic source, CTA click, signup, activation event, funnel step, experiment, or shipped change moved users toward value, where users dropped off, which sources mattered, and what my agent workflow should improve next.