Operational truth
See what is resident, executing, waiting, draining, blocked, or actually complete—without inferring state from a terminal tab.
SELF-HOSTED CODING-AGENT OPERATIONS
Work with AI agents as a system.
ThreadCells coordinates native CLI agents, keeps open workflows moving across model turns, and maintains the orchestration environment underneath them—on your own Linux host.
OWNERREADY
SUPERVISORRUNNING
WORKER 03RUNNING
WORKER 02COMPLETE
REVIEWERREADY
DURABLE RESULTPERSISTED
WORKFLOW SEQUENCEDSUPERVISORintent → workers → reviewer → durable result
RESIDENT 2 / 5PROVIDER 2 / 3WORK 2 / 2HEAVY 0 / 1
THE HARD PART / 02
Starting more agents is easy.
Knowing what is true is not.
Which process owns the worktree? Which session is only idle—and which one is finished? Is the machine out of provider capacity, work contexts, or heavy execution? Did the reviewer return a result, or just stop printing?
tm-83A1SUPERVISORRUNNINGprovider 01 / 03
tm-94C2WORKERCOMPLETEresult persisted
tm-07F4REVIEWERREADYcontext 02 / 02
OWNER GATEAUTHORITYGATEDdecision required
THE CONTROL PLANE / 03
One place to see the work,
the host, and the handoff.
ThreadCells wraps native agent execution in an operational surface: sessions, projects, terminals, profiles, capacity, workflows, documentation, optional global Telegram lifecycle alerts, and current build identity.
01
Session truthProvider, profile, lifecycle, project, and active work remain visible.
02
Operational scaleFirst, Last, and Total summaries keep large durable histories readable.
CORE IDEAS / 04
A control room built around
the failure modes that matter.
Worktree authority
Anchor work to trusted projects and managed Git worktrees. Writer leases keep concurrent mutation explicit.
Durable results
Delegated work returns a persisted result that can be delivered, acknowledged, accepted, and retired without losing history.
A healthy agent environment
ThreadCells watches host pressure and safely cleans eligible runtime, log, cache, build, and release debris while protecting active work and durable history.
WORKFLOW / 05
Intent goes out.
Evidence comes back.
The coding agent stays native. ThreadCells makes the surrounding lifecycle explicit.
- 01
Create a session
Choose a trusted local project and an agent or supervisor profile.
- 02
Give it the job
A supervisor can delegate coherent work to native CLI workers and reviewers.
- 03
Watch the system
ThreadCells keeps the workflow moving across model turns while sessions, worktrees, capacity, and host pressure stay visible.
- 04
Step in when asked
Results return durably. Owner gates pause only for decisions that genuinely need you.
LIVE RELEASE TOUR
See the control plane in motion.
A tour of the real release system: Home, multi-agent work, Agents, provider-reported Statistics, Housekeeping, capacity, and redacted notification settings. Operational values and lifecycle states are real; Session and Project labels are anonymized.
PRODUCT EXPERIENCE / 06
The workflow and the host,
in one operating view.
Open the real session behind the summary, keep the runtime healthy, and route high-signal owner attention without losing durable context.
NATIVE BY DESIGN / 07
Keep the coding agent.
Add the operating system around it.
ThreadCells drives native provider CLIs in real tmux terminals. Provider adapters report what the installed host genuinely supports; unsupported capabilities stay visible instead of being simulated.
- Codex reference adapter and first-class Claude Code adapter
- Provider-native authentication remains with the operator
- Profiles and provider configuration are versioned control-plane artifacts
TECHNICAL PREVIEW / 08
A practical first run.
Honest alpha boundaries.
ThreadCells is for individual developers and trusted small teams that operate several coding agents on one Linux host and want durable workflow state instead of a pile of terminal tabs.
Start on a trusted Linux host
The supported baseline is Ubuntu or Debian with Python 3, Git, tmux, Node.js/npm for the Web build, and at least one provider CLI you have authenticated.
Open the installation guideProvider support stays explicit
Eight built-in adapters normalize launch and lifecycle. Codex is the release-acceptance reference; readiness, resume, usage, and model controls still depend on the installed provider CLI.
Check provider compatibilityKnow where trust stops
This alpha targets one trusted operator and one host. It is loopback-first, supports remote use through an SSH tunnel, and does not treat worktrees as security sandboxes or isolate hostile tenants.
Read the alpha limitationsMACHINE OWNERSHIP / 09
Your host.
Your terminals.
Your control.
ThreadCells is self-hosted and loopback-first. It coordinates powerful local tools; it does not pretend a worktree is a security sandbox or promise hostile multi-tenancy.
Loopback firstSSH-tunnel access is the supported preview boundary.Real terminalsInspectable tmux sessions, not hidden disposable jobs.
APACHE
2.0
2.0
OPEN SOURCE
Inspect the control plane you trust with the machine.
ThreadCells is available under Apache License 2.0, with upstream attribution preserved in the appropriate legal and provenance materials.
READY / 10
Stop guessing what the agents are doing.
Run the work. See the machine. Keep the result.