Docs14 of 14
FAQ
Short answers to the questions that come up first.
Do I need an account?
No. There is no account with us and no server of ours. You sign in to each vendor through its own CLI or API, with the login you already hold.
Does it pool my subscriptions?
No. Each vendor runs under its own login. Subscriptions, context, tools and sandboxes are never pooled, proxied or shared.
Which vendors does it run?
Grok, Claude, Codex and Cursor over ACP, each through its own local CLI. Custom bots over HTTP: any Anthropic Messages or OpenAI Chat Completions endpoint, hosted or on your own machine.
Do I have to install the vendor CLIs?
Yes. They are not bundled. Install the ones you use and sign in as you normally do; the desk runs them under that login.
What does it cost?
The desk is open source under MIT, and the installers are on GitHub. Your subscriptions stay yours; the desk spends leftover you already bought.
What does it send, and where?
It talks to the vendors you connect, including their usage endpoints for the meters, and to GitHub to check for a newer release. It sends no analytics.
Where are my API keys kept?
In the OS credential store — Keychain on macOS, DPAPI on Windows — never in plain text. If that store is unavailable the desk refuses to save the key.
How do meters work when a vendor has none?
The ring stays unknown. The desk reads official meters only; a missing one is not shown as empty or full.
Is there a Linux build?
Not yet. Linux builds and tests in CI, but installers ship for Windows and macOS.
How do updates arrive?
Settings → Profile checks GitHub for a newer desk. On a Mac the installer downloads that release's disk image and replaces the app. Windows keeps the same app identity and encrypted vault across updates.