A shared work record.
Submit, claim, checkpoint, and complete tasks across clients and sessions. The ledger holds task records and standing rules, with entries labelled by the client that filed them.
task.submit / task.checkpoint / ledger.readThe runtime
ToolsEnabled Fleet is an MCP server for the Codex and Claude Code CLIs: agent fleet management and mediation, loaded by each official client. It adds coordination inside your sandbox, while each client continues to use its own conversation and sign-in.
Work in progress · BetaSubmit, claim, checkpoint, and complete tasks across clients and sessions. The ledger holds task records and standing rules, with entries labelled by the client that filed them.
task.submit / task.checkpoint / ledger.readKeep shared notes and values between sessions. Index local files and search them lexically, with no model required for search.
memory.set / memory.get / search.queryMediated edits are checked against the bytes an agent observed. Unaffected reads can be rebased after another edit; stale observations cause a refusal. Native file tools can bypass this coordination.
host.read_file / host.patch_fileStart Claude Code and Codex workers, let them delegate, and receive their reports through the tree. Child tool access and provider tiers stay within their ancestors’ runtime allowances.
agent.spawn / agent.resume / agent.set_roleRead OpenShell’s advisor state and observed denials. Get an explanation, then a scoped network-access proposal. You review access changes through OpenShell on the host.
openshell.denials / openshell.proposeInspect the agent tree, work record, asks, and settings without a hosted dashboard. Answer a question from a worker and carry on in your shell.
toolsenabled tree / ledger / settingsAgent trees
The current tree allows up to four direct workers per agent and three levels below you. Reports return to the manager that started the worker.
These are cooperative runtime rules inside one shared sandbox. They are not isolation between workers. For unattended or larger teams, use provider API keys under the applicable provider terms.
Current validation
On beta 3’s exact archive: full Linux installs under three umasks, a two-hour Linux soak with a real beta 2 to beta 3 upgrade in every round, the frozen hand test twice (42 passed, 0 failed each time), a host rehearsal of the two-command install, a two-hour Windows soak through WSL 2 (32 rounds, 0 failures), and an independent security review of the lifecycle changes; see the release notes. Autonomous task performance is not established by these checks.