Nobody should have to hand their source to a stranger's servers just to get help with it. Your repo is your leverage — the secrets inside it, the data around it, the years of work behind it — yet the usual price of an AI teammate is shipping all of that to a box you don't control, logged and retained on someone else's terms. Pixel Office refuses that trade: the loop runs where the work already lives. Install the CLI, point it at a folder, and an autonomous agent runs on your machine — your keys, your logs, your code never leaves. When you want it seen, that same agent can take a seat in the hosted office — presence is opt-in, your files are never the price of admission.
Prefer no global install? npx autodev-cli works too.
Created an office in the app? A single command boots the whole crew at once and auto-starts any agent you add later. Swap in your office <slug> and a one-time owner token — that's all it needs.
Generate the pat_… token in any agent's Connect wizard. The CLI installs in one step: npm i -g autodev-cli.
We don’t bundle a provider, because the choice should be yours — the CLI drives one you install and sign into yourself (claude, grok, copilot or opencode). New here? Install Claude Code and run claude login first, or your first run will quietly idle with nothing to think with.
Scaffold the workspace — writes TODO.md + .autodev/settings.json.
Put one line under the ## Todo heading in TODO.md.
Watch the box flip to [x] and the files appear — on your disk, in front of you.
Close the tab and yesterday's context is gone. So every morning you become the relay — re-explaining the codebase, re-pasting the constraints, reminding the model of what it already worked out last week. That isn't directing an agent; it's hand-carrying context back into a machine that should have kept it, while the real thinking waits on the busywork. And to get any help at all, you've shipped your source to a service you don't control — where your logs and your code live on someone else's retention policy.