Your computer, in the workbench.
The local host is one program per computer. It serves the workbench at localhost, opens this computer's folders as a drive, drives the machines plugged into it, and gives your agents an MCP server of their own.
One host per computer
The host owns this computer's boundaries.
The workbench page never opens a serial port or a file by itself on this computer. It asks the host, and the host checks the caller's grant, records the act, then does it.
Started for this page
A host in a scratch home, 158 tools.
The study started the host on this computer in an empty home, with no account, read /host.json and listed the tools of its MCP server, then stopped it.
The host's tools act on this computer: its folders, its devices' channels, a 3D kernel, the operations of the editors. The hosted MCP has its own, larger list (Hosted MCP).
- tools in this host's MCP server, 237,389 bytes listed
- 158
@commandagi/host, the latest of 12 versions on npm, published 2026-10-23- 0.6.8
- program per computer: a second start takes over from the first or refuses
- 1
deployments/clients/host/package.jsonOutput case-studies/this-computer/stats.jsonTool scripts/sites/case-studies.mjs this-computerRan on This computer (dell-gb10-1): Linux, arm64, Node 24, in a scratch home with no platform linkWhen The drivers it runs
41 drivers run in the host.
Each driver is one row of the catalog and says what it is verified to. 35 are built and verified on loopback; 6 are planned. None is yet verified on a bench or on hardware.
- drivers built, each verified on loopback
- 35
- planned
- 6
- verified on a bench or on hardware
- 0
packages/domain/world/drivers.jsOutput case-studies/this-computer/stats.jsonTool scripts/sites/case-studies.mjs this-computerRan on This computer (dell-gb10-1), reading the checkoutWhen Run the host on your computer.
Install the desktop app, or the host alone: npm install -g @commandagi/host, then commandagi daemon.