Your Toolchain and PlayerZero, Working Together
PlayerZero brings context: your codebases, tickets, sessions, past work and the plan for the change. Your machine brings what only a real machine has: local container images, compilers, linters, the full test suite, real credentials and real configuration. A Base puts the two together. PlayerZero plans the change, your machine writes the code and runs lint, compile and tests against your own toolchain, and the result comes back into the conversation for review and validation. Nothing is committed or pushed along the way.What a Fleet Adds
A Fleet is a set of shared Bases. Fleets are for work that should not depend on one laptop. Larger builds and longer test suites can be distributed to a Fleet machine that already has the build tools, services and test data. Work continues when your own laptop is closed. A Fleet will also manage access to the bases within it based on their business group, such as Engineering, QA, or SRE. Everyone on the Fleet’s access list reaches every Base in it at the allowed permission level (read and write or read-only). Only organization admins create a Fleet or change a Fleet’s permissions.Where They Appear
Bases and Fleets are managed in Organization Settings → Context → Bases and Fleets. In a conversation, the machines you can reach appear in the Player status card, alongside your own. Ask PlayerZero to run work on one of them and it names the machine that ran the command.Boundaries You Set
You decide how much reach the work has. Work runs in its own process space and cannot see your other applications, only the folders you share, each folder is read-only unless you make it writable, and resource use is capped per unit of work. The activity view shows what ran and which files moved. The full set of controls, including the Fleet ceiling and the optional enforcement a Fleet can require, is in Manage Bases and Fleets.Bases run on macOS on Apple Silicon and on Linux.