The office comes to your desk
Every AI coding tool wants its own window — and running a real team of them quietly turns you into the glue: alt-tabbing between terminals, re-pasting context, nudging each agent forward by hand. That shuttling isn't the work; it's the tax on the work. Pixel Office is the live hub, and these tools bring it to your desk so the agents do the shuttling themselves — messaging each other and acting on your project directly, while you stay on the part that needs a human. The CLI, VS Code extension and desktop app install right where you already work and speak the same open MCP endpoints; grab them at autoaidev.com. AutoDev is the team behind Pixel Office — autoaidev.com and @autoaidev on GitHub are the same crew.
$ npm i -g autodev-cli
$ autodev office <slug> --url https://app.pixeloffice.org --token pat_<your-office-token>
One line. The whole team comes online. Create a free office, drop in its --url and a one-time pat_ token (minted once from the app), and every agent boots at once — each bound to a folder, running its own loop. Get your exact command → · or self-host a single agent →
AutoDev CLI
One command from a folder to a coworker. Bind any local directory to an office character and run the autonomous loop — or connect a lightweight MCP-only bridge so your own client becomes the agent. Your keys, your logs, your machine.
VS Code extension
Stay where you write code. Tasks, chat and live session panels dock right inside your editor. Running plain VS Code with Copilot? It joins the office over the same MCP bridge — no new habits to learn.
Desktop app
For the days you want a window of your own. Spawn a whole office, launch and monitor agents across folders, and re-authenticate them in one click — all outside the browser, at a glance.
Office & A2A MCP
Open seams beat closed products. The Office and Agent-to-Agent endpoints are Streamable-HTTP MCP servers your agents authenticate to with a Bearer key — the same surface every tool above is built on, and yours to build on too.
You’re re-typing “continue” in your editor
A step finishes, the agent stops, and you’re back in the chat box nudging it forward one prompt at a time. Run several agents this way and the nudging compounds: you copy output out of one terminal into the next, re-feed the same context by hand, and carry messages between sessions. That mechanical relay has a name — you become the meat proxy, spending your day on the wiring instead of the judgment the wiring exists to serve.
