AWS / Coding Agents
Kiro pulls ahead of Q Dev
Until now Q Developer Pro and Kiro had been moving in step as siblings under AWS. But on Sept 16, Kiro gained Claude Fable 5.1 — while Q Developer Pro hasn't received a single new model.
Not a sibling anymore — a successor
AWS is quietly consolidating around Kiro rather than running two tools in parallel.
Per AWS's own "Amazon Q Developer end-of-support announcement" blog post, Q Developer Pro has been capped at Claude Opus 4.6 since May 29, 2026, and new signups already closed on May 15, 2026. The post states an explicit end-of-support date of April 30, 2027 for the IDE plugins and paid subscriptions as a whole — this is no longer two sibling products moving together, but a formal migration plan.
Kiro is where that traffic is meant to land. On September 16, 2026, the official Kiro blog announced Claude Fable 5.1, a model built for long-horizon, autonomous coding tasks, with a 1M-token context window and claimed reliability gains on complex multi-file refactors and long autonomous runs. Around the same period, Kiro had already shipped "Kiro Crew," a 24/7 autonomous task orchestrator that lets multiple sub-agents run work in parallel and only surfaces it for review once done. Q Developer Pro has neither.
The gap, in figures
Kiro's new features aren't unconditional, though. Fable 5.1 is currently available only to Kiro enterprise customers who have enabled "Model Governance." Kiro Crew's core feature, "Crew Members," is likewise an opt-in preview enabled from Settings → Developer → Feature Previews. Kiro is genuinely ahead, but that lead itself hasn't fully rolled out to every user yet.
| Q Developer Pro | Kiro |
|---|---|
| Frozen at Claude Opus 4.6 (since May 29) | Supports Claude Fable 5.1 (since Sep 16, needs Model Governance) |
| No autonomous orchestration feature | Kiro Crew enables 24/7 autonomous runs (preview) |
| New signups closed May 15, 2026 | Actively developed as AWS's flagship coding agent |
| End of support set for April 30, 2027 | No end-of-support date announced |
Who it helps, and how
Engineers
Staying on Q Developer Pro means no new models are coming. If long autonomous runs or multi-file refactors matter to you, evaluating a move to Kiro is the practical call.
Business / budget owners
Q Developer Pro's end-of-support date is already fixed at April 30, 2027. Build migration cost into your next contract renewal or budget cycle now rather than later.
PMs
Kiro Crew is still a preview that needs a settings toggle to enable. Plan team rollout as "pilot first, then expand" rather than assuming it's ready out of the box.
The cost of staying on a frozen product builds up quietly, not all at once.
It's time to look at Kiro
The counterpoint is worth stating plainly: both Fable 5.1 and Kiro Crew on Kiro are still limited-access or preview features, not a full rollout. Individuals and small teams outside the enterprise tier may not feel the benefit yet. And moving off Q Developer Pro means switching tools outright, with real cost in rebuilding workflows and IDE integrations.
Concretely: (1) Q Developer Pro users should first check whether their contract falls under the April 30, 2027 end-of-support date, (2) teams doing heavy long-running or multi-file autonomous work should start a pilot migration to Kiro this quarter, and (3) teams using Kiro Crew should treat it as a preview feature and avoid putting it on the critical path. Nothing in the current announcements suggests Q Developer Pro will receive new models again — in practice, consolidation onto Kiro looks like the default path.