DEV.co
MCP Servers · aws

amazon-q-developer-cli

Amazon Q Developer CLI is an open-source, Rust-based terminal agent that builds applications using natural language. The project is no longer actively maintained and has been superseded by the closed-source Kiro CLI; it will receive only critical security fixes.

Source: GitHub — github.com/aws/amazon-q-developer-cli
2k
GitHub stars
437
Forks
Rust
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryaws/amazon-q-developer-cli
Owneraws
Primary languageRust
LicenseApache-2.0 — OSI-approved
Stars2k
Forks437
Open issues1.3k
Latest releasev1.19.7 (2025-11-17)
Last updated2026-06-22
Sourcehttps://github.com/aws/amazon-q-developer-cli

What amazon-q-developer-cli is

A Rust-based agentic CLI leveraging LLMs to enable natural language application development. Built with MCP (Model Context Protocol) support, it provides a modular architecture across multiple Rust crates with TypeScript integration points.

Quickstart

Get the amazon-q-developer-cli source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/aws/amazon-q-developer-cli.gitcd amazon-q-developer-cli# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Rapid prototyping and scaffolding

Developers can quickly generate boilerplate code and project structures via natural language prompts from the terminal, reducing initial setup time.

Command-line developer productivity

Teams already using terminal-based workflows can integrate AI-assisted development without leaving the shell, streamlining local development loops.

Educational and exploratory use

Engineering teams experimenting with agentic development patterns and LLM-driven tooling can study the architecture without vendor lock-in (permissive licensing).

Implementation considerations

  • Rust toolchain dependency (rustup, nightly, stable) required for local development; prebuilt binaries available for macOS, Ubuntu, Debian, and AppImage.
  • High issue count (1,293) relative to star count (1,976) suggests unresolved bugs; assess whether outstanding issues affect your use case before adoption.
  • Dual licensing (MIT and Apache 2.0) requires choice at deployment time; clarify internal policy on which license governs your usage.
  • No active maintenance means security vulnerabilities may be discovered and patched slowly; risk assessment critical for any internet-facing or sensitive data handling.
  • MCP and LLM integration; ensure your LLM provider (AWS Bedrock, etc.) alignment and API stability assumptions are verified for your region and account.

When to avoid it — and what to weigh

  • Production-critical deployments requiring active maintenance — Project is deprecated in favor of Kiro CLI. Active maintenance and feature development have ceased; only critical security patches are provided.
  • Closed-source or proprietary requirement — This is open-source under dual MIT/Apache 2.0; if your compliance policy forbids open-source dependencies or requires proprietary tooling, use Kiro CLI instead.
  • Organizations heavily invested in AWS ecosystem — AWS has officially transitioned to Kiro CLI as the canonical product. Choosing the deprecated open-source version may create support and upgrade friction.
  • High-volume team adoption or SLA support — No commercial support or SLA; 1,293 open issues and only critical security fixes signal inadequate engineering resourcing for production deployments.

License & commercial use

Dual-licensed under MIT and Apache 2.0 (both OSI-compliant permissive licenses). Commercial use is explicitly permitted under both licenses; no attribution requirement beyond license inclusion. AWS trademarks (Amazon, Amazon Q) are reserved and may not be used to imply AWS endorsement of derivative products.

MIT and Apache 2.0 are permissive OSI licenses that allow commercial use, modification, and redistribution without royalties or legal approval from AWS. However, AWS trademark restrictions apply: the 'Amazon Q' name and AWS logos cannot be used in derived products in ways that suggest AWS affiliation or endorsement. For production commercial products, verify trademark compliance and consider that AWS has deprecated this project in favor of Kiro CLI, which may create legal or reputational friction.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceStale
DocumentationAdequate
License clarityClear
Deployment complexityLow
DEV.co fitPossible
Assessment confidenceHigh
Security considerations

Project receives only critical security fixes, not regular updates. No formal security audit history is stated. As an agentic LLM tool, it processes and sends user input to external LLM services (AWS Bedrock or similar); data residency, encryption in transit, and LLM provider policies must be validated per your compliance requirements. Rust's memory safety reduces certain classes of vulnerability, but supply-chain risk (dependencies, build toolchain) and LLM prompt injection risks remain. For sensitive or regulated workloads, threat model with respect to data flowing to external LLM services.

Alternatives to consider

Kiro CLI

Official successor, closed-source, actively maintained by AWS with feature development and commercial support. Recommended if you require active maintenance and AWS backing.

GitHub Copilot CLI / Cursor

Closed-source, actively developed, broader IDE/editor integration, and strong adoption. Better for teams prioritizing editor-native experience over terminal-first workflows.

Continue.dev / Open-source agentic CLIs

Permissive open-source alternatives offering similar LLM-driven development patterns. Suitable if you require open-source, community-driven tooling without AWS trademark constraints.

Software development agency

Build on amazon-q-developer-cli with DEV.co software developers

This project is no longer actively maintained. Evaluate the closed-source Kiro CLI for production use, or explore open-source alternatives if you require permissive licensing and community support.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

amazon-q-developer-cli FAQ

Is Amazon Q CLI still maintained?
No. AWS has deprecated this project in favor of closed-source Kiro CLI. Only critical security fixes are planned; no new features or active development.
Can I use this commercially?
Yes, both MIT and Apache 2.0 licenses permit commercial use. However, you cannot use the 'Amazon Q' trademark in ways that imply AWS affiliation. Consider trademark and reputation risk if the project is deprecated.
What platforms are supported?
macOS (DMG, Homebrew), Ubuntu, Debian, and AppImage for Linux. Windows support is not documented in the provided materials; requires review.
How many unresolved issues are there?
1,293 open issues as of the data snapshot. High relative to the project's star count and maintenance status; assess impact on your use case.

Software development & web development with DEV.co

From first prototype to production, DEV.co delivers software development services around tools like amazon-q-developer-cli. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across mcp servers and beyond.

Considering Amazon Q CLI for your team?

This project is no longer actively maintained. Evaluate the closed-source Kiro CLI for production use, or explore open-source alternatives if you require permissive licensing and community support.