podium

fractal

50 of 51 criteria have a sourced finding; 45 were also cross-checked by a second agent. Every comparison that includes fractal links here for scope, limitations, atomic answers and sources.

Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.

Rubric
0.3 · 51 criteria
Source checks
2026-11-16
Agent cross-checked
45 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Agent cross-checked partial

Terminal-only: the fractal CLI plus a Textual TUI cockpit (fractal open) and tmux panes; POSIX hosts (macOS and Linux code paths), headless mode where tmux is unavailable; no web, desktop, mobile app, mobile browser or editor extension.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops, fractal open Textual TUI cockpit · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • POSIX only.
  • No GUI, web or mobile client.
9 atomic answers
  • Desktop os [partial] Python >=3.12 on POSIX only (PyPI classifier Operating System :: POSIX); process code handles macOS and Linux; CI runs on ubuntu-latest; no Windows support or packaged desktop app. Sources: fractal:pyproject, fractal:processsrc.
  • Mobile apps [unsupported] Bounded search finds no iOS or Android app. Sources: fractal:srch-clients.
  • Browser [unsupported] No web server or browser interface in the package. Sources: fractal:srch-clients.
  • Mobile browser [unsupported] No web interface, so no mobile browser access. Sources: fractal:srch-clients.
  • Cli [supported] fractal CLI with init, node, plan, radio, channel, cost, time, config and db sub-apps. Sources: fractal:nodecmd, fractal:cliNode.
  • Editor extensions [unsupported] No editor extension; skills install into Claude Code and Codex instead. Sources: fractal:srch-clients, fractal:pluginsrepo.
  • Task actions [partial] Start, steer (radio, NODE.md, chat), approve gated steps, stop/pause/resume and merge from the CLI; the TUI observes and sends radio/chat only; review is through git. Sources: fractal:operating, fractal:tui.
  • Notifications [unsupported] No push or desktop notifications; attention comes from radio inbox, node list quiet flag and TUI unread dots. Sources: fractal:operating, fractal:tui.
  • Cross device continuity [partial] State is in a local SQLite database and worktrees; durability docs describe moving the repository to another host and resuming, but there is no multi-device client. Sources: fractal:durability, fractal:schema.

Sources: fractal:pyproject, fractal:processsrc, fractal:srch-clients, fractal:nodecmd, fractal:cliNode, fractal:pluginsrepo, fractal:operating, fractal:tui, fractal:durability, fractal:schema

Agent cross-checked supported

Embeds none; drives five agent CLIs as subprocesses (Claude Code, Codex, Grok Build, OpenCode, Oh My Pi) with per-node choice, mixed backends inside one tree, an OpenRouter route for Claude and Codex, and a registry for custom backends.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
5 atomic answers
  • Harnesses [supported] claude, codex, grok, opencode and omp registered in fractal/impl. Sources: fractal:providers, fractal:agentimpl.
  • Model providers [supported] Anthropic, OpenAI, xAI via their CLIs; OpenRouter for Claude/Codex (--provider=openrouter) and natively through OpenCode and Oh My Pi model ids. Sources: fractal:readme, fractal:providers.
  • Custom adapters [supported] agent register() and a per-tree deployment hook file let an embedding application add or override backends. Sources: fractal:providers, fractal:extending.
  • Session integration [supported] Each backend is a subprocess driven line by line with a parser into normalized stream events; sessions are forked, resumed or fresh; it controls the CLI, not an embedded harness. Sources: fractal:providers.
  • Mixed harness operation [supported] Children inherit the agent unless a node chooses its own via --agent, so one tree can mix backends; delegated child starts follow the parent backend by default. Sources: fractal:readme, fractal:providers.

Sources: fractal:providers, fractal:agentimpl, fractal:readme, fractal:extending

Sourced partial

Uses each agent CLI's own login or API key from the launching shell plus OPENROUTER_API_KEY for the OpenRouter route; no fractal account or credits; spend is priced from LiteLLM tables.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • agent subscriptions: Backends run the user logged-in CLI so a subscription login on the host works; fractal documents no per-plan guidance and its cost ledger prices tokens rather than subscription allowance.
  • vendor credits: No vendor credits or hosted usage exist.
  • local models: OpenCode and Oh My Pi can use their own configured model ids; fractal documents no local-model setup.
  • account switching: Bounded search finds no multi-account switching.
7 atomic answers
  • Agent subscriptions [partial] Backends run the user logged-in CLI so a subscription login on the host works; fractal documents no per-plan guidance and its cost ledger prices tokens rather than subscription allowance. Sources: fractal:providers, fractal:pricing.
  • Api accounts [supported] API keys in the launching environment are inherited; OPENROUTER_API_KEY for --provider=openrouter. Sources: fractal:readme, fractal:providers.
  • Vendor credits [unsupported] No vendor credits or hosted usage exist. Sources: fractal:srch-billing.
  • Local models [partial] OpenCode and Oh My Pi can use their own configured model ids; fractal documents no local-model setup. Sources: fractal:readme.
  • Account switching [unsupported] Bounded search finds no multi-account switching. Sources: fractal:providers.
  • Vendor account requirement [supported] No fractal account is needed; each agent CLI needs its own. Sources: fractal:readme.
  • Provider restrictions [unsupported] Bounded grep of README, wiki and docs finds no guidance on provider terms for unattended or subscription use; the README warns only that nodes run without permission prompts. Sources: fractal:srch-terms, fractal:readme.

Sources: fractal:providers, fractal:pricing, fractal:readme, fractal:srch-billing, fractal:srch-terms

Agent cross-checked partial

pip install plasma-fractal, fractal install for skills, fractal init on a git branch, node init, author NODE.md, launch in tmux; requires a git repo; no non-Git or no-remote restriction (push is skipped when origin is missing); no cloud or VPS installer.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • Git is required.
  • No remote-host onboarding.
7 atomic answers
  • First task setup [supported] Four stages documented: install, fractal init, fractal node init, write NODE.md and launch. Sources: fractal:gettingstarted.
  • No git [unsupported] Every node lives in a git worktree; init requires a git branch. Sources: fractal:gettingstarted, fractal:worktrees.
  • Local git without remote [supported] Push is skipped with a notice when no origin remote is configured. Sources: fractal:commitsrc.
  • Hosted git [partial] Works with any remote origin through plain git push; no GitHub-specific integration. Sources: fractal:commitsrc, fractal:srch-pr.
  • Prerequisite guidance [supported] Docs name git, tmux (or --headless) and at least one agent CLI on PATH. Sources: fractal:gettingstarted.
  • Managed cloud setup [unsupported] No managed cloud exists. Sources: fractal:srch-clients.
  • Byo vps onboarding [unsupported] No installer or onboarding for remote hosts; the CLI can be installed on any POSIX host by hand. Sources: fractal:gettingstarted.

Sources: fractal:gettingstarted, fractal:worktrees, fractal:commitsrc, fractal:srch-pr, fractal:srch-clients

Agent cross-checked partial

The fractal CLI is the programmable surface (CSV or --json output, stable exit codes, FAILED (exit N) last line) plus a Python API documented in docs/api.rst; no REST API, MCP server, webhooks or separate SDK.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • Breaking changes allowed in minor releases.
8 atomic answers
  • Cli [supported] Typer CLI covering create, inspect, steer, stop, merge and cost commands with machine-readable output. Sources: fractal:cliNode, fractal:nodecmd.
  • Api [partial] Python modules (fractal.core) are documented as an API for embedding; no network API. Sources: fractal:providers, fractal:extending.
  • Sdk [partial] The plasma-fractal package is importable (docs/api.rst); no separate multi-language SDK. Sources: fractal:pypi, fractal:docsite.
  • Mcp server [unsupported] fractal exposes no MCP server. Sources: fractal:srch-mcp.
  • Webhooks [unsupported] No webhooks. Sources: fractal:srch-trigger.
  • Operations [supported] create (node init), inspect (status, list, activity, cost), steer (radio send, chat, update), stop/pause/finish/kill and review/merge (merge, diff of template drift). Sources: fractal:nodecmd, fractal:operating.
  • Authentication [not-applicable] Local CLI only; no authentication layer. Sources: fractal:srch-team.
  • Stability [partial] Changelog says minor releases may include breaking changes while the project is young. Sources: fractal:changelog.

Sources: fractal:cliNode, fractal:nodecmd, fractal:providers, fractal:extending, fractal:pypi, fractal:docsite, fractal:srch-mcp, fractal:srch-trigger, fractal:operating, fractal:srch-team, fractal:changelog

Agent cross-checked partial

Installs fractal and wiki skills for Claude Code and Codex (marketplace or fractal install), nodes get seeded skills for fractal, memory, radio and wiki; MCP and plugins inside each node are the agent CLI's own configuration.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • mcp client: Agent backends may use MCP through their own CLI configuration; fractal passes configuration through and does not offer a client.
  • custom tools: Per-node scripts and steps are customizable files seeded into each node.
  • authentication: No fractal-managed integrations.
  • permission scope: Seeds disable approval gates by default; scope limits where commits may land.
7 atomic answers
  • Mcp client [partial] Agent backends may use MCP through their own CLI configuration; fractal passes configuration through and does not offer a client. Sources: fractal:srch-mcp, fractal:providers.
  • Plugins [supported] plasma-ai/plugins marketplace distributes the fractal and wiki skills for Claude Code and Codex. Sources: fractal:pluginsrepo, fractal:readme.
  • Custom tools [partial] Per-node scripts and steps are customizable files seeded into each node. Sources: fractal:nodeinit.
  • Instructions import [supported] NODE.md plus seeded skills and templates; nodes inherit surfaces from the parent with --inherit. Sources: fractal:gettingstarted, fractal:nodeinit.
  • Authentication [not-applicable] No fractal-managed integrations. Sources: fractal:srch-mcp.
  • Permission scope [partial] Seeds disable approval gates by default; scope limits where commits may land. Sources: fractal:seedperm.
  • Integration owner [supported] Skills are shipped by fractal; MCP and plugin setup are inherited from the underlying agent CLI. Sources: fractal:pluginsrepo, fractal:providers.

Sources: fractal:srch-mcp, fractal:providers, fractal:pluginsrepo, fractal:readme, fractal:nodeinit, fractal:gettingstarted, fractal:seedperm

Agent cross-checked partial

Python 3.12+ package using Typer for the CLI and Textual and Rich for the terminal UI; no Electron, Tauri, web or mobile client.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops, fractal open Textual TUI cockpit · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • mobile implementation: No mobile client exists.
4 atomic answers
  • Desktop implementation [supported] Terminal UI built with Textual 8 and Rich 15 (declared dependencies), not a native or Electron client. Sources: fractal:pyproject.
  • Mobile implementation [not-applicable] No mobile client exists. Sources: fractal:srch-clients.
  • Hybrids [supported] No hybrid or wrapper clients found. Sources: fractal:srch-clients.
  • Implementation evidence [supported] pyproject.toml dependencies and the fractal/tui package at the pinned commit. Sources: fractal:pyproject.

Sources: fractal:pyproject, fractal:srch-clients

Planning and context

Agent cross-checked partial

Intake is a prompt or NODE.md contract plus the /fractal skill that turns a directive into a node definition; no issue tracker import and no chat or Git triggers.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • external import: No external issue import found.
  • chat git triggers: No chat or Git event triggers.
  • sync: No external tracker sync.
  • external roundtrips: No external tracker is used.
9 atomic answers
  • Local creation [supported] Nodes are created from fractal node init and NODE.md; the skill drafts parameters from a plain-language directive. Sources: fractal:gettingstarted, fractal:readme.
  • Prompt intake [supported] /fractal [directive] interprets plain language into node parameters and instructions. Sources: fractal:readme.
  • External import [unsupported] No external issue import found. Sources: fractal:srch-pr.
  • Chat git triggers [unsupported] No chat or Git event triggers. Sources: fractal:srch-trigger.
  • Authoritative tracker [supported] The local tree (config.json, NODE.md, SQLite) is authoritative; no external tracker. Sources: fractal:schema.
  • Stable ids [supported] Node branches (dotted tree path) and message UUIDs are stable identifiers. Sources: fractal:worktrees, fractal:radio.
  • Sync [unsupported] No external tracker sync. Sources: fractal:srch-pr.
  • Supported edits [supported] NODE.md and config edits and node update retunes while the loop runs. Sources: fractal:operating.
  • External roundtrips [not-applicable] No external tracker is used. Sources: fractal:srch-pr.

Sources: fractal:gettingstarted, fractal:readme, fractal:srch-pr, fractal:srch-trigger, fractal:schema, fractal:worktrees, fractal:radio, fractal:operating

Agent cross-checked partial

Each iteration writes markdown plan files with run.iter ids and a post-mortem; NODE.md carries instructions and completion requirements re-read every iteration; revisions live in git history.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • editors: Plain markdown files edited with any editor; the TUI does not edit them.
  • revisions: Plans and NODE.md are committed in the node branch, so git history holds revisions.
7 atomic answers
  • Plans [supported] fractal plan init/list create per-iteration plan files; seed PLAN step writes them. Sources: fractal:plans, fractal:seedsteps.
  • Acceptance criteria [supported] NODE.md Completion Requirements section defines the observable conditions for finishing. Sources: fractal:gettingstarted.
  • Editors [partial] Plain markdown files edited with any editor; the TUI does not edit them. Sources: fractal:plans, fractal:tui.
  • Revisions [partial] Plans and NODE.md are committed in the node branch, so git history holds revisions. Sources: fractal:commitpipe.
  • Amendment [supported] NODE.md edits take effect at the next iteration boundary without restart. Sources: fractal:operating.
  • Restart persistence [supported] Plans, NODE.md and state persist in the worktree and database; resume re-enters the interrupted step. Sources: fractal:durability.

Sources: fractal:plans, fractal:seedsteps, fractal:gettingstarted, fractal:tui, fractal:commitpipe, fractal:operating, fractal:durability

Agent cross-checked partial

Nodes form a tree (arbitrary depth up to max-depth) where managers spawn children for separable subtasks, with width/depth/descendant caps and budget checks; approval gates and drains order work; no explicit blocker or readiness model between siblings.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • epics: A manager node with children acts as an epic, but there is no separate epic object.
  • blockers: A manager waits for children (drain) and steps can require parent approval; no declared blocker lists between siblings.
  • readiness: Node status (idle, active, paused, completed, exited) shows state; no ready queue.
9 atomic answers
  • Epics [partial] A manager node with children acts as an epic, but there is no separate epic object. Sources: fractal:spawning.
  • Hierarchy [supported] Dotted branch names spell the tree path; depth and children are capped by configuration. Sources: fractal:worktrees, fractal:spawning.
  • Blockers [partial] A manager waits for children (drain) and steps can require parent approval; no declared blocker lists between siblings. Sources: fractal:guideloop, fractal:operating.
  • Readiness [partial] Node status (idle, active, paused, completed, exited) shows state; no ready queue. Sources: fractal:statuses.
  • Enforcement [supported] Tree caps and spawn-time budget checks are enforced in code without agent cooperation; approval gates park children until approved. Sources: fractal:spawning, fractal:guideloop.
  • State propagation [supported] finish, pause and kill fan out to descendants; pause sweeps parent-first and resume leaf-first. Sources: fractal:finishing, fractal:durability.
  • Task to epic [supported] A leaf node becomes a manager by raising max-children and depth, keeping its branch and history, since limits are retunable with node update. Sources: fractal:operating, fractal:spawning.
  • Identity retention [supported] The node keeps its branch name, worktree, radio identity and DB rows when its limits are retuned. Sources: fractal:operating, fractal:worktrees.
  • Workflow constraints [supported] Seed steps are editable files; no rigid preset is required. Sources: fractal:seedsteps, fractal:nodeinit.

Sources: fractal:spawning, fractal:worktrees, fractal:guideloop, fractal:operating, fractal:statuses, fractal:finishing, fractal:durability, fractal:seedsteps, fractal:nodeinit

Agent cross-checked partial

Per-node NODE.md, seeded skills, a shared project wiki and per-node memory built on plasma-wiki, with lint and index regeneration; inherited seeds and git history provide provenance; no cross-harness vector memory.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • provenance: Wiki pages carry front matter with created/updated and sources fields; commits tag the iteration.
  • freshness: wiki lint and index regeneration at commit keep structure fresh; no automatic staleness scoring.
10 atomic answers

Sources: fractal:gettingstarted, fractal:seedperm, fractal:pluginsrepo, fractal:readme, fractal:knowledge, fractal:seedsteps, fractal:wikiroot, fractal:commitpipe, fractal:nodecmd

Sourced partial

Knowledge comes from the shared wiki and agent CLI tooling; fractal adds no code indexing, retrieval API or architectural conflict detection.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • code search: Agent CLIs search code themselves; fractal adds wiki search through the plasma-wiki skill.
  • indexing: Wiki index pages are regenerated at commit; no repository code index.
  • external knowledge: No external knowledge connectors.
  • multimodal inputs: Image or multimodal input is up to each agent CLI and not described by fractal.
10 atomic answers
  • Indexing [partial] Wiki index pages are regenerated at commit; no repository code index. Sources: fractal:commitpipe.
  • External knowledge [unsupported] No external knowledge connectors. Sources: fractal:srch-mcp.
  • Multimodal inputs [unsupported] Fractal passes text prompts only; a grep of the package finds no image or attachment input path, and anything multimodal depends on the agent CLI. Sources: fractal:srch-image.
  • Freshness [partial] Index refresh happens at each commit. Sources: fractal:commitpipe.
  • Access scope [supported] Scope restricts which subdirectories a node may commit to. Sources: fractal:commitpipe, fractal:nodeinit.
  • Api retrieval [partial] wiki CLI offers retrieval for agents. Sources: fractal:wikirepo.
  • Citations [partial] Wiki pages list sources in front matter. Sources: fractal:wikiroot.
  • Conflict detection [unsupported] No architecture conflict detection. Sources: fractal:srch-review.
  • Review enforcement [unsupported] No review-time enforcement. Sources: fractal:srch-review.

Sources: fractal:knowledge, fractal:wikirepo, fractal:commitpipe, fractal:srch-mcp, fractal:providers, fractal:nodeinit, fractal:wikiroot, fractal:srch-review, fractal:srch-image

Agent cross-checked partial

No native issue or idea backlog: the unit is a node with NODE.md and radio messages; nodes can be created without launching and parked (idle/retired), but there are no labels, search, assignee or project views.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • create: Nodes (not issues) are created with node init.
  • prioritize: Radio messages carry priority 0-10; nodes have no priority field.
  • label: No labels.
  • assign: A node is its own worker; agent and model are set per node.
17 atomic answers
  • Create [partial] Nodes (not issues) are created with node init. Sources: fractal:gettingstarted.
  • Edit [supported] NODE.md and config are editable until and after launch. Sources: fractal:gettingstarted, fractal:operating.
  • Discuss [supported] Radio threads and replies give discussion per node. Sources: fractal:radio.
  • Prioritize [partial] Radio messages carry priority 0-10; nodes have no priority field. Sources: fractal:radio.
  • Label [unsupported] No labels. Sources: fractal:srch-team.
  • Assign [partial] A node is its own worker; agent and model are set per node. Sources: fractal:nodeinit.
  • Filter [partial] node list shows status, spend and limits; filters are limited. Sources: fractal:operating.
  • Archive [supported] retire and unretire shelve nodes. Sources: fractal:statuses, fractal:nodecmd.
  • Reopen [supported] continue and resume re-arm a node. Sources: fractal:durability.
  • Project epic views [partial] The tree view in the TUI and node list show nesting. Sources: fractal:tui.
  • Idea parking [partial] An initialised idle node holds an idea without running. Sources: fractal:gettingstarted, fractal:statuses.
  • Explicit dispatch [supported] node start launches a configured node. Sources: fractal:gettingstarted.
  • Task session separation [supported] Runs, iterations, steps and agent sessions are separate DB entities under a node. Sources: fractal:schema.
  • Metadata [supported] Status, spend, limits, agent, model, effort and scope per node. Sources: fractal:nodeinit.
  • Durable states [supported] Status machine persisted in a status file and DB rows. Sources: fractal:statuses.
  • External tracker requirement [supported] No external tracker is needed or supported. Sources: fractal:srch-pr.

Sources: fractal:gettingstarted, fractal:operating, fractal:radio, fractal:srch-team, fractal:nodeinit, fractal:statuses, fractal:nodecmd, fractal:durability, fractal:tui, fractal:schema, fractal:srch-pr

Agent cross-checked partial

Agents operate the same tree through the fractal CLI inside their node loop (spawn children, radio, finish, status) with attributed rows; there is no issue schema, claim or dependency feature.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • claim: No claim mechanism; each node owns its own worktree.
  • assign: A parent chooses agent, model and effort when it spawns a child.
  • dependencies: No dependency fields.
  • permissions: Caps and scope bound what a node can do; no role permissions.
14 atomic answers

Sources: fractal:worktrees, fractal:radio, fractal:operating, fractal:spawning, fractal:readme, fractal:nodeinit, fractal:finishing, fractal:srch-team, fractal:tui, fractal:mergeguards

Agent cross-checked partial

No living product spec: the project wiki is a maintained shared knowledge base with lint and git history but has no requirement objects, approvals or drift detection.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • persistent requirements: The project wiki persists project knowledge across tasks.
  • revisions: Git history only.
  • approvals: No approval rules for wiki pages.
  • implementation links: Commits record the iteration; pages are not linked to tasks.
9 atomic answers
  • Persistent requirements [partial] The project wiki persists project knowledge across tasks. Sources: fractal:knowledge.
  • Human edits [supported] Markdown pages are editable by anyone. Sources: fractal:knowledge.
  • Agent edits [supported] Nodes edit wiki pages in REVIEW steps. Sources: fractal:seedsteps.
  • Revisions [partial] Git history only. Sources: fractal:commitpipe.
  • Approvals [unsupported] No approval rules for wiki pages. Sources: fractal:srch-review.
  • Later retrieval [supported] Later nodes read the wiki. Sources: fractal:knowledge.
  • Drift detection [unsupported] No drift detection (node diff covers template drift only). Sources: fractal:srch-review.
  • Review integration [unsupported] Review does not check against spec requirements. Sources: fractal:srch-review.

Sources: fractal:knowledge, fractal:seedsteps, fractal:commitpipe, fractal:srch-review

Coordination and automation

COORD-01

Parallel work

Sourced partial

Every node runs its own loop in its own tmux session or process group, so a tree iterates in parallel; no fixed global quota, only tree caps; node list shows status, spend and quiet flags.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • quotas: children, depth and descendants caps bound the tree; no global concurrency quota.
  • observed concurrency: No documented measurement of concurrent node counts.
5 atomic answers
  • Concurrent sessions [supported] Many nodes can be active at once, each in its own tmux session or detached process group. Sources: fractal:worktrees, fractal:readme.
  • Concurrent tasks [supported] Sibling nodes work on separate subtasks concurrently. Sources: fractal:worktrees.
  • Quotas [partial] children, depth and descendants caps bound the tree; no global concurrency quota. Sources: fractal:spawning.
  • Observed concurrency [partial] Width and descendant caps bound concurrency per tree, but no measured or vendor-reported count of simultaneously running nodes is published. Sources: fractal:spawning.
  • Status visibility [supported] node list shows status, detail, spend, limits and last-activity age with a ! for quiet active nodes; the TUI tree shows the same. Sources: fractal:operating, fractal:tui.

Sources: fractal:worktrees, fractal:readme, fractal:spawning, fractal:operating, fractal:tui

Agent cross-checked partial

Parents create and own child nodes; exclusive ownership comes from one worktree per node, the tree-wide worktree lock and slot accounting; no human assignment queue.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • human assignment: A human spawns nodes with a chosen agent; assignment of work to other humans does not exist.
  • claims: A node is bound to its branch and worktree.
  • queues: No work queue beyond spawn slots.
  • routing: Radio routes messages to channels and parents.
7 atomic answers
  • Human assignment [partial] A human spawns nodes with a chosen agent; assignment of work to other humans does not exist. Sources: fractal:gettingstarted.
  • Agent assignment [supported] Managers spawn and configure children. Sources: fractal:spawning.
  • Claims [partial] A node is bound to its branch and worktree. Sources: fractal:worktrees.
  • Queues [unsupported] No work queue beyond spawn slots. Sources: fractal:spawning.
  • Routing [partial] Radio routes messages to channels and parents. Sources: fractal:radio.
  • Duplicate prevention [supported] Unique node names, flock-serialised worktree add and slot checks prevent duplicate nodes. Sources: fractal:worktrees, fractal:spawning.
  • Ownership enforcement [supported] Scope checks refuse commits outside configured roots and merges refuse active or dirty targets. Sources: fractal:commitpipe, fractal:mergeguards.

Sources: fractal:gettingstarted, fractal:spawning, fractal:worktrees, fractal:radio, fractal:commitpipe, fractal:mergeguards

Agent cross-checked partial

Product-owned recursive orchestration: any node can spawn child nodes with their own agent, model and effort, message them over radio, read their reports and merge their branches; children keep status and retained results; cross-harness mixes allowed.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • authentication: Relies on the agent CLI logins; no extra auth.
12 atomic answers

Sources: fractal:gettingstarted, fractal:models, fractal:readme, fractal:radio, fractal:finishing, fractal:providers, fractal:spawning, fractal:nodeinit, fractal:operating, fractal:tui, fractal:transcripts, fractal:schema, fractal:durability

Agent cross-checked partial

Per-node interval and sleep settings re-run the loop on a fixed cadence while the process runs; no cron, event triggers or webhooks; client independence depends on where tmux runs.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • schedules: interval fixes iteration cadence (e.g. 1h) and sleep delays between iterations; no calendar schedules.
  • events: No event triggers.
  • recurring tasks: Interval loops recur until a finish condition or cap.
  • retries: Failed steps trigger a single re-dispatch for model drops and the loop continues per status rules.
8 atomic answers
  • Schedules [partial] interval fixes iteration cadence (e.g. 1h) and sleep delays between iterations; no calendar schedules. Sources: fractal:readme, fractal:nodeinit.
  • Events [unsupported] No event triggers. Sources: fractal:srch-trigger.
  • Recurring tasks [partial] Interval loops recur until a finish condition or cap. Sources: fractal:readme.
  • Completion conditions [supported] Completion requirements plus iteration, cost and time caps end runs. Sources: fractal:gettingstarted, fractal:budgets.
  • Scheduler location [supported] The node loop runs in a local tmux session or detached process group on the host. Sources: fractal:worktrees, fractal:readme.
  • Overlaps [supported] A node runs one loop; launching refuses an active node. Sources: fractal:statuses.
  • Retries [partial] Failed steps trigger a single re-dispatch for model drops and the loop continues per status rules. Sources: fractal:operating.
  • Client independence [supported] tmux sessions outlive the terminal; the host must stay up. Sources: fractal:operating.

Sources: fractal:readme, fractal:nodeinit, fractal:srch-trigger, fractal:gettingstarted, fractal:budgets, fractal:worktrees, fractal:statuses, fractal:operating

Agent cross-checked partial

Rich controls: stop, finish, pause (freeze and resume exact run), kill, approval gates, radio directives, retunes and chat; stalls surface as a quiet flag; no push notifications.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • notifications: No push notifications.
  • escalation: Children message parents over radio; escalation timing is not enforced.
  • chat terminal parity: Chat runs a separate agent turn and TUI attach is read-only.
10 atomic answers
  • Pause [supported] pause freezes the subtree and resume continues the same run. Sources: fractal:durability.
  • Stop [supported] stop ends after the step, finish after the iteration, kill immediately; history persists. Sources: fractal:operating, fractal:finishing.
  • Resume [supported] resume adopts the open run and re-enters the interrupted step. Sources: fractal:durability.
  • Steer [supported] Radio directives, NODE.md edits, chat and node update. Sources: fractal:operating.
  • Notifications [unsupported] No push notifications. Sources: fractal:srch-clients.
  • Pending decisions [supported] node pending lists steps waiting for approval; radio inbox lists questions. Sources: fractal:operating, fractal:guideloop.
  • Escalation [partial] Children message parents over radio; escalation timing is not enforced. Sources: fractal:radio.
  • Visible errors [supported] Failed rows, exit reasons and detail columns surface errors. Sources: fractal:statuses, fractal:operating.
  • Chat terminal parity [partial] Chat runs a separate agent turn and TUI attach is read-only. Sources: fractal:chat, fractal:tui.
  • Retained history [supported] Runs, iterations, steps and radio retained in SQLite. Sources: fractal:schema.

Sources: fractal:durability, fractal:operating, fractal:finishing, fractal:srch-clients, fractal:guideloop, fractal:radio, fractal:statuses, fractal:chat, fractal:tui, fractal:schema

Agent cross-checked partial

The TUI cockpit and node list show a whole tree with status, spend, limits, last activity, radio unread dots and nesting across the repository; no board, no per-epic dependency graph.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • fleet fixture: Catalog does not run the product.
  • dependencies: No dependency graph.
  • navigation errors: Failed nodes show exit detail in listings; TUI navigation to the failing step is not documented.
  • fixture mode: Catalog did not run a fixture.
8 atomic answers
  • Fleet fixture [unknown] Catalog does not run the product. Sources: fractal:tui.
  • Parent child [supported] Tree pane shows parent/child nodes. Sources: fractal:tui.
  • Dependencies [unsupported] No dependency graph. Sources: fractal:srch-team.
  • Attention [supported] Quiet-node flag, unread radio dots and node pending. Sources: fractal:operating, fractal:tui.
  • History [supported] node activity shows lifecycle events with cost, agent and model. Sources: fractal:operating.
  • Workload [supported] Per-node spend and limits. Sources: fractal:operating.
  • Navigation errors [partial] Failed nodes show exit detail in listings; TUI navigation to the failing step is not documented. Sources: fractal:operating.
  • Fixture mode [unknown] Catalog did not run a fixture. Sources: fractal:tui.

Sources: fractal:tui, fractal:srch-team, fractal:operating

Agent cross-checked partial

No mandatory preset: any directive in natural language, per-node agent/model/effort, live retunes (node update, NODE.md), and the TUI and radio show who is doing what; no live role editor.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • presets: Templates and seed steps preset configuration; none required.
  • live roles: Tree shows parents and children; roles are inferred from caps.
  • auth friction: Each agent CLI must already be logged in.
10 atomic answers
  • Quick task [supported] One leaf node with caps and a NODE.md is a quick task. Sources: fractal:gettingstarted.
  • Growing epic [supported] Raising max-children lets a leaf grow into a manager. Sources: fractal:operating.
  • Presets [partial] Templates and seed steps preset configuration; none required. Sources: fractal:nodeinit.
  • Natural language [supported] /fractal skill turns plain-language directives into node parameters. Sources: fractal:readme.
  • Agent configuration [supported] agent, provider, model and effort per node. Sources: fractal:models.
  • In run changes [supported] Caps, timeouts and NODE.md changes apply at the next iteration. Sources: fractal:operating.
  • Live roles [partial] Tree shows parents and children; roles are inferred from caps. Sources: fractal:tui.
  • Retained relationships [supported] Branch names and DB rows keep parentage. Sources: fractal:worktrees.
  • Discoverability [supported] fractal --help, docs site and wiki. Sources: fractal:docsite.
  • Auth friction [partial] Each agent CLI must already be logged in. Sources: fractal:providers.

Sources: fractal:gettingstarted, fractal:operating, fractal:nodeinit, fractal:readme, fractal:models, fractal:tui, fractal:worktrees, fractal:docsite, fractal:providers

Execution and reliability

Sourced partial

Local by default (tmux or headless processes on the host); runs on any POSIX host you control by installing there; no managed cloud or hosted control plane.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: local, self-hosted · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • byo remote: Nothing prevents installing on a VPS, but fractal ships no remote provisioning; durability docs mention moving a repository between hosts.
  • managed cloud: No vendor cloud.
  • hybrid: No hybrid mode.
  • provisioning: No provisioning.
12 atomic answers
  • Local [supported] Nodes run on the machine where fractal node start is run. Sources: fractal:gettingstarted.
  • Byo remote [partial] Nothing prevents installing on a VPS, but fractal ships no remote provisioning; durability docs mention moving a repository between hosts. Sources: fractal:durability.
  • Self hosted [supported] The whole tool runs on user hosts. Sources: fractal:readme.
  • Managed cloud [unsupported] No vendor cloud. Sources: fractal:srch-billing.
  • Hybrid [unsupported] No hybrid mode. Sources: fractal:srch-clients.
  • Provisioning [not-applicable] No provisioning. Sources: fractal:srch-clients.
  • Payer [supported] The user pays for agent usage and hardware. Sources: fractal:readme.
  • Resources [unsupported] No host sizing or resource guidance is published; a grep of the README and user-flow and design wiki finds none. Sources: fractal:srch-sizing.
  • Region [not-applicable] Not applicable. Sources: fractal:srch-clients.
  • Expiry [supported] No expiry; run and time caps are configurable. Sources: fractal:timebudgets.
  • Client disconnect [supported] tmux or detached sessions continue after the terminal closes. Sources: fractal:operating.
  • Other device continuation [partial] SSH to the same host works; there is no other-device client. Sources: fractal:operating.

Sources: fractal:gettingstarted, fractal:durability, fractal:readme, fractal:srch-billing, fractal:srch-clients, fractal:timebudgets, fractal:operating, fractal:srch-sizing

Agent cross-checked partial

One git worktree and branch per node (branch isolation plus scope checks); not a filesystem, network or secret sandbox, and the README warns agents run without permission prompts with your credentials.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: local · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • container: No container runtime support.
  • vm: No VM support.
  • os sandbox: Seed configs disable backend sandboxes (e.g. Codex danger-full-access).
  • filesystem: Scope limits commits, not filesystem reach.
12 atomic answers
  • Checkout [supported] Each node has its own checkout. Sources: fractal:worktrees.
  • Branch [supported] Branch named parent.child, merged with squash. Sources: fractal:worktrees, fractal:finishing.
  • Worktree [supported] git worktree per node in the repository worktrees folder. Sources: fractal:worktrees.
  • Container [unsupported] No container runtime support. Sources: fractal:srch-clients.
  • Vm [unsupported] No VM support. Sources: fractal:srch-clients.
  • Os sandbox [partial] Seed configs disable backend sandboxes (e.g. Codex danger-full-access). Sources: fractal:seedperm.
  • Filesystem [partial] Scope limits commits, not filesystem reach. Sources: fractal:commitpipe, fractal:readme.
  • Process [partial] Separate tmux sessions or process groups per node. Sources: fractal:durability.
  • Network [unsupported] No network boundary. Sources: fractal:readme.
  • Secrets [unsupported] Credentials come from the launching shell; no secret isolation. Sources: fractal:readme.
  • Code separation [supported] Per-node worktrees plus merge guards. Sources: fractal:mergeguards.
  • Security boundary [unsupported] README states the worktree isolates the branch, not the filesystem or network. Sources: fractal:readme.

Sources: fractal:worktrees, fractal:finishing, fractal:srch-clients, fractal:seedperm, fractal:commitpipe, fractal:readme, fractal:durability, fractal:mergeguards

Agent cross-checked partial

Strong crash and restart handling: pause parks a node as a process exit and resumes the same run; the healer reconciles dead loops; continue and resume re-enter interrupted steps; sessions are resumable; manual repair uses reconcile; multi-day runs are supported.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • expiry: No sandbox expiry.
  • context loss: Agent session context may be lost when no session id was recorded; wiki and plans persist.
  • duplicate actions: Interrupted steps are re-entered, which can repeat work; commits are discipline-checked.
12 atomic answers
  • Client disconnect [supported] Sessions live in tmux or detached groups and persist after the terminal closes. Sources: fractal:operating.
  • Worker crash [supported] A healer stamps crashed active nodes exited and closes open rows; node reconcile repairs. Sources: fractal:statuses, fractal:nodecmd.
  • Service restart [supported] No server exists; state is files and SQLite so a reboot costs only the loop process. Sources: fractal:durability.
  • Expiry [not-applicable] No sandbox expiry. Sources: fractal:srch-clients.
  • Transcript reload [supported] Provider transcripts resolve per session id. Sources: fractal:transcripts.
  • Process reconnect [supported] node attach re-attaches to tmux sessions. Sources: fractal:operating.
  • Task resume [supported] resume and continue adopt the open run and resume the agent session where recorded. Sources: fractal:durability.
  • State reconstruction [supported] Reconcile rebuilds status from rows and sessions. Sources: fractal:statuses.
  • Context loss [partial] Agent session context may be lost when no session id was recorded; wiki and plans persist. Sources: fractal:durability, fractal:transcripts.
  • Duplicate actions [partial] Interrupted steps are re-entered, which can repeat work; commits are discipline-checked. Sources: fractal:durability.
  • Manual repair [supported] node reconcile, reap and delete exist. Sources: fractal:nodecmd.
  • Multi day continuity [supported] Budgets arm per run, pauses credit back time and runs chain across restarts. Sources: fractal:durability, fractal:timebudgets.

Sources: fractal:operating, fractal:statuses, fractal:nodecmd, fractal:durability, fractal:srch-clients, fractal:transcripts, fractal:timebudgets

Agent cross-checked partial

Warms the git-ignored build cache for new worktrees and uses node scripts for setup; no snapshots, service orchestration, port allocation or secret injection.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • dependencies: Scripts and steps run by agents install dependencies; fractal documents cache warming for new worktrees.
  • snapshots: No snapshots.
  • services: No service orchestration.
  • ports: No port allocation.
10 atomic answers

Sources: fractal:worktrees, fractal:srch-clients, fractal:readme, fractal:gettingstarted, fractal:mergeguards

Agent cross-checked partial

Comprehensive enforced limits: per-run iteration, depth, children, descendants, time (run, iteration, step), cost (run, iteration, step) with reserve wind-down and step watchdogs; non-enforcing backends warn only.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • token limits: Token use is bounded through cost caps; there is no separate token cap.
  • retries: A step off its pinned model gets one re-dispatch; budget-ended runs re-arm only with --continue --max-cost.
  • provider failures: API retry backoff is a timed pause and a no-progress watchdog for Claude.
8 atomic answers
  • Time limits [supported] timeout, iter-timeout and step-timeout with pause credit-back. Sources: fractal:timebudgets.
  • Turn limits [supported] max-iters caps iterations per run. Sources: fractal:readme.
  • Token limits [partial] Token use is bounded through cost caps; there is no separate token cap. Sources: fractal:budgets.
  • Spend limits [supported] max-cost, max-iter-cost and max-step-cost with reserve-budget. Sources: fractal:budgets.
  • Timeouts [supported] Per-run, iteration and step timeouts. Sources: fractal:timebudgets.
  • Retries [partial] A step off its pinned model gets one re-dispatch; budget-ended runs re-arm only with --continue --max-cost. Sources: fractal:operating, fractal:budgets.
  • Provider failures [partial] API retry backoff is a timed pause and a no-progress watchdog for Claude. Sources: fractal:providers.
  • Enforcement [supported] Enforced by the loop and per-step budget flags; unenforceable per-step caps are warn-only and documented. Sources: fractal:budgets.

Sources: fractal:timebudgets, fractal:readme, fractal:budgets, fractal:operating, fractal:providers

Agent cross-checked partial

Central SQLite database of runs, iterations, steps, costs and signals with node status, activity, cost and time commands; end reasons and detail columns; quiet-node flags; no usage export besides CSV/JSON listings or benchmark numbers.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • traces: Step and event rows in the database serve as traces; no OpenTelemetry.
  • performance method: No benchmark method; ADEMark does not list this product.
  • responsiveness: The TUI polls with mtime change detection and off-thread snapshots; no measurement.
13 atomic answers
  • Logs [supported] Agent logs, headless.log, tmux sessions and transcripts. Sources: fractal:readme, fractal:transcripts.
  • Traces [partial] Step and event rows in the database serve as traces; no OpenTelemetry. Sources: fractal:schema.
  • Failure reasons [supported] Exit reasons, model drop and failure detail on rows and listings. Sources: fractal:operating, fractal:statuses.
  • Usage export [supported] Listing commands output CSV or JSON. Sources: fractal:cliNode.
  • Task stats [supported] node cost spent and breakdown per node. Sources: fractal:operating.
  • Agent stats [supported] Activity rows show agent, model and effort. Sources: fractal:operating.
  • Project stats [supported] Tree-wide totals through the root node. Sources: fractal:operating.
  • Time stats [supported] node time commands and activity timestamps. Sources: fractal:timebudgets.
  • Failure status [supported] failed, exited and detail columns. Sources: fractal:statuses.
  • Approval status [supported] node pending lists gated steps. Sources: fractal:operating.
  • Reconnect consistency [supported] One status vocabulary shared by status file and rows with a healer. Sources: fractal:statuses.
  • Performance method [unsupported] No benchmark method; ADEMark does not list this product. Sources: fractal:readme.
  • Responsiveness [partial] The TUI polls with mtime change detection and off-thread snapshots; no measurement. Sources: fractal:tui.

Sources: fractal:readme, fractal:transcripts, fractal:schema, fractal:operating, fractal:statuses, fractal:cliNode, fractal:timebudgets, fractal:tui

Agent cross-checked partial

Per-step cost ledger with roll-ups by iteration, run and subtree across harnesses, null for unknowable cost, pricing from the LiteLLM table; subscription allowance is not modelled; CSV/JSON output; no billing reconciliation.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • subscription allowance: Subscription allowance is not modelled; prices come from API token tables.
  • provider reconciliation: No reconciliation with provider bills.
  • compute cost: No compute cost.
  • refresh delay: Active steps count only flushed cost.
14 atomic answers
  • Task cost [supported] Per-node run spend including descendants. Sources: fractal:measurement.
  • Session cost [supported] Per-step and per-iteration costs. Sources: fractal:measurement.
  • Child cost [supported] Subtree cost chained from descendant runs. Sources: fractal:measurement.
  • Epic cost [supported] A manager node total covers its subtree. Sources: fractal:measurement.
  • Harness aggregation [supported] One ledger across claude, codex, grok, opencode and omp with per-backend cost modes. Sources: fractal:providers, fractal:measurement.
  • Billed vs estimated [supported] Backends that report cost are used; others are priced from tokens; unknowable is null. Sources: fractal:measurement, fractal:pricing.
  • Tokens [supported] Token usage is priced into rows. Sources: fractal:pricing.
  • Subscription allowance [unsupported] Subscription allowance is not modelled; prices come from API token tables. Sources: fractal:pricing.
  • Provider reconciliation [unsupported] No reconciliation with provider bills. Sources: fractal:measurement.
  • Compute cost [unsupported] No compute cost. Sources: fractal:measurement.
  • Refresh delay [partial] Active steps count only flushed cost. Sources: fractal:budgets.
  • Alerts [partial] Reserve window and caps stop or steer rather than alert. Sources: fractal:budgets.
  • Export [supported] cost commands output CSV/JSON. Sources: fractal:cliNode.
  • Drilldown [supported] cost breakdown per node, activity per step. Sources: fractal:operating.

Sources: fractal:measurement, fractal:providers, fractal:pricing, fractal:budgets, fractal:cliNode, fractal:operating

Agent cross-checked partial

Tree caps and slot accounting, a worktree lock, merge lock and build cache warming; no CPU/RAM limits, queues for work or check deduplication.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • queues: Merges queue behind a repo-wide lock; no work queue.
  • cpu ram: No CPU or RAM limits.
  • backpressure: Spawn caps refuse new children; no load-based backpressure.
  • host awareness: No host awareness.
12 atomic answers

Sources: fractal:spawning, fractal:mergeguards, fractal:srch-clients, fractal:srch-review, fractal:finishing, fractal:statuses, fractal:durability, fractal:budgets

Human collaboration and control

Agent cross-checked partial

Single-operator tool: no accounts, presence, co-prompting or shared sessions; collaboration is through shared git and the wiki.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • visibility: Anyone with host access sees tmux and the TUI; no sharing feature.
  • discussion: Radio threads are between nodes and the user node.
  • comments: No human comments feature.
  • presence: No presence.
11 atomic answers

Sources: fractal:tui, fractal:srch-team, fractal:radio, fractal:readme, fractal:operating

Agent cross-checked unsupported

No roles, membership, SSO or provisioning; the user node is the only human identity.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
9 atomic answers

Sources: fractal:srch-team, fractal:readme

Agent cross-checked partial

Default is full access: seeded configs bypass approvals (Claude bypassPermissions, Codex danger-full-access, Grok always-approve, OpenCode --auto, omp --yolo); only parent approval gates on steps and commit scope are product-enforced.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • command: Agent command prompts are disabled by the seeded configs.
  • tool: Tool prompts are disabled by default.
  • network: No network approvals.
  • secret: No secret approvals.
14 atomic answers

Sources: fractal:seedperm, fractal:readme, fractal:guideloop, fractal:finishing, fractal:operating, fractal:spawning, fractal:commitpipe, fractal:mergeguards

Agent cross-checked partial

Everything is recorded in the local SQLite database and git history (runs, steps, costs, radio) with sender attribution for nodes; local files are mutable and no retention or integrity model is defined.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • approvals: Approvals are recorded in lifecycle rows.
  • decisions: Plans and post-mortems capture decisions.
  • cross user persistence: No multiple users.
  • mutability: Local database and files can be edited; unsend exists for radio.
11 atomic answers

Sources: fractal:operating, fractal:schema, fractal:guideloop, fractal:commitpipe, fractal:radio, fractal:plans, fractal:seedsteps, fractal:srch-team, fractal:cliNode

Sourced partial

Review is through git and the loop REVIEW step; fractal finish and merge are separated for operator review, but there is no diff UI, comments or request-changes flow.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
Not separately cross-checked
  • pending reviews: node pending lists gated steps; completed nodes await merge.
  • change understanding: Plans, post-mortems and radio reports explain changes.
  • evidence navigation: Transcripts and activity by iteration.
  • comments: No review comments.
13 atomic answers

Sources: fractal:operating, fractal:finishing, fractal:plans, fractal:transcripts, fractal:srch-review, fractal:tui, fractal:cliNode, fractal:tuiwidgets

Agent cross-checked partial

A second person with host or repository access can read the same branches, worktrees, database and radio, continue a paused node and chat with its session; there is no attribution or ownership transfer.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • ongoing takeover: Anyone with host access can resume or steer; no formal takeover.
  • decisions: Plans and radio.
  • permissions: No permission model.
  • ownership: No ownership.
12 atomic answers

Sources: fractal:durability, fractal:operating, fractal:transcripts, fractal:plans, fractal:radio, fractal:commitpipe, fractal:srch-team

Verification and delivery

Agent cross-checked partial

Retains commits, plan files with post-mortems, wiki pages, transcripts and database rows per iteration; no screenshot, recording or preview gallery.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • screenshots: No screenshot feature.
  • recordings: No recordings.
  • previews: No previews.
  • test outputs: Agent step output in transcripts; no test result store.
13 atomic answers

Sources: fractal:commitpipe, fractal:plans, fractal:knowledge, fractal:srch-review, fractal:transcripts, fractal:seedsteps, fractal:schema, fractal:radio

Agent cross-checked partial

The commit pipeline runs scope check, wiki lint and project lint every iteration and refuses out-of-scope changes; completion requirements and a self REVIEW step are prompt-level; no CI or independent reviewer gate.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • tests: Agents run tests as part of steps; no product-enforced test gate.
  • types: Only via the project lint configuration.
  • ci: No CI response.
  • independent review: The REVIEW step is the same agent reviewing its own diff.
11 atomic answers

Sources: fractal:seedsteps, fractal:commitpipe, fractal:srch-pr, fractal:srch-review, fractal:nodeinit

Agent cross-checked partial

Branch and worktree per node, enforced commit subjects, push to origin after each commit, squash merge up the tree with guards and conflict recovery; no PR creation or CI loop.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • pull requests: No pull request creation.
  • comments: No PR comments.
  • ci response: No CI response.
  • rebase: Merge-base advance after squash converges nodes; no rebase UI.
9 atomic answers
  • Branches [supported] One branch per node named parent.child. Sources: fractal:worktrees.
  • Worktrees [supported] One worktree per node. Sources: fractal:worktrees.
  • Commits [supported] fractal commit composes subjects <branch>: iteration run.iter (message). Sources: fractal:commitpipe.
  • Pull requests [unsupported] No pull request creation. Sources: fractal:srch-pr.
  • Comments [unsupported] No PR comments. Sources: fractal:srch-pr.
  • Ci response [unsupported] No CI response. Sources: fractal:srch-pr.
  • Rebase [partial] Merge-base advance after squash converges nodes; no rebase UI. Sources: fractal:finishing.
  • Conflicts [supported] Merge conflict restore, verdicts and continue-after-hand-resolution are documented. Sources: fractal:mergeguards.
  • Product state [supported] Status, merge locks and recorded run state. Sources: fractal:statuses, fractal:mergeguards.

Sources: fractal:worktrees, fractal:commitpipe, fractal:srch-pr, fractal:finishing, fractal:mergeguards, fractal:statuses

Agent cross-checked partial

The operator runs finish then merge; the user node pushes its own base branch; no release or deploy; merge guards check exact node and target state.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • approve: Operator review precedes merge; parent approves gated steps.
  • release: No release feature.
  • deploy: No deploy feature.
  • exact revision: Merge guards check node and target state at merge time.
6 atomic answers

Sources: fractal:finishing, fractal:guideloop, fractal:nodecmd, fractal:srch-pr, fractal:mergeguards, fractal:srch-team

Agent cross-checked partial

Iteration commits carry run.iter subjects and the database links steps to sessions; merge records a two-parent advance commit; no PR, build or deploy links and no rollback command beyond git.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • pr links: No PRs.
  • build links: No build links.
  • deployment links: No deployments.
  • delivery status: completed vs exited and merged state; no delivery status.
9 atomic answers

Sources: fractal:commitpipe, fractal:plans, fractal:srch-pr, fractal:finishing, fractal:schema, fractal:srch-review

Agent cross-checked partial

No batch review queue: node list and pending show finished nodes and gated steps; merges are serialised; no risk filters, grouped findings or approvals of exact revisions.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • review queue: node list shows completed nodes awaiting merge; node pending lists approvals.
  • summaries: Post-mortems and radio reports.
  • grouping: The tree groups children under parents.
  • risk size filters: None.
12 atomic answers

Sources: fractal:operating, fractal:seedsteps, fractal:radio, fractal:tui, fractal:srch-review, fractal:plans, fractal:mergeguards, fractal:finishing

Ownership, privacy and economics

Agent cross-checked partial

Apache-2.0 for the fractal package and its sibling plasma-wiki, plugins and templates repositories; no closed components or hosted edition; pinned v1.4.0 (5e1c65c).

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • server license: No server component.
  • hosted extensions: No hosted service.
  • hosted parity: No hosted edition.
6 atomic answers

Sources: fractal:license, fractal:pyproject, fractal:srch-clients, fractal:srch-billing, fractal:repoapi, fractal:pluginsrepo, fractal:wikirepo, fractal:changelog

Agent cross-checked partial

Fully local: state is git worktrees, a SQLite database and markdown wiki; everything is portable git plus files; no vendor account.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • vendor dependencies: Needs agent CLIs and fetches the LiteLLM price table from GitHub.
  • import: Repository clone plus fractal state; templates import seeds.
  • cancellation: No account.
8 atomic answers

Sources: fractal:readme, fractal:pricingsrc, fractal:cliNode, fractal:schema, fractal:nodeinit, fractal:srch-billing, fractal:durability

Agent cross-checked partial

Data stays on the host; fractal sends nothing to Plasma (no product telemetry); it fetches a LiteLLM price table from GitHub and sends prompts only to whatever provider the chosen agent CLI uses.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • retention: No retention policy is defined; files stay until deleted.
  • training: No vendor model.
  • subprocessors: Only the user-chosen model providers and GitHub for the price table.
  • telemetry disclosure: extending.md states the package ships no telemetry hooks beyond an extension point; the README does not discuss telemetry.
15 atomic answers

Sources: fractal:readme, fractal:srch-telemetry, fractal:providers, fractal:schema, fractal:commitpipe, fractal:nodecmd, fractal:pricingsrc, fractal:extending

Agent cross-checked partial

Free Apache-2.0 software with no seats, plans or usage fees; model and compute costs are the user's.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Free open source · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • currency: No price.
  • interval: No price.
  • included usage: No metering.
  • credits: No credits.
12 atomic answers

Sources: fractal:srch-billing, fractal:budgets, fractal:readme

Agent cross-checked partial

ADE fixed cost is zero; scenarios depend on agent usage which fractal can cap and report; no vendor scenario pricing.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • one person: ADE $0 plus agent usage, bounded by max-cost.
  • two people: No collaboration pricing; each runs their own host.
  • five people: Same.
  • task assumptions: No vendor scenario.
11 atomic answers

Sources: fractal:budgets, fractal:srch-team, fractal:srch-billing, fractal:measurement, fractal:pricing

Agent cross-checked partial

Generally available open-source releases (1.4.0 on 2026-10-25; tags only, no GitHub release page), active changelog and issues; support is through GitHub; no response commitments.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • support: GitHub issues.
  • response commitments: None stated.
  • status history: No status page.
  • deprecation: Breaking changes are listed per release.
8 atomic answers

Sources: fractal:changelog, fractal:pyproject, fractal:license, fractal:readme, fractal:repoapi, fractal:schema

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Agent cross-checked partial

Free to use completely (Apache-2.0), no card or caps from fractal; agent subscriptions or API usage are separate.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • trial: Not applicable.
  • credits trial: Not applicable.
  • paid only: None.
  • early access: None.
10 atomic answers

Sources: fractal:license, fractal:srch-billing, fractal:readme, fractal:budgets

Agent cross-checked partial

Transparent: free software, no pricing units, included limits, overages or markups.

Scope
Surfaces: fractal CLI (Typer) driving tmux or headless agent loops · Version: v1.4.0 (commit 5e1c65c, 2026-10-25) · Plan: Open source (Apache-2.0) · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-16 (6 days old)
Agent cross-check
2026-11-17
  • units: No pricing.
  • included limits: None.
  • overages: None.
  • compute markup: None.
9 atomic answers

Sources: fractal:srch-billing, fractal:license

Sources

fractal:pyproject

fractal pyproject.toml

plasma-fractal 1.4.0, Apache-2.0, Python >=3.12, deps textual/rich/typer/jinja2/plasma-wiki; classifier Operating System :: POSIX only.

Kind
source-inspected
Locator
[project] version, requires-python, dependencies, classifiers
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
pyproject.toml
fractal:operating

fractal wiki: operating

node list/status/activity/cost, TUI cockpit, tmux attach, radio feed; steering through radio directives, NODE.md edits, chat, retunes, approvals and lifecycle verbs.

Kind
documented
Locator
Monitoring; Steering
Source date
Not stated
Retrieved
2026-11-16
fractal:durability

fractal wiki: durability

Pause parks the loop as a full process exit keeping run, iteration and step rows open so resume continues the same run; survives reboot or host migration.

Kind
documented
Locator
Paused is active-like; Park semantics
Source date
Not stated
Retrieved
2026-11-16
fractal:tui

fractal wiki: TUI actions

The TUI cockpit is read-only by construction except radio send/reply/react/save, chat and read-only tmux attach; lifecycle changes stay on the CLI.

Kind
documented
Locator
Radio writes; Session viewing; What the cockpit never does
Source date
Not stated
Retrieved
2026-11-16
fractal:cliNode

fractal docs: node CLI

fractal node CLI conventions and reference: CSV or --json output, exit codes, short names, durations and costs.

Kind
documented
Locator
Conventions; command reference
Source date
Not stated
Retrieved
2026-11-16
fractal:nodecmd

fractal fractal/cli/cmd/node.py

Typer commands for init, start, finish, stop, pause, resume, kill, merge, delete, attach, status, list, activity, approve, pending, chat, update, scope.

Kind
source-inspected
Locator
def node_init, node_start, node_finish, node_stop, node_pause, node_resume, node_kill, node_merge, node_chat, node_approve, node_update
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/cli/cmd/node.py
fractal:processsrc

fractal fractal/util/process.py

Process sweeps use ps and lsof on macOS and /proc on Linux.

Kind
source-inspected
Locator
process listing macOS and Linux
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/util/process.py
fractal:schema

fractal fractal/core/schema.sql

Local SQLite schema for runs, iterations, steps, messages, channels and costs.

Kind
source-inspected
Locator
CREATE TABLE statements
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/core/schema.sql
fractal:pluginsrepo

plasma-ai/plugins README

Plugin marketplace repository (Apache-2.0) distributing the fractal and wiki skills for Claude Code and Codex.

Kind
documented
Locator
plugin table; Claude Code; Codex
Source date
Not stated
Retrieved
2026-11-16
fractal:srch-clients

Bounded search: clients

No web server, desktop app, mobile app or editor extension; the interface is a CLI and a Textual terminal UI.

Kind
source-inspected
Locator
grep -Ei for electron, tauri, react, flask, fastapi, http server, websocket, vscode, jetbrains, ios, android over fractal/, docs/, README, pyproject
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
.
fractal:readme

fractal README

Trees of autonomous agent loops, each node in its own git worktree with hard caps (iterations, depth, children, cost, time); five agent backends; TUI over a local SQLite database; nodes run without permission prompts by default.

Kind
documented
Locator
intro; WARNING; Installation; Usage; parameter list
Source date
Not stated
Retrieved
2026-11-16
fractal:providers

fractal wiki: agent providers

Five backends (claude, codex, grok, opencode, omp) registered by base command; routes such as OpenRouter; register() as an in-process extension point.

Kind
documented
Locator
Supported backends; The registry; Provider routes
Source date
Not stated
Retrieved
2026-11-16
fractal:extending

fractal wiki: extending agents

Embedding applications register or override agent backends in process or through a per-tree deployment hook file; the package itself ships no telemetry.

Kind
documented
Locator
extension seam; deployment hook file; telemetry
Source date
Not stated
Retrieved
2026-11-16
fractal:agentimpl

fractal fractal/impl

One backend module per supported agent CLI.

Kind
source-inspected
Locator
claude.py codex.py grok.py omp.py opencode.py
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/impl
fractal:pricing

fractal wiki: pricing

Token usage becomes dollars from a cached LiteLLM price table; refresh and staleness semantics; unpriced models disclosed.

Kind
documented
Locator
LiteLLM price table; unpriced model contract
Source date
Not stated
Retrieved
2026-11-16
fractal:srch-billing

Bounded search: billing

No billing or licence gating code.

Kind
source-inspected
Locator
grep -Ei for stripe, license key, plan, pricing page over fractal/ and README
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
.
fractal:srch-terms

README.md

No provider terms, subscription-plan or rate-limit guidance appears in the README, wiki or docs; the only subscription hits are radio channel subscriptions.

Kind
source-inspected
Locator
grep -rniE "terms of service|rate limit|subscription plan" README.md wiki docs
Source date
Not stated
Retrieved
2026-11-17
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
README.md
fractal:worktrees

fractal wiki: worktrees

One git worktree per node in a per-node directory named by its branch under the repository worktrees folder; a child forks the parent branch tip; tree-wide flock serialises worktree add and spawn caps.

Kind
documented
Locator
Where worktrees live; Forking a child
Source date
Not stated
Retrieved
2026-11-16
fractal:gettingstarted

fractal wiki: getting started

Install via pip, run fractal install for skills, fractal init on a git branch, fractal node init with budgets and scope, author NODE.md instructions and completion requirements, launch in tmux (or --headless).

Kind
documented
Locator
Install; fractal init; fractal node init; NODE.md
Source date
Not stated
Retrieved
2026-11-16
fractal:commitsrc

fractal fractal/core/commit.py

Push to origin after each commit unless the node is local; missing origin skips push with a notice.

Kind
source-inspected
Locator
_push, push unless local
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/core/commit.py
fractal:srch-pr

Bounded search: pr

No pull request creation or management: delivery is squash-merge into a local target branch plus git push to origin.

Kind
source-inspected
Locator
grep -Ei for pull request, gh pr, octokit, github api over fractal/ and wiki/
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
.
fractal:changelog

fractal CHANGELOG.md

Keep-a-Changelog history; 1.4.0 dated 2026-10-25; [Unreleased] empty at the pinned commit; breaking changes allowed in minors.

Kind
documented
Locator
[1.4.0] - 2026-10-25; [Unreleased]
Source date
Not stated
Retrieved
2026-11-16
fractal:srch-team

Bounded search: team

No accounts, roles, SSO or multi-user model; the only identity is the local user node.

Kind
source-inspected
Locator
grep -Ei for login, auth, user account, role, permission model, sso, saml over fractal/ and wiki/
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
.
fractal:srch-trigger

Bounded search: trigger

Only per-node interval and sleep settings and signals; no cron schedules, webhooks or repository event triggers.

Kind
source-inspected
Locator
grep -Ei for cron, schedule, webhook, github action trigger over fractal/ and wiki/
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
.
fractal:srch-mcp

Bounded search: mcp

Mentions are of agent MCP configuration passed through to the backend CLIs; fractal exposes no MCP server.

Kind
source-inspected
Locator
grep -Ei for mcp over fractal/, docs, wiki
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
.
fractal:pypi

plasma-fractal on PyPI

Package plasma-fractal published on PyPI (README names it as the installation route).

Kind
documented
Locator
project page
Source date
Not stated
Retrieved
2026-11-16
fractal:docsite

fractal documentation site

Sphinx documentation site named in the README.

Kind
documented
Locator
home
Source date
Not stated
Retrieved
2026-11-16
fractal:nodeinit

fractal wiki: node init

Complete node initialisation reference: caps, scope, agent, model, effort, timeouts, interval, sleep, wait, budgets, sync, detached, local.

Kind
documented
Locator
node init flags and config keys
Source date
Not stated
Retrieved
2026-11-16
fractal:seedperm

fractal fractal/_node/agents/claude/settings.json

Seed Claude config sets defaultMode bypassPermissions; the Codex seed sets sandbox_mode danger-full-access and Grok permission_mode always-approve.

Kind
source-inspected
Locator
permissions.defaultMode
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/_node/agents/claude/settings.json
fractal:radio

fractal wiki: radio

Inter-node messaging in fractal/core/radio.py: channels, send/post/reply, subscriptions, read receipts, reactions, saved messages, all in the central database.

Kind
documented
Locator
Radio is fractal inter-node messaging
Source date
Not stated
Retrieved
2026-11-16
fractal:plans

fractal wiki: plans

fractal plan init/list create markdown plan files per iteration named timestamp-run.iter-name.md.

Kind
documented
Locator
Creating plans; Listing plans
Source date
Not stated
Retrieved
2026-11-16
fractal:commitpipe

fractal wiki: commit pipeline

fractal commit runs scope check, wiki index refresh, lint, stage, commit and push (unless --local) as one operation with enforced subject discipline.

Kind
documented
Locator
single path into git history; scope, refresh, lint
Source date
Not stated
Retrieved
2026-11-16
fractal:seedsteps

fractal fractal/_node/steps/03-REVIEW.md

Seed loop steps PREPARE, PLAN, EXECUTE, REVIEW, COMMIT; REVIEW has the agent inspect its own diff and update memory.

Kind
source-inspected
Locator
Review step
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/_node/steps/03-REVIEW.md
fractal:finishing

fractal wiki: finishing

finish ends a node after its iteration and lands completed or exited by reason; merge squash-merges the node branch into its merge target after operator review.

Kind
documented
Locator
The finish signal; What merge does
Source date
Not stated
Retrieved
2026-11-16
fractal:statuses

fractal wiki: statuses

One status vocabulary across node status file and database rows (idle, active, paused, completed, exited, failed, retired); a healer reconciles crashed loops.

Kind
documented
Locator
One status set, two homes
Source date
Not stated
Retrieved
2026-11-16
fractal:spawning

fractal wiki: tree limits

Width, depth and descendants caps plus a spawn-time budget check enforced without agent cooperation.

Kind
documented
Locator
three caps and the budget check
Source date
Not stated
Retrieved
2026-11-16
fractal:guideloop

fractal docs: loop guide

Step frontmatter requires_approval: true makes a step wait for the parent to run fractal node approve; SYNC runs between approval windows.

Kind
documented
Locator
Approval gates; SYNC
Source date
Not stated
Retrieved
2026-11-16
fractal:wikiroot

fractal wiki/_index.md

First-party descriptive wiki shipped in the repository documenting architecture, configuration, design, features and operator journeys.

Kind
documented
Locator
index of architecture, configuration, design, features, user_flow
Source date
Not stated
Retrieved
2026-11-16
fractal:knowledge

fractal wiki: knowledge stores

Project wiki and per-node memory implemented with the plasma-wiki CLI as shared knowledge bases nodes read and grow.

Kind
documented
Locator
knowledge stores
Source date
Not stated
Retrieved
2026-11-16
fractal:wikirepo

plasma-ai/wiki README

plasma-wiki: indexed knowledge-base CLI that fractal depends on for project and node memory (Apache-2.0).

Kind
documented
Locator
overview
Source date
Not stated
Retrieved
2026-11-16
fractal:srch-review

Bounded search: review

No code review interface; node diff reports template drift only and review happens in git.

Kind
source-inspected
Locator
grep -Ei for review ui, diff view, approve change, request changes over fractal/tui and fractal/cli
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
.
fractal:srch-image

fractal/impl/claude.py

No image or attachment input path exists in fractal; prompts are text, and the few hits are unrelated (provisional_errors, worktree and template wording).

Kind
source-inspected
Locator
grep -rniE "image|multimodal|vision|attachment" fractal/
Source date
Not stated
Retrieved
2026-11-17
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/impl/claude.py
fractal:mergeguards

fractal wiki: merge guards

Merge refuses while the node or target is active, on dirty target worktrees and untracked-file or footprint conflicts; merges are serialised by a repo-wide lock.

Kind
documented
Locator
refusals; repo-wide merge lock; paused nodes
Source date
Not stated
Retrieved
2026-11-16
fractal:models

fractal wiki: models and effort

Per-node model and reasoning-effort overrides; Claude and Codex seeds pin effort high.

Kind
documented
Locator
model and effort overrides
Source date
Not stated
Retrieved
2026-11-16
fractal:transcripts

fractal wiki: transcripts

Provider session transcripts resolved per agent through the node sessions facade; session ids stored on step and iteration rows.

Kind
documented
Locator
Resolution
Source date
Not stated
Retrieved
2026-11-16
fractal:budgets

fractal wiki: cost budgets

max_cost per run (subtree-shared), max_iter_cost, max_step_cost; reserve window steers wind-down; non-enforcing agents warn only.

Kind
documented
Locator
three cap tiers; subtree-shared; Reserve window
Source date
Not stated
Retrieved
2026-11-16
fractal:chat

fractal wiki: chat

fractal node chat sends one prompt to a node agent in a fresh, forked or resumed session without writing cost rows or disturbing the loop.

Kind
documented
Locator
conversational door onto a node
Source date
Not stated
Retrieved
2026-11-16
fractal:timebudgets

fractal wiki: time budgets

Run, iteration and step timeouts with pause credit-back so frozen time does not charge deadlines.

Kind
documented
Locator
run, iteration and step timeout tiers; pause credit-back
Source date
Not stated
Retrieved
2026-11-16
fractal:srch-sizing

README.md

No host sizing or resource guidance is published in the README or user-flow and design wiki pages.

Kind
source-inspected
Locator
grep -rniE "RAM|memory usage|cpu|disk space" README.md wiki/user_flow wiki/design
Source date
Not stated
Retrieved
2026-11-17
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
README.md
fractal:measurement

fractal wiki: cost measurement

Per-step cost rows in the central database roll up through iterations, runs and descendants; unknowable cost is stored null and disclosed, not zero.

Kind
documented
Locator
per-step ledger rows; unknowable cost recorded as null
Source date
Not stated
Retrieved
2026-11-16
fractal:tuiwidgets

fractal/tui/widgets.py

The cockpit panes are drag-resizable and re-clamp on terminal resize; on a terminal too small for both bounds the floor wins. No narrow-terminal layout is documented.

Kind
source-inspected
Locator
shell resize edge; geometry path re-clamps on terminal resize
Source date
Not stated
Retrieved
2026-11-17
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/tui/widgets.py
fractal:license

fractal LICENSE

Apache License 2.0 for the repository.

Kind
source-inspected
Locator
whole file
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
LICENSE
fractal:repoapi

GitHub repository metadata

793 stars on plasma-ai/fractal, Apache-2.0, default branch main; latest tag v1.4.0 (commit 5e1c65c, 2026-10-25); no GitHub releases published.

Kind
documented
Locator
stargazers_count, license, pushed_at
Source date
Not stated
Retrieved
2026-11-16
fractal:pricingsrc

fractal fractal/core/pricing.py

Fetches the LiteLLM model price table from raw.githubusercontent.com for cost computation.

Kind
source-inspected
Locator
LiteLLM raw.githubusercontent.com URL
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
fractal/core/pricing.py
fractal:srch-telemetry

Bounded search: telemetry

No product telemetry; the only outbound fetch of its own is the LiteLLM price table; the Codex seed config disables the agent analytics.

Kind
source-inspected
Locator
grep -Ei for telemetry, analytics, sentry, posthog, usage report over fractal/, wiki/, README
Source date
Not stated
Retrieved
2026-11-16
Commit
5e1c65c0a5dc367d3d4f223a997b5f010d568722
Path
.

Comparisons with fractal

Compare fractal with any other product on adecomparison.com.