Amazon Q Developer CLI is now a legacy catalog entry. AWS documentation says the Amazon Q Developer CLI has been rebranded to Kiro CLI, and the current forward path for this command-line agent lineage is Kiro.
What changed
Q CLI became Kiro CLI - AWS's current documentation directs users from Amazon Q Developer CLI to Kiro CLI. Existing Q CLI users should evaluate the Kiro migration path rather than treat this as a separate current agent.
Historical relevance - Q CLI matters because it established AWS's terminal-agent workflow and is still relevant to teams that installed it before the Kiro transition.
Migration tracking - DevThrottle tracks this entry so users searching for Amazon Q CLI understand why the active recommendation points to Kiro CLI.
Autonomy level
Level 3 historically, but current evaluation should happen against Kiro CLI.
Strengths
- Important migration context for AWS-heavy teams
- Clear lineage into Kiro CLI
- Useful historical reference for DevThrottle compatibility work
Limitations
- Not the current AWS/Kiro CLI direction
- Feature claims should not be reused for Kiro without fresh verification
- Use the Kiro CLI entry for current guidance