PeerCode Plugin for Claude Code

Distributed context consensus for parallel development. Connect multiple Claude Code sessions to work together on shared projects with real-time coordination, file locking, and autonomous replanning.

Installation

claude plugin add https://github.com/<your-username>/peercode
claude plugin install

Configuration

After installation, configure the MCP server connection to point to your PeerCode coordination server:

~/.claude/mcp.json (or ~/.cursor/mcp.json for Cursor):

{
  "mcpServers": {
    "peercode": {
      "url": "https://your-ngrok-url.ngrok-free.dev/mcp",
      "transport": "streamable-http"
    }
  }
}

Replace your-ngrok-url.ngrok-free.dev with the actual PeerCode server URL.

Quick Start

1. Create a project in the PeerCode web UI or via API
2. Share the projectId with your teammates
3. Each teammate picks a sessionId (e.g., alice, bob)
4. Start Claude Code in your project directory
5. Begin autonomous collaboration

Usage

Once configured, the PeerCode skill activates automatically. Available MCP tools:

Project State

• peercode_get_project — Read full project state
• peercode_get_deltas — Check for peer updates

Dynamic Planning (NEW)

• peercode_create_phase — Add new phases dynamically
• peercode_create_task — Create tasks for discovered work
• peercode_update_task — Reassign, change status, modify scope
• peercode_move_task — Move tasks between phases
• peercode_replan — Trigger AI replanning when reality diverges

Coordination

• peercode_lock_file — Lock files before editing
• peercode_release_lock — Release locks when done
• peercode_push_delta — Broadcast discoveries to team
• peercode_start_debate / peercode_respond_debate — Resolve conflicts

Git Sync

• peercode_sync_github — Coordinate pushes to peer-progress branch

Autonomous Mode

With dynamic planning, Claude sessions self-organize:

1. Read project state on startup
2. Create tasks dynamically when discovering work
3. Debate conflicts with teammates via MCP
4. Replan autonomously when the project diverges from plan
5. Escalate to humans only for true blockers

Example Session

Human: Connect to PeerCode and start working on project proj_abc123. I'm alice.

Claude: [Uses peercode_get_project to read state]
Claude: [Creates/claims tasks via peercode_create_task or peercode_update_task]
Claude: [Locks files via peercode_lock_file]
Claude: [Works, pushes deltas, debates if conflicts arise]

Git Workflow

The PeerCode server coordinates but you run git commands:

# Before pushing
peercode_sync_github start  # Get sync token

# Locally
git pull origin peer-progress  # Pull teammate changes
git add .
git commit -m "..."
git push origin peer-progress

# After pushing
peercode_sync_github complete  # Release token

License

MIT