pvestal

AI Team Sync — AI skill for Claude Code

AI community

Coordinate multiple AI coding agents (Claude Code, Cursor, Codex) on one repo — declared sessions, file scope locks (advisory/exclusive), and shared decisions, surfaced in VS Code, a browser dashboard.

How to install AI Team Sync

This entry records only its repository, not the path inside it, so there is no exact command to give. Open pvestal/ai-team-sync and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What AI Team Sync does

Alternatives in AI

Define — Definition phase - Clarify and scope problems with multi-AI consensus 2.8k ★
Agentchattr — Free, local chat where AI coding agents can tag each other, talk, and coordinate with you 1.5k ★
Kibitz — Real-time decoded feed of AI agent actions — monitor multiple Claude Code & Codex sessions, see exactly what e 521 ★

README

ai-team-sync

Stop AI agents (and humans) from stepping on each other's work.

When two devs both tell their AI agents to change the same files, nobody knows until conflicting PRs appear. ai-team-sync gives instant visibility — who's working on what, and why — through declared **sessions**, file **scope locks** (advisory or exclusive), and logged **decisions**. It surfaces in VS Code, a browser dashboard, a CLI, and natively in Claude Code via MCP.

Status: built as a personal multi-agent coordination tool, used daily. Small, dependency-light, MIT-licensed — useful if you run more than one coding agent against the same repo.

![ai-team-sync dashboard — who's working on what, color-coded by developer, with the files each has open](docs/dashboard.png)

*The live dashboard: each agent/developer's open files at a glance, color-coded — so nobody edits the same file blind.*

Quickstart

# 1. install + run the server (API + dashboard on :8400)
pip install -e .
ats-server &

# 2. announce what you're working on — teammates/agents see it instantly
ats session start -s "src/auth/**" -d "Refactoring auth to JWT"

# 3. claim a path so others get blocked/warned, with a reason they can see
ats lock add "src/auth/**" --mode exclusive --reason "JWT migration, #1234"

# 4. before you touch a file, check it's free
ats lock check src/auth/middleware.py        # exits non-zero if locked

# 5. see who's working on what
ats team

# 6. record a decision so it outlives the chat session
ats decision log "Chose JWT over sessions" -c JWT -r "session cookies" \
  --reason "stateless auth for horizontal scaling"

# 7. wrap up — releases locks, notifies the team
ats session complete -m "Done"

Dashboard: `http://localhost:8400/dashboard`. For Claude Code, wire up the [MCP server](#mcp-server-for-claude-code) so it does steps 3–4 automatically.