agentsmesh matrix
Display the feature-target compatibility matrix for your current configuration. Shows which features are supported natively, embedded as projected skills, or not supported for each configured target.
Project vs global: Without --global, each cell reflects project catalog levels (descriptor.capabilities) combined with your agentsmesh.yaml conversion settings. With --global, cells use global catalog levels (descriptor.globalSupport.capabilities when present, otherwise the same as project). Those catalog tables are the source of truth for documentation — see the Supported tools reference (Feature matrix (project scope) and Feature matrix (global scope)). The SUPPORT_MATRIX and SUPPORT_MATRIX_GLOBAL exports in src/core/matrix/data.ts match those tables.
Usage
agentsmesh matrix [flags]Flags
| Flag | Description |
|---|---|
--global | Show the matrix for canonical home config under ~/.agentsmesh/. |
--targets <csv> | Limit matrix columns to specific target IDs. |
--verbose | Show detailed feature notes alongside the matrix. |
Examples
Show full matrix
agentsmesh matrixShow matrix for specific targets
agentsmesh matrix --targets claude-code,cursor,copilotShow matrix with detailed notes
agentsmesh matrix --verboseShows per-file details for the canonical features present in the current project.
Show the global-mode matrix
agentsmesh matrix --globalSample output
Column headers match the targets list in your agentsmesh.yaml (here: every built-in target). Feature labels include counts when your canonical tree has items (for example commands (2) or additional rules (1)). Set NO_COLOR=1 to print plain symbols without ANSI colors. The block below illustrates project-scope catalog symbols for that full target list.
┌────────────────┬────────────┬────────────┬────────────┬────────────┬────────────┬────────────┬────────────┬────────────┬────────────┬────────────┬────────────┬────────────┐│Feature │Claude │cursor │copilot │continue │junie │kiro │gemini-cli │cline │codex-cli │windsurf │antigravity │roo-code │├────────────────┼────────────┼────────────┼────────────┼────────────┼────────────┼────────────┼────────────┼────────────┼────────────┼────────────┼────────────┼────────────┤│rules │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ ││additional rules│ ✓ │ ◆ │ ✓ │ ✓ │ ✓ │ ✓ │ ◆ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ ││commands │ ✓ │ ✓ │ ✓ │ ◆ │ ◆ │ – │ ✓ │ ✓ │ ◆ │ ✓ │ ◐ │ ✓ ││agents │ ✓ │ ✓ │ ✓ │ – │ ◆ │ ✓ │ ✓ │ ◆ │ ✓ │ ◆ │ – │ – ││skills │ ✓ │ ✓ │ ✓ │ ◆ │ ◆ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ ││mcp │ ✓ │ ✓ │ – │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ✓ │ ◐ │ – │ ✓ ││hooks │ ✓ │ ✓ │ ◐ │ – │ – │ ✓ │ ◐ │ ✓ │ – │ ✓ │ – │ – ││ignore │ ✓ │ ✓ │ – │ – │ ✓ │ ✓ │ ✓ │ ✓ │ – │ ✓ │ – │ ✓ ││permissions │ ✓ │ ◐ │ – │ – │ – │ – │ ◐ │ – │ – │ – │ – │ – │└────────────────┴────────────┴────────────┴────────────┴────────────┴────────────┴────────────┴────────────┴────────────┴────────────┴────────────┴────────────┴────────────┘
Legend: ✓ = native ◆ = embedded ◐ = partial – = not supportedLegend
| Symbol | Meaning |
|---|---|
✓ | Feature maps directly to the tool’s native config format. |
◆ | Feature is projected into a compatible format with metadata for round-trip import. |
◐ | Limited support — some fields or behaviors may not round-trip. |
– | Not supported. Feature is skipped for this target. |
Using the matrix for planning
Before adding a new feature to your canonical config, run agentsmesh matrix to understand which tools will receive it natively and which will receive an embedded projection. This helps set expectations for team members using different tools.