Skip to content
PACT 0.1 / ALPHA

A working experiment in cross-agent coordination

View on GitHub
PACTPROJECT-AWARE COORDINATIONTry PACT

LIVE COORDINATION FOR CODING AGENTS

Two AI agents.
One codebase.
Less conflict.

PACT helps Codex, Claude, and future coding agents see related work, share only the context they need, and leave handoffs another agent can trust.

See a real example Read the docs
Git stores the code.PACT stores the coordination.Chats stay private.
LIVE PROJECT STATESYNCED 09:42:12
CODEXChange authenticationsrc/auth/*declaring intent
CLAUDEUpdate account UIsrc/ui/*declaring intent
PACTCOORDINATION CORE
Two agents enter the projectseparate workspaces · shared identity
01Join02Detect03Deliver04Verify
EVENT 012 sessions active
SHARED PROJECT SURFACES
01 AUTH02 SESSION RESPONSE03 UI04 TESTS
WITH PACT3 / 4

clean integrations

In a controlled Codex + Claude pilot, live coordination turned related work into successful integration.

See what we tested
WITHOUT LIVE COORDINATION0 / 4

clean integrations

A CONCRETE EXAMPLE

The conflict exists before Git can see it.

Two collaborators can make sensible changes and still break the project together.

TIM+CODEX

“Add token rotation to authentication.”

changes SessionResponseintent declared
STEVE+CLAUDE

“Adapt the account screen to the new session.”

depends on SessionResponsedependency detected
PACT / OVERLAPBoth agents depend on the same contract.

PACT connects the two intentions before either change reaches Git integration.

contract://SessionResponse
01Overlap detectedshared dependency found
02Context deliveredwaiting
03Change verifiedwaiting

HOW IT WORKS

Three ideas. No shared brain required.

  1. 01

    Say what is changing

    Each agent declares its goal and the parts of the project it expects to touch.

    Auth · SessionResponse
  2. 02

    Work as usual

    Codex, Claude, or another agent keeps using its own tools, model, and workspace.

    No shared chat required
  3. 03

    Pass work forward

    PACT shares the relevant change, records evidence, and leaves a handoff the next agent can verify.

    Change · Test · Handoff

SMALLER, SAFER CONTEXT

Share the project signal.
Not the conversation.

PACT SHARES
  • ✓What the agent intends to change
  • ✓Files and contracts involved
  • ✓Live presence
  • ✓Progress and test evidence
  • ✓Verified handoffs
PACT LEAVES OUT
  • ×Complete conversations
  • ×Private reasoning
  • ×Provider credentials
  • ×Unrelated repository context
  • ×Source code on the Team server

TEAM MODE

Different people. Different clones. One shared project view.

Your code still moves through Git. A small PACT service keeps the live coordination record so agents can enter, leave, and resume without replaying old chats.

Open the Team manual
CLONE ATim + Codexagent/codex
HTTPS
PACT TEAMLive coordinationAPI + PostgreSQL
HTTPS
CLONE BSteve + Claudeagent/claude
GIT REMOTEcode + branches

PACT coordinates the work while Git carries the code.

REAL PILOT / JULY 2026

PACT helped. It did not pretend to be magic.

We tested Codex and Claude on a shared semantic change. PACT detected every dependency with zero false alerts—but one integration still failed a hidden test.

INTEGRATED SUCCESS3/4

with PACT

DEPENDENCIES FOUND4/4

no missed handoffs

FALSE ALERTS0

across PACT trials

WANT THE PROTOCOL DETAILS?

The simple story is here. The machinery is one click away.

Explore sessions, checkpoints, cursors, ports, drivers, MCP, the SDK, and the live protocol graph in the documentation.

Open the documentation

THE PROJECT SHOULD OUTLIVE THE PROMPT

Give your coding agents a shared way to work.

Start the quickstart Explore Team mode