Top-heavy anchors
Cline, Continue, and Kilo dominate adoption and define the practical default.
Sector Radar
VS Code AI Coding Agent Extensions
Diversum analyzed 22 source-verified VS Code AI coding-agent extensions to map the IDE-agent default, protocol-client boundary, lineage signals, and why this sector forms the third Super Cluster bridge candidate.
Corpus denominator: 22 in-cluster accepted candidates. Evidence snapshot: 2026-05-17.
What we found
The IDE-agent default is real, but the edges matter.
This radar maps sector position rather than declaring winners. Protocol clients, Claude Code bridges, and lineage-bearing repos are visible because they shape the boundary.
Protocol boundary
MCP and ACP surfaces survive, but they are separated instead of collapsed into one protocol bucket.
Lineage visibility
Kilo and Claude Code Local carry lineage notes without being treated as hidden verifier overrides.
Super Cluster bridge
The sector connects MCP/session/local-process traits to TypeScript/webview/extension packaging traits.
Interactive evidence graph
Explore why repositories cluster together.
Connections are generated from report evidence: shared centroid traits, protocol/runtime surfaces, workflow themes, lineage/client-family notes, and adjacent boundary signals.
Read next
Report artifacts
Public artifacts keep denominator, source, limitation, and correction paths visible.
Full report
Executive summary, cluster map, sector health, findings, gaps, and reader actions.
Evidence graph
Interactive 3D map of repo connections by traits, protocol surfaces, workflow themes, lineage notes, and adjacent boundaries.
Chart-ready data
Role composition, health metrics, centroid traits, protocol surfaces, and score matrix.
Centroid definition
The 10-trait default VS Code AI coding-agent extension pattern.
Calibration table
All 22 repositories scored across five radar dimensions with rule traces.
Methodology
Boundary rules, limitations, public language, and correction process.