Claude doesn't know what other Claude sessions are doing. Traffic Cop is the shared brain that tells every AI agent what's locked, what's building, and what's safe to touch — so they can work together without stepping on each other's files.
Traffic Cop exists because AI can now work with AI.
You can have five Claude sessions open at once, each working a different part of your codebase. That's powerful — until two of them touch the same file, or both try to kick off a build at the same moment. They have no awareness of each other. Traffic Cop gives them that awareness. It's not a tool for developers to manage AI. It's a tool for AI to manage itself.
AI coding tools are powerful individually. Together, without coordination, they create new classes of failures.
Two Claude sessions both bump the iOS build number at the same time. TestFlight rejects both.
Two APK build processes access the Android signing keystore simultaneously. Both APKs come out invalid.
Agent A edits a native module while Agent B's iOS build is running. The build picks up half-written code.
A Claude session crashes mid-checkout. The files stay locked forever — until someone manually cleans up.
"Is anyone building right now?" — nobody knows. Each AI session is an island.
AI sessions get a "file locked" error and stop cold. There's no queue, no ETA, no handoff — just a wall with no way around it.
Install once, forget it's there — until it saves your build.
Runs as a Windows service in the background. Maintains the source of truth for all locks and builds via SQLite. Connects to Claude via MCP protocol.
A free .skill file for Claude/Cowork. Automatically checks the cop before every checkout or build — no manual step required.
Every session gets a clear green or red signal. When blocked, AI explains why, gives an ETA, and suggests what to work on instead.
Stale locks from crashed sessions are automatically released after 30 minutes. No manual intervention needed.
// Agent calls tc_checkout before editing tc_checkout({ session_id: "sess_abc123", files: "ios/, app.json, eas.json", purpose: "Fix push notification entitlements" }) // Cop responds { status: "APPROVED", expires_at: "2:45 PM", message: "🟢 3 files locked for 60 minutes. Remember to tc_checkin when done." } // Meanwhile, another agent tries to build iOS... tc_request_build({ build_type: "ios" }) { status: "CONFLICTS", conflicts: [{ file: "ios/", session: "Claude Chat A", held_for: "3m" }], advice: "🟡 ios/ is checked out by Claude Chat A. Ask them to checkin first." }
Lock any file or directory before editing. Conflict detection is instant. Locks auto-expire so your team never stays blocked.
iOS, APK, and web builds each know which files they need. The cop automatically blocks checkouts that would corrupt a running build.
Blocked sessions queue automatically. The moment the holding session checks in, the lock is handed directly to the next agent waiting — no polling, no manual retry. Claude sees exactly who has the file, what they're doing with it, and gets the grant notification the instant it's ready.
Sessions send heartbeats to stay alive. If a session dies, the cop detects it and auto-releases its locks after a configurable timeout.
Any session can call tc_get_status to see all active locks, running builds, and recent build history — across the whole team.
The server ships as a compiled Go binary — no source code in your hands. Licensed with Ed25519 cryptographic keys, not serial numbers.
One installer script sets up the server as a Windows service that starts automatically and restarts on failure. Works silently in the background.
Binaries for Windows, macOS, and Linux. Any machine on the team can run the server — or connect as a client.
Remote and distributed teams coordinate across networks via an encrypted relay. No VPN required — just connect and the cop handles the rest.
The Cowork skill is open source and free forever. The server is what requires a license — the client never has a paywall.
Every machine connected to Traffic Cop is one seat. The skill is always free — only the coordination server requires a license.
Need more than 20 computers or a custom deployment? Contact us for enterprise pricing.