claudeers.
// Other

multi-agent-repo-protocol

Rules, git hooks and scripts that let several AI coding agents (Claude Code, Codex, DeepSeek) share one git repo without overwriting each other, with every c…

// Other[ cli ][ api ][ claude ]#claude#other◷ MIT$open-sourceupdated 22 days ago
Actively maintained
100/100
last commit 16 days ago
last release 16 days ago
releases 1
open issues 0

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up multi-agent-repo-protocol (git-clone project) into my current project.
Found on https://claudeers.com/multi-agent-repo-protocol
Repo: https://github.com/Soda-null/multi-agent-repo-protocol
Homepage/docs: —
Detected install method: git-clone → git clone https://github.com/Soda-null/multi-agent-repo-protocol
Category: other. Platforms: cli, api.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
active; community-verified: false. Confirm the source before running anything.
// or clone
git clone https://github.com/Soda-null/multi-agent-repo-protocol

// compatibility

Platformscli, api
Operating systems—
AI compatibilityclaude
LicenseMIT
Pricingopen-source
LanguagePython

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

multi-agent-repo-protocol

Rules, git hooks and small scripts that let several AI coding agents — Claude Code, Codex, a cheap API model, a local model — work in one git repository without overwriting each other, and let you find out afterwards which agent did what.

中文说明

The problem

When you use more than one agent on the same project, the same things go wrong again and again:

  • Agent B "cleans up" files that agent A had not committed yet. A's work is gone.
  • All agents commit under your one git identity. When something breaks, git blame says you.
  • An agent reads an old decision in a status file and follows it, because nobody removed it.
  • One agent calls another on its own and spends that agent's quota.
  • A cheap model is given a task that needs judgment, and its plausible-looking output is accepted.

The agents cannot talk to each other. Files are the only channel. So this protocol puts everything into files, and puts a machine check on every rule that a machine can check.

What is inside

PieceWhat it does
AGENTS.md (+ CLAUDE.md symlink)One constitution read by every agent
docs/agent_board.mdClaims table: who is working on which paths right now
.githooks/commit-msgRejects a commit without an Agent: <name> trailer, so every commit is attributed
scripts/agent_worktree.shGives each parallel agent its own working tree on agent/<name>
scripts/delegate.shSends a task to a cheaper agent — only if the task names a command that proves it correct
docs/decisions.md + docs/glossary.mdAppend-only decision ledger with an index, and one line per code name
scripts/check_current_docs.pyBlocks a commit when an entry file cites a superseded decision without saying so
scripts/check_doc_structure.pyEvery doc has a header card; indexes list every file; entry files stay small
scripts/worklog.py, new_log.pyDaily log, and hours derived from commit times (no tokens)
scripts/repo_hygiene.pyWeekly check-up: deletes only junk and merged branches, reports the rest
.claude/skills/close-session/A Claude Code skill: the end-of-session checklist

The rules in one screen

  1. Start: git pull, git status, read the board. Uncommitted changes belong to another agent: never revert, stash or tidy them.
  2. Claim your task on the board in your first commit; release it when done.
  3. Sign every commit with Agent: claude-code (or codex, deepseek, local, human). The hook enforces it.
  4. Stage your own paths by name. Never git add -A in a shared tree.
  5. Parallel work → separate worktrees. Merging into main is the human's call.
  6. Never silently reverse another agent's conclusion. Ledgers are append-only; without new evidence, write the disagreement down and let the human decide.
  7. Peers do not call peers. Codex and Claude Code are the human's two seats; neither invokes the other unless the human asks (delegate.sh needs --peer).
  8. Delegation needs an acceptance command. No command that proves the work right → the task is judgment work and stays with the expensive agent and the human.
  9. The most-read files state only what holds now. A superseded decision is removed or marked in the same clause; a checker enforces it.
  10. End: commit everything you finished. What you leave uncommitted is what the next agent destroys.

Why each rule exists, with the incidents behind it: docs/why.md.

Install

git clone https://github.com/Soda-null/multi-agent-repo-protocol.git
cd multi-agent-repo-protocol
./install.sh /path/to/your/repo

install.sh copies the template into your repository, never overwrites an existing file (it lists what it skipped), links CLAUDE.md to AGENTS.md, and sets core.hooksPath. Then fill in the "Project" section of AGENTS.md and §1 of STATUS.md.

Every clone needs the hooks enabled once:

git config core.hooksPath .githooks

Requirements: git ≥ 2.28, bash, Python ≥ 3.9. No Python packages. Tested on Linux, macOS and Windows.

Windows

Install Git for Windows (it brings Git Bash) and Python 3.9+, then in PowerShell:

.\install.ps1 C:\path\to\your\repo

What is different on Windows, and handled for you:

  • Line endings. .gitattributes keeps shell scripts and hooks at LF; with CRLF, bash fails with \r: command not found. If your repository already has a .gitattributes, the installer skips it — add the lines from template/.gitattributes yourself.
  • python3. Windows often has only python or py. The hooks and delegate.sh find a working Python 3 and make python3 ... acceptance lines work anyway. In PowerShell, run the scripts as python scripts\check_doc_structure.py.
  • Symlinks need Developer Mode. Without it, CLAUDE.md becomes a one-line file @AGENTS.md (Claude Code reads it as an import), and agent_worktree.sh skips linking untracked data rather than copying it.
  • Run the shell scripts (agent_worktree.sh, delegate.sh) from Git Bash. Git runs the hooks with its own bash, so commits from any terminal or app are checked.
  • Time zone names (LOG_TZ) need pip install tzdata on Windows; without it the local time is used, with a warning.

Delegation in practice

The expensive agent writes a short packet:

# Fix the broken links in docs/

## Steps
1. ...

**Acceptance:** `python3 scripts/check_links.py`

and runs scripts/delegate.sh docs/handoffs/2026-01-15-links.md. The script runs the cheap agent in its own worktree, runs the acceptance command, commits with Agent: deepseek only on PASS, and prints one line: PASS or FAIL. The expensive agent reads that line, not the cheap agent's transcript.

Launchers are set by environment variables (DEEPSEEK_CMD, CODEX_BIN, CLAUDE_CMD, LOCAL_MODEL), so any headless agent that takes a prompt and edits files can be the executor.

What this does not solve

  • An overclaim in prose. No checker can tell that a sentence says more than the evidence. The human is the only check, and the protocol says so instead of pretending otherwise.
  • Orchestration overhead. Writing a packet costs tokens. Delegate only when the work is much bigger than its specification (rule of thumb: packet < 1 KB, work > 20 KB of files).

Test

tests/smoke_test.sh

It installs the protocol into a throwaway repository and checks every gate: unsigned commits are rejected, stale decisions are caught, packets without an acceptance command are refused, peer calls without --peer are refused, a fake executor's work is committed with its trailer.

Origin

This grew out of a one-person research repository in which Claude Code, Codex and DeepSeek worked side by side for about two months (2026). The project content is not included; only the collaboration layer is.

License

MIT

// faq

What is multi-agent-repo-protocol?

Rules, git hooks and scripts that let several AI coding agents (Claude Code, Codex, DeepSeek) share one git repo without overwriting each other, with every commit attributed. It is open-source on GitHub.

Is multi-agent-repo-protocol free to use?

multi-agent-repo-protocol is open-source under the MIT license, so it is free to use.

What category does multi-agent-repo-protocol belong to?

multi-agent-repo-protocol is listed under other in the Claudeers registry of Claude-compatible tools.

6 views
★ 12 stars
unclaimed
updated 22 days ago

// embed badge

multi-agent-repo-protocol on Claudeers
[![Claudeers](https://claudeers.com/api/badge/multi-agent-repo-protocol.svg)](https://claudeers.com/multi-agent-repo-protocol)

// retro hit counter

multi-agent-repo-protocol hit counter
[![Hits](https://claudeers.com/api/counter/multi-agent-repo-protocol.svg)](https://claudeers.com/multi-agent-repo-protocol)

// reviews

// guestbook

0/500

// related in Other

🔓

符合nature论文学术表达和科研绘图的Skill

// otherYuan1z0825/⟨Python⟩★ 54,085◷ Apache-2.0[ claude ]
🔓

Anti-AI-slop design skill for Claude Code, Cursor, and Codex.

// otherNutlope/⟨CSS⟩★ 49,642◷ MIT[ claude ]
🔓

Huashu Design · HTML-native design skill for Claude Code · Claude Code 里 HTML 原生的设计 skill · 高保真原型 / 幻灯片 / 动画 + 20 设计哲学 + 5 维评审 + MP4 导出 · Agent-agnostic

// otheralchaincyf/⟨HTML⟩★ 28,944◷ MIT[ claude ]
🔓

Open source Ghostty-based macOS terminal with vertical tabs and notifications for AI coding agents. Built for multitasking, organization, and programmability.

// othermanaflow-ai/⟨Swift⟩★ 28,842◷ NOASSERTION[ claude ]
→ see how multi-agent-repo-protocol connects across the ecosystem