Install & connect
Install, then connect by allowing it in your browser. Also covers remote machines and CI.
Install
Node.js 18 or later is required.
npm i -g comitia
Once it's installed, run comitia --version to confirm.
Connect — allow it in your browser
comitia login
- Your browser opens to Comitia's "Connection request" screen
- Pick a workspace and permission level, then click "Allow"
- Back in the terminal, you'll see "Connected"
You'll never see a raw token string. The connection uses a secret the CLI generates plus a 5-minute, single-use code (PKCE), so even if the code ends up in your address bar, it's useless anywhere else.
⚠️ Only click "Allow" on a connection request screen if you just ran
comitia loginin your own terminal. If someone sent you the link, close it.
init — connect + tell your AI about it
comitia init -g
In addition to login, this writes usage notes into your AI rules files (like ~/.claude/CLAUDE.md) and installs the Claude Code skills. Without this, your AI won't know comitia exists — you'd have to explain it every time. Drop -g to apply it to just the current folder.
Permissions and workspaces
| Read only | Look up and read docs and sources. Can't add or edit |
| Sources & organize | Can add sources and organize the wiki |
| Single workspace | The CLI won't ask which workspace to use. If the connection leaks, it's limited to that one workspace |
| All | Every workspace you can see. Use comitia use to set a default |
🔑 In most cases, stick with read only + single workspace.
From a remote machine or over SSH
If your browser is on a different device, the connection can't come back to your terminal. Use the paste-a-code flow instead.
comitia login --paste
Open the address in your own browser and click "Allow" — you'll get a connection code. Paste that into the terminal. The code only works for 5 minutes, and you shouldn't share it with anyone.
From CI or scripts
Where nobody can click through a browser, use a token directly. In Comitia, go to your profile (top right) → "Connection tokens" and issue one.
export COMITIA_TOKEN=z2o_live_...
export COMITIA_COMPANY=<workspace id>
comitia recent
Or save it once:
comitia login z2o_live_...
Environment variables take priority over the config file — COMITIA_API · COMITIA_TOKEN · COMITIA_COMPANY. (The old names Z2O_* are also read.)
Where it's stored, and disconnecting
- Connection info is stored at
~/.comitia/config.json, locked down so only your account on this machine can read it comitia logout— remove it from this machine- Disconnect from the server — Comitia → profile → "Connection tokens" → trash icon. Do this if you lose a laptop
comitia whoami— see how you're currently connected