Spidersan
Available Now

Spidersan

Branch Coordination for AI Agents

Your AI team's coordination layer. Track branches, detect conflicts early, and get optimal merge order — so your agents can work in harmony.

npm install -g spidersan
View on GitHub →
~/my-project
spidersan register feature/auth --files "lib/auth.ts,api/login.ts"
✓ Registered branch: feature/auth (2 files)
spidersan conflicts
🕷️ Checking for conflicts...
⚠️ Conflict detected: lib/auth.ts
└─ Also modified by: feature/oauth (watsan)
spidersan merge-order
📋 Optimal merge order:
1. feature/oauth (watsan) — no dependencies
2. feature/auth (you) — after oauth merges
spidersan ready-check
✓ Ready to merge after feature/oauth

😰 Without Coordination

  • 10 AI agents, 1 file, 51 minutes of chaos
  • 12 merge conflicts requiring manual resolution
  • 2 build breaks pushed to main
  • Agents overwriting each other's work
  • No visibility into who's editing what

🕷️ With Spidersan

  • Same task completed in 5 minutes (10x faster)
  • 0 conflicts — detected before they happen
  • Optimal merge sequence calculated automatically
  • Real-time visibility into branch activity
  • Confidence level: 5/5
Features

Coordination for the Multi-Agent Era

🔍

Conflict Detection

Detect file conflicts between branches before you go too deep. Know exactly who's touching what files.

👁️

Watch Mode

Daemon mode that auto-registers file changes as you work. Real-time conflict warnings with Hub integration.

📊

Merge Ordering

Get topologically-sorted merge order. Know exactly which branches to merge first for zero conflicts.

🦺

Rescue Mode

Got 10+ abandoned branches? Scan, triage (MERGE/SALVAGE/ABANDON), and salvage good code from broken branches.

📜

Who-Touched

Show git history combined with agent activity for any files. See the full story of who changed what.

🤖

MCP Integration

Full Model Context Protocol server for AI agents. Seamless integration with Claude, Cursor, and other AI tools.

Integration

Part of the Treebird Ecosystem

Toak

Spidersan + Toak

Pause before merging — request human approval via Toak when Spidersan detects a conflict that needs a judgment call.

spidersan ready-check --require-approval
Learn about Toak →
envoak

Hub Credentials

Store your Spidersan Hub API keys securely in envoak. Share across machines without exposing secrets.

envoak push # includes SPIDERSAN_HUB_KEY
🧠

Watsan Knowledge

Query branch history and conflict patterns from the knowledge base. Learn from past coordination challenges.

watsan oracle "common auth conflicts"
Commands

Full Command Reference

spidersan init
Initialize Spidersan in the current project.
spidersan register --files
Register a branch with the files being modified.
spidersan list
List all registered branches and their file ownership.
spidersan conflicts
Show file conflicts between your branch and others.
spidersan merge-order
Get topologically-sorted optimal merge order.
spidersan ready-check
Verify branch is ready to merge (no WIP, no conflicts).
spidersan depends
Set or show branch dependencies.
spidersan stale
Find stale branches that haven't seen recent activity.
spidersan cleanup
Remove stale branches from the registry.
spidersan rescue
Start rescue mission for abandoned branch cleanup.
spidersan abandon
Mark a branch as abandoned (inactive).
spidersan merged
Mark a branch as merged and remove from active tracking.
spidersan sync
Sync the registry with actual git branches.
spidersan watch
Daemon mode: watch files and auto-register changes.
spidersan doctor
Diagnose local state and registry health.
spidersan config
View or edit configuration with guided wizard.
spidersan auto
Auto-watch start, stop, and status (config-based).
spidersan welcome
Onboarding guide and quick start walkthrough.

Advanced commands like who-touched, monitor, lock, and scan are available in the ecosystem plugin.

Use Cases

Built for AI-First Teams

🤖 Multi-Agent Coordination

Running 5 Claude agents in parallel? Spidersan ensures they don't step on each other's toes with real-time conflict detection.

🏗️ Post-Hackathon Cleanup

Got 20 branches from a weekend sprint? Use rescue mode to scan, triage, and salvage the good parts automatically.

👥 AI Pair Programming

Human + AI working together? Both register their branches and get instant alerts when overlapping work is detected.

🦅 Fleet Coordination

Orchestrating a flock of specialized agents? Spidersan provides the coordination layer that prevents chaos.

FAQ

Common Questions

Spidersan is a coordination layer for AI coding agents. It tracks which branches are modifying which files, detects potential merge conflicts before they happen, and provides optimal merge ordering so your agents can work in parallel without stepping on each other.

When you register a branch with spidersan register --files, Spidersan tracks which files you're modifying. When you run spidersan conflicts, it compares your file list against all other registered branches and alerts you to any overlaps. In watch mode, this happens automatically in real-time.

Yes! All 18 core CLI commands are MIT licensed and free forever — including init, register, conflicts, merge-order, watch, doctor, rescue, and more. Advanced ecosystem commands are available via the ecosystem plugin.

Run spidersan watch --agent myagent to start watching. Add --hub for real-time conflict warnings via the Spidersan Hub. Use --quiet to only show conflicts and suppress normal output. The watcher auto-registers files as you edit them with 1-second debouncing.

Spidersan works with any git-based workflow. It has explicit MCP integration for Claude, Cursor, and other AI tools that support Model Context Protocol. For other tools, use the CLI directly or integrate via the watch mode daemon.

Coordinate Your AI Fleet Today

Stop the chaos. Start the harmony.

npm install -g spidersan