Kiro

At a glance

What Kiro does

Spec mode, Vibe mode, Steering files, Hooks, MCP, Agent Hooks, VS Code import

Best for

Spec-driven development with structured requirements, design docs, and tasks before code generation

Works well with

Conflicts & caveats

• Kiro's spec mode is tuned for Claude models — GPT-4o may work but spec-driven flows are best with Claude.
• GitHub Copilot does not officially support Kiro.
• Continue.dev only supports VS Code and JetBrains — your IDE is Kiro.
• Codeium does not officially support Kiro — use VS Code, JetBrains, Vim, or Neovim.
• Cursor built-in only runs inside the Cursor editor — your IDE is Kiro.
• Cline only supports VS Code and JetBrains IDEs — your IDE is Kiro.
• Windsurf Cascade only runs inside Windsurf — your IDE is Kiro.
• Sourcegraph Cody does not officially support Kiro — use VS Code, JetBrains, or Visual Studio.
• Tabnine does not officially support Kiro.
• Amazon Q Developer does not officially support Kiro — use VS Code or JetBrains.
• JetBrains AI Assistant only runs inside JetBrains IDEs — your IDE is Kiro.
• Qodo officially supports VS Code and JetBrains — your IDE is Kiro.
• Supermaven only supports VS Code, JetBrains, Neovim, and Zed — your IDE is Kiro.
• Zed Agent only runs inside the Zed editor — your IDE is Kiro.
• Augment Code officially supports VS Code, JetBrains, Vim, and Neovim — your IDE is Kiro.
• OpenCode is a terminal-first CLI; running it inside Kiro works but the experience is in the embedded terminal.
• Amp (Sourcegraph) officially supports VS Code and JetBrains — your IDE is Kiro. Use the CLI version otherwise.
• Sourcegraph Cody (Enterprise) supports VS Code, JetBrains, and Visual Studio — your IDE is Kiro.
• Cursor CLI works in any terminal but needs an active Cursor subscription — your IDE is Kiro, which is fine but the cost is tied to Cursor.
• @codebase indexing is a Cursor-only feature, but your IDE is Kiro.
• Cursor Background Agents are dispatched from Cursor (desktop or mobile) — your IDE is Kiro.