You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -36,6 +35,21 @@ This is a **coordination protocol, not a project management tool.** Jira was bui
36
35
37
36
The CLAUDE.md integration pattern is as important as the server itself. Agents coordinate automatically without humans configuring anything.
38
37
38
+
## How This Relates to Agent Teams, Code Review, and Other Multi-Agent Tools
39
+
40
+
These tools are complementary, not competing. They operate at different layers:
41
+
42
+
-**Claude Code Agent Teams** coordinates agents within a single session — one lead, parallel teammates, shared task list. Intra-session.
43
+
-**Claude Code Review** dispatches parallel review agents against a single PR. Intra-PR.
44
+
-**VS Code multi-agent** runs Claude, Codex, and Copilot agents side by side for one developer. Intra-machine.
45
+
-**AgentConductor** dynamically adjusts agent communication graphs per coding problem. Intra-problem.
46
+
47
+
**Swarm Protocol** coordinates across sessions — multiple humans, each running their own agents, on a shared codebase. Inter-session, inter-human.
48
+
49
+
An agent uses Agent Teams internally for its own subtask parallelism. It uses Swarm Protocol's MCP tools to know which work to pick up, which files to avoid, and what context the previous agent left behind.
50
+
51
+
The single-player problem is getting solved. The multiplayer problem hasn't started.
52
+
39
53
## Who Is This For
40
54
41
55
Teams of 2+ developers where AI agents (Claude Code, etc.) are the primary development interface. If your workflow is "open terminal → tell Claude Code what to build → review the PR" and teammates are doing the same thing at the same time — this is the missing layer.
@@ -63,7 +77,7 @@ See [LANDSCAPE.md](docs/LANDSCAPE.md) for the full competitive breakdown.
63
77
|**Intent**| A unit of desired outcome — not a ticket. Lifecycle: `draft → open → claimed → done`. Has constraints, acceptance criteria, and dependency chains. |
64
78
|**Claim**| "I'm working on this." Tracks which files are being touched. Includes heartbeat — claims with no heartbeat for 30 min get flagged as stale. |
65
79
|**Signal**| Event notification: completion, blocked, conflict, info. When a completion signal fires, dependent intents auto-unblock. |
66
-
|**Context Package**| Everything an agent needs to start work — intent, dependencies, active claims on overlapping files, recent signals, team conventions — assembled in one call via `get_context`. |
80
+
|**Context Package**| Everything an agent needs to start work — intent, dependencies, active claims on overlapping files, recent signals, team conventions — assembled in one call via `get_context`. Solves the state handoff problem: when Agent A completes work, the structured output travels with the task so Agent B gets a stable input contract, not just "the file changed." Sequential dependency chains require this — Agent B's correctness depends on Agent A's output schema being stable across runs. |
- MCP server with task queues, file locking, and built-in messaging between agents
81
105
- Standard workflow: initialize → claim tasks → lock files → work → complete
82
106
- Runs entirely locally, data stored in Git repo
@@ -86,6 +110,20 @@ This is single-player multiplayer vs. true multiplayer. Different product catego
86
110
87
111
---
88
112
113
+
## Research Papers
114
+
115
+
### AgentConductor (Chinese labs, Feb 2026)
116
+
- Dynamic topology evolution for multi-agent code generation
117
+
- LLM-based orchestrator infers agent roles and task difficulty, constructs task-adapted DAG topology
118
+
- Easy tasks get small, cheap teams. Hard tasks get large, highly connected teams.
119
+
- Manager rewrites the team workflow on failure based on error feedback
120
+
- 68% token cost reduction vs. fixed topologies, 14.6% accuracy improvement on competition-level code
121
+
- Validates our core thesis: static agent pipelines waste compute on simple tasks and fail on complex ones
122
+
- Still single-problem scope — solves intra-session topology, not cross-session coordination
123
+
- Paper: https://arxiv.org/abs/2602.17100
124
+
125
+
---
126
+
89
127
## What Jira Is Doing
90
128
91
129
- Atlassian launched **"agents in Jira"** (open beta, Feb 2026) — assign tasks to AI agents from the same dashboard as human employees
@@ -137,11 +175,14 @@ This is single-player multiplayer vs. true multiplayer. Different product catego
137
175
| Team support | None | Multi-team with conventions |
138
176
| State sharing | Env vars, shared files | PostgreSQL, real-time via MCP |
139
177
| Draft workflow | No | Draft → publish → claim |
178
+
| State handoff | Implicit (file system changes) | Explicit (Context Package with structured output + dependency schema) |
140
179
141
180
## Key Positioning
142
181
143
182
- Not "Jira but with AI" — that's what Atlassian is doing and they'll always do it better
144
183
- Not "one dev managing agent fleet" — that's what 1Code, CCPM, tick-md do
184
+
- Not "smarter agents in one session" — that's what Agent Teams, Code Review, VS Code multi-agent, and AgentConductor do
145
185
-**"Coordination infrastructure for agent-first teams"** — a new category
146
186
- The market for this is tiny today and enormous in 12-18 months
187
+
- March 2026 signal: Anthropic shipped Agent Teams AND Code Review. Microsoft shipped multi-agent VS Code. AgentConductor paper dropped. All single-player. The multiplayer gap is widening, not closing.
147
188
- First mover who names the category owns the narrative
0 commit comments