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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Implementation links [supported] Plan filenames and commit subjects carry the run.iter reference so plans link to commits. Sources: fractal:plans, 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.
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.
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.
Skills [supported] Seeded skills fractal, memory, radio and wiki; installable to user or project skill directories. Sources: fractal:pluginsrepo, fractal:readme.
Memory [supported] Per-node memory pages updated every REVIEW step and shared project learnings in the wiki. Sources: fractal:seedsteps, fractal:knowledge.
Scope [supported] Node memory is per node; the project wiki is shared across the tree. Sources: fractal:knowledge.
Provenance [partial] Wiki pages carry front matter with created/updated and sources fields; commits tag the iteration. Sources: fractal:wikiroot, fractal:commitpipe.
Deletion [supported] Pages and nodes can be deleted with git and node delete. Sources: fractal:nodecmd.
Freshness [partial] wiki lint and index regeneration at commit keep structure fresh; no automatic staleness scoring. Sources: fractal:seedsteps, fractal:knowledge.
Takeover continuity [supported] Memory and wiki are committed files that a new session or person reads. Sources: fractal:knowledge.
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
Code search [partial] Agent CLIs search code themselves; fractal adds wiki search through the plasma-wiki skill. Sources: fractal:knowledge, fractal:wikirepo.
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.
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.
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
Shared ids [supported] Humans and agents use the same node branches and message UUIDs. Sources: fractal:worktrees, fractal:radio.
Read [supported] Agents run node list/status/activity and radio read. Sources: fractal:operating.
Create [supported] A manager node spawns children with node init (agent skill). Sources: fractal:spawning, fractal:readme.
Update [supported] Managers retune children with node update. Sources: fractal:operating.
Claim [unsupported] No claim mechanism; each node owns its own worktree. Sources: fractal:worktrees.
Assign [partial] A parent chooses agent, model and effort when it spawns a child. Sources: fractal:nodeinit.
State changes [supported] Nodes finish themselves and managers can stop, pause, resume or kill children. Sources: fractal:finishing.
Dependencies [unsupported] No dependency fields. Sources: fractal:srch-team.
Children [supported] Parent/child nodes are first class. Sources: fractal:spawning.
Results [supported] Results are committed work plus radio reports and finish reasons. Sources: fractal:finishing, fractal:radio.
Human visibility [supported] node list, radio feed and the TUI show agent actions. Sources: fractal:operating, fractal:tui.
Attribution [supported] Messages record sender and session; rows record node, agent, model and effort. Sources: fractal:radio, fractal:operating.
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.
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.
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.
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
Roles [supported] User (root) node, manager nodes and leaf nodes; all zero caps makes a leaf. Sources: fractal:gettingstarted.
Model harness effort [supported] Per-node --agent, --model and --effort, inherited by default. Sources: fractal:models, fractal:readme.
Messages [supported] Radio send/post/reply with channels, subjects and priorities. Sources: fractal:radio.
Results return [supported] Children finish with a reason, commit work for merge and post reports; parents read feeds. Sources: fractal:finishing, fractal:radio.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Multi day continuity [supported] Budgets arm per run, pauses credit back time and runs chain across restarts. Sources: fractal:durability, fractal:timebudgets.
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
Dependencies [partial] Scripts and steps run by agents install dependencies; fractal documents cache warming for new worktrees. Sources: fractal:worktrees.
Caches [supported] A fork warms git-ignored build state from the user node. Sources: fractal:worktrees.
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.
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.
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.
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.
Shared limits [supported] Run budget is shared across the subtree and descendants cap is enforced from the ancestor. Sources: fractal:budgets, fractal:spawning.
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
Command [unsupported] Agent command prompts are disabled by the seeded configs. Sources: fractal:seedperm, fractal:readme.
Tool [unsupported] Tool prompts are disabled by default. Sources: fractal:seedperm.
Network [unsupported] No network approvals. Sources: fractal:readme.
Secret [unsupported] No secret approvals. Sources: fractal:readme.
Delivery [supported] Steps with requires_approval wait for a parent to run node approve; merge is a separate operator act. Sources: fractal:guideloop, fractal:finishing.
Approver identity [partial] The user node or parent node approves; no human identity. Sources: fractal:operating.
Lifetime [partial] An approval releases one step. Sources: fractal:guideloop.
Allow [supported] node approve releases the gate. Sources: fractal:operating.
Deny [partial] The parent can stop or kill; no explicit deny verb. Sources: fractal:operating.
Revoke [partial] Stop and kill end a gated or running node. Sources: fractal:operating.
Tunnels [not-applicable] No tunnels. Sources: fractal:readme.
Defaults [supported] README warns that nodes run without permission prompts by default. Sources: fractal:readme, fractal:seedperm.
Safer modes [partial] Seed configs can be edited; agent-level modes are user configured. Sources: fractal:seedperm.
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.
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
Keyboard [partial] The TUI has a focus ring and key actions. Sources: fractal:tui.
Narrow screen [partial] The cockpit re-clamps pane geometry on terminal resize and panes are drag-resizable, but no narrow-terminal layout is documented. Sources: fractal:tuiwidgets, fractal:tui.
Context switching [partial] Short names resolve nodes quickly. Sources: fractal:cliNode.
Roles [partial] Node roles in the tree are visible. Sources: fractal:tui.
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.
Attribution [unsupported] No human attribution. Sources: fractal:srch-team.
Context loss [partial] Sessions without recorded ids lose context. Sources: fractal:transcripts.
Harness transfer [partial] Node agent can be changed with node update and relaunch; sessions are per agent. Sources: fractal:operating, fractal:transcripts.
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
Tests [partial] Agents run tests as part of steps; no product-enforced test gate. Sources: fractal:seedsteps.
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.
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.
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
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
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.
Subprocessors [partial] Only the user-chosen model providers and GitHub for the price table. Sources: fractal:pricingsrc.
Telemetry disclosure [partial] extending.md states the package ships no telemetry hooks beyond an extension point; the README does not discuss telemetry. Sources: fractal:extending, fractal:srch-telemetry.
Telemetry defaults [supported] No default collection found. Sources: fractal:srch-telemetry.
Telemetry controls [not-applicable] No telemetry to control. Sources: fractal:srch-telemetry.
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
Release stage [supported] Version 1.4.0 on PyPI; changelog says the project is young and minors may break. Sources: fractal:changelog, fractal:pyproject.
Release activity [supported] Dated changelog entries up to 2026-10-25 and repository pushes through 2026-11-05. Sources: fractal:changelog, fractal:repoapi.
Status history [unsupported] No status page. Sources: fractal:readme.
Deprecation [partial] Breaking changes are listed per release. Sources: fractal:changelog.
Export options [supported] Git and SQLite. Sources: fractal:schema.
node list/status/activity/cost, TUI cockpit, tmux attach, radio feed; steering through radio directives, NODE.md edits, chat, retunes, approvals and lifecycle verbs.
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.
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
Embedding applications register or override agent backends in process or through a per-tree deployment hook file; the package itself ships no telemetry.
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
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.
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).
Inter-node messaging in fractal/core/radio.py: channels, send/post/reply, subscriptions, read receipts, reactions, saved messages, all in the central database.
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.
One status vocabulary across node status file and database rows (idle, active, paused, completed, exited, failed, retired); a healer reconciles crashed loops.
No image or attachment input path exists in fractal; prompts are text, and the few hits are unrelated (provisional_errors, worktree and template wording).
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.
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