Operate ThreadCells
without repository archaeology.

ThreadCells is a self-hosted system for running several coding agents as one coordinated workflow on a Linux machine. It gives agents real terminals and Git worktrees, keeps ope…

This is the fastest supported path from a source checkout to a local ThreadCells server. It builds an immutable local candidate, verifies its contents, installs it under the cur…

This guide explains the supported local installation path and the reason ThreadCells installs from a verified candidate. If you want only the commands, use Quick setup.

This tutorial starts one deliberately small agent and shows where to find its terminal and result. Complete Quick setup first and leave the ThreadCells server running.

ThreadCells adds structure around native coding-agent terminals. This page introduces one idea at a time and then shows how the pieces fit together.

ThreadCells is loopback-first: the server should listen on 127.0.0.1, not on a public interface. The ordinary Web UI is an operator console and does not provide a general login…

The Web UI is the operator's live view of ThreadCells. It is designed for a loopback listener and works normally in a browser or as an installed basic PWA. Installing it does no…

A ThreadCells project is a registered Git repository. It gives sessions, profiles, statistics, and workflows a stable place to belong. ThreadCells never makes a repository safe…

A provider is the native coding-agent CLI that actually runs the model turn. ThreadCells supplies an adapter around that CLI so launches, terminal status, cancellation, capabili…

A profile is a reusable launch policy for an agent. It answers: which provider and model should run, how much reasoning should it use, what role and instructions should it recei…

A workflow represents work that must remain coherent across several model turns, terminals, or delegated agents. It prevents a provider's final message from being mistaken for c…

Statistics summarizes usage that supported provider CLIs actually emit. It helps answer which sessions, profiles, projects, and providers consumed model tokens; it is not a bill…

Operator authorization protects sensitive control-plane changes in Settings. It is separate from access to the ordinary Web UI: browsing agents, terminals, docs, and statistics…

ThreadCells can send low-noise lifecycle notifications to one Telegram destination. This is an installation-global ThreadCells capability: it does not belong to, read configurat…

ThreadCells separates capacity because coding-agent work can pressure different parts of a host at different times. A model turn consumes provider capacity; an assigned coding c…

This is an advanced guide for maintainers adding a trusted provider integration. Operators choosing among built-in providers should start with Providers.

ThreadCells publishes JSON Schema Draft 2020-12 documents for ProfileDefinition V1, ProviderConfiguration V1, AdapterManifest V1, and AdapterCapabilities V1 under schemas/v1 in…

ThreadCells is a local control plane around native coding-agent processes. It deliberately keeps the provider terminal, Git repository, durable coordination state, and browser U…

Routine ThreadCells operation is mostly about preserving four kinds of truth: the running build identity, workflow ownership, available capacity, and recoverable state.

Housekeeping reclaims runtime artifacts only when ThreadCells can prove they are eligible. It is intentionally conservative: an unknown, unreadable, active, referenced, or chang…

A useful ThreadCells backup preserves the durable coordination state and the configuration needed to interpret it. Installed code and build caches are usually rebuildable; the d…

ThreadCells deployment promotes a verified immutable candidate into the local runtime. It does not imply publication, a Git push/tag, package release, or public network exposure.

An upgrade is a controlled candidate promotion with a verified rollback, not an in-place overwrite of whatever files happen to be running.

Start by preserving evidence: current build identity, safe error text, affected session/workflow, capacity status, recent logs, and Git status. Avoid cleanup, deletion, or blind…

Build an isolated local candidate from a clean committed tree with scripts/buildlocalcandidate.py --output <new-directory. It packages the generated Docs/UI and a local wheel. V…

ThreadCells is intended for one trusted Linux host operated by one person or a small trusted team. It coordinates powerful native coding agents; it is not a sandbox for hostile…

ThreadCells is a technical preview focused on trustworthy local operations for coding agents on one Linux host. These boundaries are intentional product facts, not promises abou…

ThreadCells is for developers who already value native coding-agent CLIs but need a clearer way to operate several of them on one machine.

ThreadCells is an independent downstream derived from AWS Labs CLI Agent Orchestrator. The retained upstream license and attribution are in the source candidate's LICENSE and NO…

Thanks for helping improve ThreadCells. Reports and pull requests are welcome when they are focused, actionable, and safe to discuss publicly.

GitHub Issues are ThreadCells' curated public backlog, not a transcript of warnings, audits, or release debugging.