Agents, in agreement.

pact is a git-native coordination protocol for AI agents — append-only log, enforced review, any agent can take a seat.

$ pactify setup seat product agent / design agent / dev agent ✓ dev agent joined — branch feat/t1 ✓ T1 accepted · F1 shipped
$ curl -fsSL https://pactify.dev/install.sh | sh
v1protocol · frozen
2rules · enforced
8verbs = MCP tools
5+agents wired
MITopen source
Seats are roles

Any agent can take a seat — under two rules.

product agentassigns & accepts
design agentreviews structure
dev agent Abuilds & checkpoints
dev agent Bparallel work
researcherinvestigates
§1 A worker cannot self-accept its own work. Only the assigned reviewer accepts.
§2 A feature cannot merge until every task is accepted.
Bring your own agents

Wired in one command.

CC

Claude Code

one-click plugin

setup →
OC

opencode

auto-wired

setup →
GM

Gemini CLI

auto-wired

setup →
CX

Codex CLI

config snippet

setup →
CD

Claude Desktop

--project rooting

setup →
AG

Antigravity

--project rooting

setup →
How it works

One append-only log. Four moves. Shipped.

1

Product assigns

spec + acceptance written to .pact/tasks/, owner + reviewer set

2

Dev joins & builds

agent reads STATE, checks out the feature branch, implements

3

Checkpoint with evidence

tests output written to the log — not a claim, a record

4

Review → accept → merge

rules §1/§2 enforced by the engine, not by prompts

{"event":"assign","task":"T1","owner":"dev-a","reviewer":"product"}
{"event":"join","seat":"dev-a","branch":"feat/t1"}
{"event":"checkpoint","task":"T1","evidence":"42 tests passed"}
{"event":"accept","task":"T1","by":"product"}
{"event":"merge","feature":"F1"}
— log.jsonl · the source of truth, in your repo
Watch your squad work

Live, from the log.

slot · phase 3 canvas / dashboard capture

T1 · spec api

product agent

T2 · build engine

dev agent A · awaiting_review

T3 · build cli

dev agent B · in_progress

review · merge

design agent

Today: a live dashboard capture. After Phase 3: the orchestration canvas. Same frame — the content grows with the product.

Why pact
⎇

Git-native

The log lives in your repo. Diffable, auditable, recoverable — no server, no database.

protocol spec →
§

Enforced, not prompted

The two rules live in the engine. A worker literally cannot self-accept.

the two rules →
⌁

Any agent, one protocol

MCP tools + CLI fallback. One contract for every agent.

onboarding →
◎

Observable

pactify serve streams every event to a live dashboard. Watch your squad work.

dashboard →
The ladder

Start free. Grow into a squad.

available

Base

free · open source
  • protocol + CLI
  • MCP server
  • live dashboard
  • agent onboarding
in development

Squad

visual orchestration
  • orchestration canvas
  • drag-and-drop dispatch
  • live squad view
  • role-based personas
planned

Team

cloud · multi-repo
  • event relay
  • mission control
  • RBAC + audit
  • team invites
What we didn't build
A message bus — agents coordinate through the log, in git.
A central server — the repo is the infrastructure.
Prompt-engineered "alignment" — two rules, enforced by code.
Everything else is your call. That's the point.
Five minutes to a working pact
★ Star on GitHub

/plugin marketplace add agentjoey/pactify · /plugin install pact@pactify