Docs.
Install, connect what you already pay for, and read leftover. Short on purpose. The repo holds the rest.
- 01Getting startedInstall the desk, make a project, start a chat. Ten minutes, no account.
- 02Connect the vendors you pay forEach vendor runs through its own CLI, under the login you already hold. Nothing pools.
- 03Projects and chatsA project is a name. A chat carries its own vendor, model and effort.
- 04Permissions and sandboxTwo separate controls, both on the chat. Agents can ask to raise them. They never lower them.
- 05Meters, budgets and paceSpend is leftover, read from each vendor's own meter. A missing meter stays unknown.
- 06Work that outlives a turnSchedules, goals, plans, workers and routing. All journalled, all back after a restart.
- 07LearningA private store on your own disk. Off until you turn it on. Export it or wipe it any time.
- 08Skills, MCP and custom botsExtend the desk with the vendors' own skills, MCP servers, and bots you add.
- 09Command referenceType / in any chat. These are the desk's own commands; each vendor adds its own on top.
- 10Data and privacyWhere things live, what it talks to, and what never leaves the machine.
- 11Updates and releasesThe desk checks GitHub. Installers and notes for every version live there.
- 12TroubleshootingThe short list. If it is not here, the public repo's issues are the place.
- 13How it fits togetherA window, a main process, and one adapter per vendor. The window never touches a vendor CLI.
- 14FAQShort answers to the questions that come up first.
Something missing? The public repo has the README, every release, and an issue tracker.
Get the desk.
Windows and macOS. Open source under MIT.