phuryn/swarm-protocol

Coordination protocol for agent-first teams. No UI. No sprints. No Jira. Just state sync.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 13 minutes ago
Added to GitGenius on August 31st, 2026
Created on March 13th, 2026
Open Issues & Pull Requests: 6 (+0)
Number of forks: 8
Total Stargazers: 53 (+0)
Total Subscribers: 0 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.5 hours
Mean response time: 29.1 hours
90th percentile: 38.8 hours
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 143 days
Stale 30+ days: 5
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • good first issue (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Swarm Protocol is a coordination protocol that enables agent-first teams to synchronize work across multiple developers and AI agents without traditional project management tools.

The tool solves the multiplayer coordination problem: when multiple developers each run their own AI agents on a shared codebase, those agents need to know what work is in flight, which files are being edited, and what tasks are unblocked and ready to claim. Without coordination, agents collide on the same files, duplicate work, and lose context between sessions. Swarm Protocol addresses this through state synchronization exposed as an MCP server—the same protocol Claude Code already speaks. Agents query shared state to see what's happening, claim work, detect file conflicts, and hand off tasks. The integration pattern centers on dropping a coordination file into the repository; agents then coordinate automatically without manual configuration.

This tool is built for teams of multiple developers where AI agents are the primary development interface—the workflow of telling Claude Code what to build and having teammates do the same simultaneously. It operates at the inter-session, inter-human layer, complementary to tools like Claude Code Agent Teams which coordinate within a single session. It is not intended for solo developers running multiple agents in parallel, nor as a Jira replacement or general project management system. The distinction is fundamental: existing tools solve single-player agent parallelism; this solves multiplayer coordination across a shared codebase.

The project is in alpha with nineteen MCP tools implemented and integration tests passing, built in public. Development is active with a focus on the core coordination primitives and the CLAUDE.md integration pattern as central to the design.