Docs
Setup, every agent, policies, the dashboard, the CLI and the API, in one place.
Read the docs →Help and support
Fix it fast,
or just ask us.
Most problems are a login, a trust prompt or a hook that didn't load, and comity doctor names the fix. For anything else, email hello@comity.so.
Ways to get help
Start with what's fastest. If you're still stuck, write to us.
Troubleshooting guide
Every comity doctor check, hooks that don't run, MCP errors, plan limits and fail-closed repos.
Troubleshooting →comity doctor
Run it in the repo where your agent works. Every warning comes with a › hint that names the fix.
CLI reference →comity status
What this machine sees: your login, checks skipped in the last day with their timings, and who isn't coordinated.
CLI reference →Your org in the dashboard
Needs you lists what's waiting on you, Activity shows live sessions, and Plan & billing shows who's coordinated.
Dashboard tour →Email us
Write to hello@comity.so. Include comity doctor --json, comity status --json and the last lines of hook.log.
hello@comity.so →Common fixes
The problems we see most, and what to run.
My agent's hooks don't seem to run.
Run comity doctor in the folder where the agent starts. Codex needs the comity hooks approved in /hooks, Claude Code needs the folder trusted, and an agent started in a subfolder skips hooks committed at the repo root.
Claude Code has no Comity tools.
Start claude in the repo once and accept the trust prompt. Its MCP connection gets the token from comity mcp-headers, which Claude Code runs only in trusted folders. Or set COMITY_TOKEN.
"token: rejected by server (401)"
The token was revoked, expired, or belongs to a different server. Run comity login again. If COMITY_TOKEN is set in your shell, it overrides the stored login: update or unset it.
"This repo uses Comity org X"
The repo's comity.json binds it to an org this machine isn't logged in to. Run comity login --org X.
Edits are blocked: "Comity is unreachable"
The repo is fail-closed. Run comity doctor and fix the server check. If Comity itself is down and the work can't wait, comity fail-open --for 1h --reason "…" lets edits through, and owners see each use in the audit log.
Some teammates' agents aren't coordinated.
On the Free plan, the first 5 developers active in a month are coordinated. An owner can upgrade in Plan & billing, and the caps lift immediately.
Hooks don't run on Windows.
Claude Code runs hook commands through Git Bash, so install Git for Windows. If comity update fails with EBUSY or EPERM, close other terminals and agent sessions using comity, then run the printed npm command.
Still stuck? Send us what doctor sees. Run these in the repo where your agent works and paste the output into your email. It's usually all we need to find the fix.
hello@comity.so →