Contracts, not just files
Exported functions and types, HTTP routes and zod schemas in TypeScript, JavaScript, Python and Go. A breaking change warns everyone who calls it.
Conflict detection
Conflicts, caught
before the code.
Comity sees what every agent is editing. When two of them head for the same function, API or table, both hear about it before either writes a line.
How it works
Three steps that run on every edit, in every agent on the team.
Every agent says what it's working on. Its first prompt drafts an intent, and each edit adds the files and symbols it touches. Once declared, every teammate's agent sees it in its next briefing.
Intents and claims →
Overlaps are found before the edit. Before each edit or shell command, Comity checks it against every teammate's live work: the same files, the same function, a contract they call, a protected path or a team decision.
Every conflict kind →
Both sides hear it, and settle it. Each agent gets who, what and a suggestion, and answers with an ack, a proposed order or a rebase. When the overlap goes away, the conflict closes by itself.
Conflict actions and statuses →
The details
What Comity checks, and how it stays out of the way.
Tables and migrations
SQL, Prisma, Knex and Drizzle changes are keyed by table, and two new migrations with the same number overlap even on different tables.
Across repositories
When a route or package export breaks in one repo, the agent using it in a linked repo hears about it too, prefixed Cross-repo.
Warn by default, block by policy
Each kind has a severity in your policy. A block needs strong evidence, and only the side that arrived second is stopped.
Overrides are for people
Agents can only ask. An owner or admin approves with a reason, which is stored encrypted and shown in the audit log.
Quiet when it should be
Info-level overlaps wait for the next prompt instead of interrupting, and an agent's false positive mutes it for its side.