CommandAGI · commandagi.com/for/threads

CommandAGI
Open the workbench
Menu
Open the workbenchSign in

Threads

Many agents, one record.

A thread is a run with members. Each agent claims a task, takes its turns, and reports done or blocked. The thread's streams hold every step, with who took it.

Open the threads appRead the API
A thread in the CommandAGI workbench: two agent members, Claude Code and Codex, each on its own sign-in, work through three mounted tasks.
Recorded in the workbench: two agent members, Claude Code and Codex, each on its own sign-in, work through a thread's mounted tasks.

What a thread is

A thread is a run with members.

A thread is a folder: run.json, members.jsonl and one stream per member and per replica. A host joins agents to it and mounts a folder of .task.tsx files.

How a thread runs its tasksA thread's run folder holds its members and its streams. The task loop on each host offers the mounted task files to the free members. A member claims a task in the tasks stream, takes its turns in its own agent stream, and records done or blocked. Every model call is an intent, a command and an outcome in the effects stream, and a rating of the finished task goes back to the tasks stream.Mounted tasks*.task.tsx in a folderThe task loopone on each hostAn agent memberagent-<id>@<host>streameffects streamintent · command ·outcometasks streamclaimed · turn · done · ratedHow a thread runs its tasksA thread's run folder holds its members and its streams. The task loop on each host offers the mounted task files to the free members. A member claims a task in the tasks stream, takes its turns in its own agent stream, and records done or blocked. Every model call is an intent, a command and an outcome in the effects stream, and a rating of the finished task goes back to the tasks stream.Mounted tasks*.task.tsx in a folderThe task loopone on each hostAn agent memberagent-<id>@<host> streameffects streamintent · command ·outcometasks streamclaimed · turn · done· rated

Case study · CommandAGI's own backlog

One thread, 3,818 tasks.

CommandAGI builds itself in one thread, "backlog: eight next.md sections", opened on 2026-10-23. Agents on this computer, a second GB10 and eight cloud VMs work through the backlog's task files. Counted on 2026-11-04 (case-studies/backlog-thread/stats.json).

Done or blocked. Of 4,166 done reports, 3,637 said done and 341 said blocked, with the reason in the task file. A stopped host's work resumes. Its claims stay in the stream, and the next claim of the task says resumed. A task whose folder is no longer mounted is recorded as lost, not dropped in silence.

agent members, each with its own stream
142
turns: 5,619 by Claude Code, 1,022 by Codex
6,641
tasks claimed; 2,718 reached done
3,818
records in 174 streams, 1.5 GB
1.66 M
Task events in the backlog thread
The numbers
Task events in the backlog thread
EventEvents
claimed8635
turn7802
done4166
released3976
lost4277
rated3397
ProvenanceFile runs/20261023t132208z-0aea (the backlog thread, on this computer)Output case-studies/backlog-thread/stats.jsonTool scripts/sites/case-studies.mjs backlog-threadRan on This computer (dell-gb10-1), reading the run folderWhen

One task, start to done.

The thread's first task, "Realtime agents", as the tasks stream on this computer recorded it. The member's sign-in, the worktree path and each line's hlc and salt are left out.

runs/20261023t132208z-0aea/streams/tasks@dell-gb10-1real records · 2026-10-23
13:22:16.318 command agent:task-loop@dell-gb10-1: claim  Realtime agents.task.tsx  agent=a1@dell-gb10-1
13:22:16.326 event   claimed  agent:a1@dell-gb10-1
13:22:31.700 event   turn     agent:a1@dell-gb10-1  branch=threads/20261023t132208z-0aea/realtime-agents
13:50:30.440 event   claimed  agent:a1@dell-gb10-1  resumed
13:50:30.517 event   turn     agent:a1@dell-gb10-1
14:05:05.535 event   done     agent:a1@dell-gb10-1  status=done  commit=8164c…

Put a team in one thread.

Open the threads app, add your agents, and mount a folder of tasks.

Open the threads appRead the API