kiro CLI 3.0 launched november 3, 2026. it ships cloud sessions, persistent memory via /memories, and spec mode in the terminal - real improvements. it also retires the standalone desktop IDE. macOS users are auto-migrated to the CLI on their next update.
if you were using kiro's visual interface for structured development work, this is a meaningful change. the Workflows panel, the approval checkpoints, the visual pipeline showing where a task is in the feature-pipeline sequence - those are gone. what you get is a capable CLI with cloud-backed sessions and cross-session memory.
this post covers what the transition means in practice, and what your options are.
what the kiro desktop app offered
the kiro visual IDE (the "Classic" app, now retired) was not just a wrapper around the CLI. the Workflows panel showed a structured pipeline with nested steps - requirements, design, implementation, review - and approval gates displayed as checkpoints. you could see the pipeline state at a glance: which step was running, what had been approved, what was waiting. the spec artifacts (requirements.md, design.md, tasks.md) surfaced in the editor panel alongside the agent's work.
for teams running structured development work - not just "run agents and see what happens" - that visual context mattered. structured workflows produce approval decisions at several points. having those decisions visible and in context is different from reading CLI output and deciding whether to continue.
the value was not the IDE itself. it was the visual layer on top of a structured process - stages in view, decisions surfaced, pipeline state legible without digging into files or reading terminal output.
what CLI 3.0 adds - and what changes
to be fair: kiro CLI 3.0 is a real upgrade in some areas. cloud sessions let you start a long-running workflow and disconnect - the work continues in a managed sandbox and you can reconnect later without losing state. /memories adds genuine cross-session context persistence, something the desktop app lacked. spec mode in the CLI makes the structured pipeline scriptable and automatable in ways the GUI couldn't support.
the three workflow recipes run identically: feature-pipeline (requirements → design → implementation → review → PR), investigate, and publish-pr. the structure is there. what the CLI removes is the visual layer - the pipeline panel, the step checkpoints, the overview that made it easy to see where a task is and what needs your attention. approval decisions happen in the terminal.
pricing is unchanged: free (limited credits), pro $20/user/month, pro+ $40/user/month. all inference routes through AWS Bedrock on kiro's key, not yours.
the VS Code extension still ships and provides some visual context. it's not the standalone desktop app, but it's closer than the raw CLI for teams already in VS Code.
your options
stay on kiro CLI or VS Code extension. if the cloud sessions or persistent memory were features you wanted, the trade-off probably works. the workflow recipes run the same. teams that cared about the structured spec artifacts more than the visual pipeline will find the CLI equivalent. the VS Code extension brings back some visual context if you're in that editor.
use the spec artifacts as your process, CLI as the tool. if you were using kiro primarily for the structured spec artifacts and found the visual UI incidental, the CLI is functionally equivalent. spec-driven development doesn't require a visual interface - it requires discipline around the artifacts themselves. the spec-driven development guide covers this approach independently of any specific tool.
look for a desktop-first tool that kept the visual pipeline. if the visual interface was central to how you used kiro - stages in view, approval checkpoints, knowing at a glance what the agent is doing and what needs your attention - then a tool that stayed desktop-first is worth evaluating. the CLI transition is real; not every team will find it acceptable for production workflows.
what to look for in a structured alternative
the structured workflow was kiro's thesis. if that's what you valued, the right alternative shares these properties - even if the implementation differs:
- stages with real approval gates. not just "run agents in sequence" but explicit checkpoints where you decide whether to continue. the gap between parallel runners and structured tools is whether you can stop work at a gate before it goes somewhere wrong. see why AI coding agents need hard stage boundaries.
- a design step before implementation. kiro's design.md was a checkpoint before agents started writing code. the tool you move to should have something equivalent - a stage where the shape of the work is agreed before any code is produced. see design-first agentic development.
- code review that closes the loop. kiro's feature-pipeline gates on a review verdict before the PR ships. a replacement should have a review stage that runs before merge, not just CI checks after the fact.
- your subscription, not vendor credits. kiro's Bedrock-credit model works for some teams. if you want to avoid credit management and cloud routing of your code context, a local-first tool with bring-your-own-key economics is the alternative model.
the broader context
kiro's CLI move is part of a pattern. conductor joined Meta in november 2026 and stepped back from local tooling. paradev went MIT open-source. claude code ships dynamic workflows natively. the agentic coding market is sorting into two layers: free or open-source runners (paradev, claude code native) and tools that add structured process on top.
the tools that remain valuable are the ones that do something the free runners don't - structured stages, approval gates, visual context, team-level process. kiro bet that cloud sessions and cross-session memory are the right differentiator. some users will follow that bet. others will find the visual pipeline was more important than they realized, and want something that kept it.
defract is built for the second group. it's a dedicated macOS and windows desktop app - not an IDE extension - that runs a visual development pipeline on your own Anthropic subscription: story → design (a rendered visual reference before any code) → architecture → implementation → specialist review → release. all of it runs locally; code context never leaves your machine. the pipeline is user-authored, not vendor-preset templates. it's free to download.
if you used kiro's visual pipeline and want to understand how defract compares directly, the defract vs kiro page covers the specific differences in full.
defract
defract is the structured lifecycle tool that stayed desktop-first. free, no caps, no signup.