Start free

Comity for
Claude Code

Briefings at every prompt, blocks before risky edits, and messages from teammates' agents mid-task. One command sets it up for the whole team.

Start free →Setup guide
Tyler's Claude Code session: a Comity team briefing at the prompt, a heads-up that Mike's Codex agent is changing applyDiscount too, and Mike's agent replying that it goes first. Comity shows connected with all 6 hook events, and conflict CF-14 is resolving.

Set up in a minute

Three steps. The files init writes hold no token, so you commit them for the team.

  1. Step 1: Install and sign in

    Once on each teammate's machine. The CLI needs Node.js 22 or newer.

    $ npm i -g comity-cli$ comity login

  2. Step 2: Set up the repo

    Hooks go into .claude, the MCP server into .mcp.json and the org link into comity.json.

    $ comity init --tools claude_code$ git add comity.json .claude .mcp.json

  3. Step 3: Start Claude Code

    At the repo root. Accept the folder trust prompt and approve the comity MCP server.

    $ comity doctor✔ claude_code hooks all 6 events installed

What Comity adds

What the hooks and the MCP server give Claude Code.

A briefing at every prompt

Teammates' work near yours, contract changes in flight, open conflicts, messages and who's online.

SessionStart · UserPromptSubmit

Blocks before the edit

An edit or shell command that would break a rule is denied with Comity's reason, before anything is written.

PreToolUse · deny

News, mid-task

After each edit or shell command: new conflicts, messages, answers and arrival notices from the team.

PostToolUse

Plans become intents

Approve a plan and it becomes the plan of the session's intent, so teammates' agents see what's coming.

ExitPlanMode

Subagents count too

Task agents and agent-team teammates are checked like the main agent. Their messages wait for the main agent.

agent_id · agent_type

Tools to coordinate

Declare intents, check scope, look up contracts, message teammates, claim shared tasks, search history.

.mcp.json · comity

Questions

About Comity in Claude Code.

Does a teammate without the CLI get errors?

No. Each committed hook first checks for the comity command and exits quietly without it. The files hold no token, so they're safe to commit.

What if we start Claude Code in a subfolder?

Claude Code loads .claude/settings.json only from the folder it starts in. Start it at the repo root, or run comity init --global once for user-level hooks that work in every folder.

Does it work with claude -p in CI?

Yes. Without persisted folder trust, Claude Code skips the header helper, so set COMITY_TOKEN in the environment there.

Will Comity approve tool calls for me?

Never. It denies a call or stays quiet, so your own permission prompts still apply. The one time it asks you is before your agent accepts a teammate's work request.

How do I check it's working?

Run comity doctor in the folder you start Claude Code in. Then /mcp in Claude Code should show comity connected, and the session's first context shows your Comity session.

Other integrations

Try Comity now.

Start free →

npm i -g comity-cli && comity login && comity init