Skip to content

Supported Harnesses

This page is the canonical 5-tier support matrix for AI coding harnesses (“agents”) that Spec Kitty integrates with. Each row conforms to the HarnessEntry schema in kitty-specs/spec-kitty-3-2-docs-01KS4KSZ/data-model.md. The research procedure that backs each classification lives in docs/archive/plans/3-2-doc-publication/3-2-harness-research-method.md.

Access date for citations: 2026-06-03.


Tier legend

TierOne-line definition
first_classInstalled by default; canonical UX (slash command or Agent Skill); integration-tested; current external doc citation.
supportedInstalled by the standard installer; current external doc citation; may lack first-class integration tests or have a degraded mechanism.
partialInstaller touches the host but coverage is incomplete, or no current external citation could be located.
experimentalProvisional coverage that may break without notice; typically depends on another harness’s installation.
archivedNo longer covered by the installer, or the upstream project is deprecated; coverage (if any) lives in docs/migrations/.

Full tier criteria and promotion rules are maintained in docs/archive/plans/3-2-doc-publication/3-2-harness-research-method.md §5 and §6.


Support matrix

HarnessKeyInstalled surfaceMechanismTierCitation (accessed 2026-06-03)Notes
Claude Codeclaude.claude/commands/slash_commandfirst_classhttps://docs.claude.com/en/docs/claude-code/overviewReference harness; integration-tested in src/specify_cli/.
Codex CLIcodex.agents/skills/spec-kitty-*/SKILL.mdskillfirst_classhttps://github.com/openai/codexHeaviest agent skills integration; canonical skill tree at .agents/skills/.
OpenCodeopencode.opencode/command/slash_commandsupportedhttps://opencode.ai/docs/spec-kitty.* command set installed via standard installer.
Cursorcursor.cursor/commands/slash_commandsupportedhttps://cursor.com/docs/spec-kitty.* command set installed via standard installer.
Google Gemini CLIgemini.gemini/commands/slash_commandsupportedhttps://github.com/google-gemini/gemini-cli/spec-kitty.* command set installed via standard installer.
Qwen Codeqwen.qwen/commands/slash_commandsupportedhttps://github.com/QwenLM/qwen-code/spec-kitty.* command set installed via standard installer.
Amazon Q CLIq.amazonq/prompts/promptsupportedhttps://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/Retained as legacy alongside Kiro rebrand per CLAUDE.md.
GitHub Copilotcopilot.github/prompts/promptsupportedhttps://docs.github.com/en/copilot/customizing-copilot/adding-custom-instructions-for-github-copilotPrompt-file mechanism; /spec-kitty.* set installed.
Augment Code (Auggie)auggie.augment/commands/slash_commandsupportedhttps://docs.augmentcode.com/auggie/overview/spec-kitty.* command set installed via standard installer.
Roo Clineroo.roo/commands/ (existing projects only)slash_commanddeprecatedhttps://docs.roocode.com/Roo Code shut down on 2026-05-15. spec-kitty init --ai roo is rejected; existing .roo/ dirs are preserved and a deprecation notice is shown on spec-kitty upgrade.
Kilo Codekilocode.kilocode/workflows/workflowsupportedhttps://kilocode.ai/docsWorkflow mechanism; /spec-kitty.* set installed.
Windsurfwindsurf.windsurf/workflows/workflowsupportedhttps://docs.windsurf.com/windsurf/cascade/workflowsWorkflow mechanism; /spec-kitty.* set installed.
Kirokiro.kiro/prompts/promptpartialhttps://kiro.dev/docsPrompt-file surface only for Spec Kitty 3.3 plugin-install scoping; not a plugin/Powers bundle candidate until upstream exposes and verifies a package primitive.
Google Antigravityantigravity.agents/skills/spec-kitty-*/SKILL.mdskillpartialhttps://www.antigravity.google/docs/rules-workflowsAntigravity stopped reading .agent/workflows/ on 2026-10-19; since 4.0.0rc8 its commands install as the shared command-skill packages (/spec-kitty-<command>) and old workflow files are archived by spec-kitty upgrade. Partial until a real-session smoke test is recorded.
Pi TUIpi.agents/skills/spec-kitty-*/SKILL.mdskillpartialhttps://pi.dev/docs/latest/skillsInstaller-supported command-skill packages; keep partial until a real-session smoke test is recorded.
Mistral Vibevibe.agents/skills/ via .vibe/config.toml skill_pathsskillexperimentalhttps://docs.mistral.ai/mistral-vibe/terminal/quickstartUses the shared .agents/skills/spec-kitty-* packages plus a .vibe/config.toml skill_paths entry. Behaviour may change with Vibe upstream.
Letta Codeletta.agents/skills/spec-kitty-*/SKILL.mdskillpartialhttps://docs.letta.com/letta-code/skillsInstaller-supported command-skill packages; keep partial until a real-session smoke test is recorded.

Cross-reference quick view

TierCountMembers
first_class2Claude Code, Codex CLI
supported9OpenCode, Cursor, Gemini CLI, Qwen Code, Amazon Q CLI, GitHub Copilot, Augment Code, Kilo Code, Windsurf
partial4Kiro, Google Antigravity, Pi TUI, Letta Code
experimental1Mistral Vibe
deprecated1Roo Cline (shut down 2026-05-15)
archived0
Total17

Promotion path

A harness moves up tiers only when new evidence lands. See docs/archive/plans/3-2-doc-publication/3-2-harness-research-method.md §6 for the full rule. Summary:

  1. partial → supported when (a) the installer produces a full /spec-kitty.* set, (b) a current external citation is recorded, and (c) at least one smoke test has been documented.
  2. supported → first_class when (a) integration tests exercise the harness end-to-end, (b) the mechanism is the harness’s canonical UX, (c) the per-harness page under docs/guides/harnesses/<key>.md is non-stub, and (d) the promotion is logged in CHANGELOG.
  3. Demotion happens when citations cannot be re-verified across two freshness audits, the upstream is deprecated, or the installer ceases to produce a valid surface.

Tier moves are recorded in this matrix’s row notes and the project CHANGELOG.


Maintenance

  • The inventory step is re-run on every release; the citation step is re-run on every release as part of the freshness audit (WP13).
  • This matrix is the published artifact; the procedure that backs it is maintained at docs/archive/plans/3-2-doc-publication/3-2-harness-research-method.md.
  • Per-harness “how-to” pages live at docs/guides/harnesses/<key>.md and are promoted under the plan’s matrix-first default (decision 01KS4KTS4V300M9MMTS1AJEGXY).