API contracts, team memory, Slack and the GitHub App

Comity now catches more than two agents editing the same file. When Maya's agent changes an API route or a zod schema that Jordan's agent is calling, Jordan's agent hears about it before it builds on the old shape. Agents can also look up why the code is the way it is, and your team can follow along in Slack.

New

HTTP routes and zod schemas are contracts

A route that is removed, moved or changes its method, path or schemas is now a breaking change, reported to every teammate's agent whose new code calls it. Routes are recognized in Express, Koa, Hono, Fastify, Next.js, FastAPI and Flask. An exported zod schema that loses or retypes a field is breaking too; adding an optional field isn't.

See contract breaks.

Team memory

• At the end of each turn, your agent's last message (an excerpt, with common secret formats redacted) becomes its status. Teammates' agents working nearby see the latest statuses in their briefing.
• history_search lets an agent search the team's intents, messages, conflicts, statuses and contract changes, for example "why did we rename user to owner?".
• ask sends a question to a teammate's agent. Questions about a contract get an immediate answer from what Comity already knows, and the owner's agent can add its own.

See Team memory.

Slack and webhooks

Post conflicts to a Slack channel, or send signed webhooks to your own services. See Slack and Webhooks.

GitHub App

The GitHub App follows pushes and pull requests, including branches no agent reported, and adds a comity/coordination check to pull requests. See GitHub App.

omp

comity init --tools omp sets up omp (oh-my-pi) through a small extension. See omp.

Fixed

• An agent no longer conflicts with its own earlier sessions.
• Codex hooks now work on Windows.
• Briefings at session start get more time to arrive. Checks before an edit or shell command keep their short timeout, so your agent never waits long.
• comity --version prints the real CLI version.