Exact checks, no guessing
Rules are plain path, package and command checks. What Comity can't see, it doesn't claim to check.
Team decisions
Settle it once.
Every agent follows.
Record what your team settled, like Postgres, not Mongo, and why. Every agent hears it, and gets a heads-up or a block when it goes against it.
How it works
Agents propose. People confirm. Comity checks.
Agents propose, people confirm. Tell your agent what was settled and it records a proposal. An owner or admin confirms it in the dashboard, in Slack, or right in Claude Code.
Recording a decision →
Every agent hears it. Each session starts with the decisions in force for its repo, most relevant first. New and changed ones arrive at its next prompt.
What agents are told →
Go against one, and the agent hears why. Comity checks edits, package installs and shell commands against each decision's rules. Warn gives a heads-up. Block stops it until someone approves an override.
Warn and block →
The details
What Comity checks, and what it leaves to people.
Package managers covered
npm, pnpm, yarn, pip, uv, cargo, go get, gem, composer and more. Versions are stripped, so mongodb@6 is still mongodb.
Forbidden commands
Block patterns like git push --force anywhere in a command line, even after && or a pipe.
Every version kept
Each proposal, change and retirement is a numbered version: who proposed it, who confirmed it, and their notes.
How well it's followed
The Decisions tab counts how often each decision warned or blocked an agent in the last 30 days.
From a handoff to a rule
A decision in a handoff's context pack becomes a team proposal with one click: Make team decision.