Amazon Q Developer, the successor to Amazon CodeWhisperer, is AWS's attempt to fold an AI coding assistant into the places developers already work: their editor, their terminal, and the AWS Management Console. Rather than positioning itself purely as an autocomplete engine, AWS pitches it as an assistant that spans the software development lifecycle, from generating a function to reviewing a diff to migrating a legacy Java application. The most useful way to judge whether it fits your team is to walk through how it actually gets used day to day, then weigh the specifics against the price.
How a Typical Session Plays Out
The tool is designed to sit inside an existing workflow instead of asking you to adopt a new interface. A representative loop looks like this:
- Install the extension in your editor. Amazon Q Developer ships plugins for Visual Studio Code, JetBrains/IntelliJ IDEA, Visual Studio, and Eclipse (in preview). Once authenticated, it begins offering inline suggestions as you type, ranging from short snippets to complete functions.
- Write code with inline chat alongside completions. Beyond passive autocomplete, you can open an inline chat inside the editor to ask questions about the file you are in or request a change in natural language, keeping the conversation in context rather than in a separate window.
- Hand off larger tasks to the agent. For work that spans more than a single suggestion, Q Developer can operate agentically, taking on feature implementation, writing tests, and reviewing code as a multi-step task rather than a single prompt-response exchange.
- Move to the command line when needed. Q Developer works in the terminal, including translating natural-language descriptions into bash commands, which is aimed at the moments when you know what you want to do but not the exact flags.
- Run a security and code review pass. Before merging, you can trigger vulnerability scanning across your codebase; the tool flags issues and proposes remediation rather than only reporting them.
- Use it for migrations and cloud questions. Separately from feature work, the transformation capability handles Java 8-to-17 upgrades and .NET porting from Windows to Linux, and the assistant is also available inside the AWS Console to answer questions about services and configuration.
The through-line is that Q Developer tries to meet you at each stage rather than being a single-purpose completion tool, and its integrations into GitHub (preview), GitLab, Slack, and Microsoft Teams extend that reach beyond the editor itself.
What the Tool Actually Does
Several capabilities are worth understanding in terms of when they matter, not just that they exist.
Inline suggestions and editor chat
The core experience is real-time code suggestions in the editor. This is the feature you interact with most, and its value depends heavily on how conventional your codebase is. For common patterns and well-trodden libraries it reduces keystrokes meaningfully; for domain-specific logic you will accept fewer suggestions. The inline chat is the more interesting addition, because it lets you ask "why does this fail" or "rewrite this to use async" without leaving the file.
Agentic task execution
The agent is the part AWS leans on hardest, and it is backed by a concrete claim: Q Developer reports top scores on the SWE-Bench Leaderboard and Leaderboard Lite, benchmarks that measure resolving real GitHub issues. Benchmarks are not production, but they are a reasonable proxy for how well an agent can carry a multi-step task end to end. In practice this is where you would delegate a scoped feature or a batch of test-writing and then review the result, rather than trusting it unsupervised.
Security scanning and code review
Vulnerability scanning with automated remediation suggestions is bundled in rather than sold as a separate product. AWS states it outperforms leading publicly benchmarkable tools on detection across most popular languages. For teams that do not already run a dedicated SAST tool, having detection and suggested fixes inside the same assistant lowers the friction of catching issues before merge.
Code transformation
This is the feature most specific to Q Developer's target audience. It automates Java 8 to Java 17 upgrades and ports .NET applications from Windows to Linux, framing both as work the assistant can drive rather than a fully manual slog. If you are carrying a portfolio of aging enterprise Java services, this is a distinct reason to look at the tool that its competitors do not all offer.
Customization and CLI translation
You can connect private repositories so recommendations reflect your own codebase conventions rather than generic public code, and the natural-language-to-bash translation in the CLI is a small but frequently useful convenience.
Where It Fits Best
The strongest case for Amazon Q Developer is a team already committed to AWS. The assistant lives inside the AWS Console, can answer architecture and service-selection questions in that context, and pairs naturally with cloud-native and infrastructure work. If your organization also maintains legacy Java or Windows .NET workloads, the transformation features turn what is normally a manual, error-prone migration into a partially automated one.
DevOps and platform engineers benefit from the CLI integration and console assistance, while application developers get the editor completions and agent. Teams that want AI code help but have no meaningful AWS footprint will find the AWS-specific advantages irrelevant, and should evaluate it purely on the quality of its editor experience against general-purpose alternatives. You can compare options in the AI code generator category before committing.
What It Costs
Pricing is genuinely approachable, which lowers the barrier to trying it. The Free tier is perpetual, not a trial.
| Plan | Price | Notable limits |
|---|---|---|
| Free | $0 | 50 agentic requests/month; 1,000 lines of code transformation/month |
| Pro | $19/user/month | Increased agentic request limits; 4,000 lines of transformation/month per user (pooled at account level); Identity Center support with admin dashboards; IP indemnity; access to the latest Claude models in the IDE or CLI |
The overage rate for transformation beyond the monthly allocation is $0.003 per line of code. Two Pro details carry real weight for organizations: IP indemnity, which matters to legal teams worried about the provenance of generated code, and admin dashboards through AWS Identity Center, which are the difference between an individual tool and something you can govern across a team. The inclusion of the latest Claude models on Pro is also notable, since it signals the assistant is not limited to a single in-house model.
The Tradeoffs to Weigh
The clearest limitation is orientation: much of what makes Q Developer distinctive, the console integration, service-selection help, and cloud tooling, is only valuable if you use AWS. Outside that ecosystem the tool competes on editor completions and agent quality alone, where the field is crowded. Several capabilities that AWS highlights, including Eclipse support and the GitHub integration, are still in preview, so their reliability is not yet the same as the generally available features. The benchmark claims, while specific and cited, are leaderboard results rather than guarantees about your particular codebase; conventional code will see more benefit than niche or heavily domain-specific work. Finally, the free tier's 50 monthly agentic requests are enough to evaluate the agent but will constrain anyone who wants to rely on it daily, effectively steering serious users toward the Pro plan.
Overall Assessment
Amazon Q Developer is a coherent, well-integrated assistant that is easiest to recommend to teams building on AWS, and specifically compelling for anyone facing Java or .NET modernization work. The perpetual free tier makes it low-risk to trial, and at $19 per user per month the Pro plan is priced in line with peers while adding governance and indemnity features that matter at organizational scale. The parts to scrutinize before adopting are the preview-stage integrations and how much of the AWS-specific value actually applies to your stack. If you are AWS-native, it is a straightforward candidate; if you are not, judge it on the editor and agent experience like any other assistant. Browse more AI tools or read practical comparisons on the blog to weigh it against the field.
Common Questions
Is Amazon Q Developer the same as CodeWhisperer?
Amazon Q Developer is the successor to Amazon CodeWhisperer. It carries forward the AI coding assistance role and expands it with agentic task execution, security scanning, and code transformation.
Does it have a free plan?
Yes. The Free tier is perpetual and includes 50 agentic requests per month and 1,000 lines of code transformation per month at no cost.
How much does the Pro tier cost and what does it add?
Pro is $19 per user per month. It raises agentic request limits, increases transformation capacity to 4,000 lines per month per user (pooled at the account level), and adds Identity Center support with admin dashboards, IP indemnity, and access to the latest Claude models in the IDE or CLI.
Which editors and platforms does it support?
It offers plugins for Visual Studio Code, JetBrains/IntelliJ IDEA, Visual Studio, and Eclipse (preview), plus the command line, the AWS Management Console, GitHub (preview), GitLab, Microsoft Teams, and Slack.
Can it help migrate legacy applications?
Yes. Its code transformation feature automates Java 8 to Java 17 upgrades and ports .NET applications from Windows to Linux, turning a normally manual migration into a partially automated one.
