70 sources from practitioners, by month and sentiment.
Across the 61 independent public accounts the read is mixed and leans positive: 18 positive, 12 mixed, and 13 negative; 18 state no overall view and cast no vote. Agentic coding draws the most consistent praise, from 15 of the 16 sources that discuss it. Every source discussing answer quality, bugs, or product direction raises a concern. Accounts that compare tools split 6 to 7 on their preferred main tool.
Positive, mixed and negative sources
181213
The score counts them as 16 positive, 11 mixed and 12 negative votes, one per author. See How the numbers work.
Counted for All practitioners, from 70 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
1Agentic Coding15 of 16 sources on it praise itHow well Q Developer carries a task through reading files, editing code, running commands, and checking the result.
Testing Q Developer on the free tier with Claude Sonnet 4.5, Heller saw its first C++ pi program fail to compile until a fix was requested; in the Q CLI it fixed a websocket chat example with a simple three-line addition. Says Q has improved significantly and "I can certainly recommend it to AWS customers".
"Amazon Q Developer has improved significantly over the last year. I can certainly recommend it to AWS customers."
Excerpt, Martin Heller
Published Dec 4, 2025Hands-on review in VS Code and the Q CLI, compared with Codex
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
Used Amazon Q in VS Code to scaffold the HTML, CSS, and JavaScript front end of a side project. It was great for UI and less so for build scripts and cron workflows.
Published Sep 9, 2025self-described: Side project, self-hosted on a Raspberry Pi
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Had Amazon Q drive GitHub through the gh CLI and it worked well, merging when checks passed, though it hallucinated JSON schema details every new session.
Published May 22, 2025
Practitioner account, pseudonymous; direct use; counts toward Reliability
Lets Q Developer work on small, well-defined Python problems for half an hour while doing other work. It runs scripts and fixes errors, but did much worse in a large codebase.
Published Mar 22, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Positive
Pietro Maffi, Engineer building internal Jira reporting apps
Built a Jira reporting app quickly with Amazon Q. Copilot's version failed after 30 minutes of fixes, and one Q prompt repaired it, which the author attributes to Q running Sonnet 4.
Published Aug 26, 2025self-described: Company where Copilot is the approved assistant
Practitioner account, self-described; direct use; counts toward Delivered outcomes
Revisiting Q Developer, Ebert came away with a much more favorable impression than nearly a year earlier; using claude-4-sonnet in the Q CLI, never hit throttling, unlike Claude Code at work. Will "likely" keep Claude Code at work but would strongly consider Q CLI for new side projects for its pricing.
"I'll likely continue using Claude Code at work since this tool already has widespread adoption and support within my organization. However, due to Amazon's relatively inexpensive pricing model, I would strongly consider using Q Developer CLI in any new side projects I pursue in the future."
Excerpt, Chris Ebert
Published Jul 15, 2025self-described: Side project, a browser game built for the AWS Build Games Challenge; uses Claude Code at work
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Says the Q Developer CLI and IDE plugins work as well as the Claude models they wrap, but naming everything Amazon Q confuses the console assistant with the developer tools.
Published Jul 14, 2025
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Has Q write a plan to a markdown file, clears the context, and has it execute the plan phase by phase on Sonnet 4, sometimes comparing against a Codex implementation.
Published Jun 25, 2025
Practitioner account, pseudonymous; direct use; not counted, takes no position
Built a static World Clock app with the Q CLI, deployed it to S3 and CloudFront, updated it live, and deleted the infrastructure, all through prompts, and also lists real limits.
Published Apr 26, 2025
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Employer-approved Q Developer has been good with Python, Kubernetes and CDK or CloudFormation. It builds a Lambda setup from a script and pulls context from other templates in the project.
Published Feb 24, 2025self-described: Employer-approved tooling; Python, Kubernetes, CDK
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
A senior .NET developer on a company-licensed Amazon Q in Visual Studio reports that since "last month" the agent asks permission for every file and folder; one change took more than 500 allow clicks and over 2 hours against 5 minutes by hand. Calls the overall experience "very worst and bad".
Published Jul 17, 2026self-described: Company-provided Q license, .NET Core in Visual Studio 2022 and 2026
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Operational control
Revisiting Q Developer, Ebert came away with a much more favorable impression than nearly a year earlier; using claude-4-sonnet in the Q CLI, never hit throttling, unlike Claude Code at work. Will "likely" keep Claude Code at work but would strongly consider Q CLI for new side projects for its pricing.
"I'll likely continue using Claude Code at work since this tool already has widespread adoption and support within my organization. However, due to Amazon's relatively inexpensive pricing model, I would strongly consider using Q Developer CLI in any new side projects I pursue in the future."
Excerpt, Chris Ebert
Published Jul 15, 2025self-described: Side project, a browser game built for the AWS Build Games Challenge; uses Claude Code at work
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Built a static World Clock app with the Q CLI, deployed it to S3 and CloudFront, updated it live, and deleted the infrastructure, all through prompts, and also lists real limits.
Published Apr 26, 2025
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Testing Q Developer on the free tier with Claude Sonnet 4.5, Heller saw its first C++ pi program fail to compile until a fix was requested; in the Q CLI it fixed a websocket chat example with a simple three-line addition. Says Q has improved significantly and "I can certainly recommend it to AWS customers".
"Amazon Q Developer has improved significantly over the last year. I can certainly recommend it to AWS customers."
Excerpt, Martin Heller
Published Dec 4, 2025Hands-on review in VS Code and the Q CLI, compared with Codex
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
A big fan of the Q CLI for AWS work, Dockerfiles, shell scripts, and prototype projects asks why they should move to Kiro CLI, finding the run of new tools confusing.
Published Nov 19, 2025
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Says the Q CLI injects so much into shell profiles that terminal start-up slows by seconds, and it lacked support for streamable HTTP and SSE MCP servers.
Published Jul 14, 2025self-described: DevOps practitioner, in tech since 2005
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
3AWS Knowledge7 of 10 sources on it praise itThe quality of Q's answers about AWS services, the account's own resources, IAM, and CDK, CloudFormation, or Terraform.
Q's extension and CLI saved hours on AWS infrastructure and IAM, S3, and ECS debugging, but generated IaC needed fixes before CloudFormation accepted it, and its code review works like a linter.
Published Aug 11, 2025
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
For Terraform creating an IAM user, KMS key and encrypted S3 bucket, Q Developer produced clean code with no deprecated parameters and AWS security defaults, where ChatGPT did not.
Published Mar 31, 2025self-described: Terraform for IAM, S3 and KMS
Employer-approved Q Developer has been good with Python, Kubernetes and CDK or CloudFormation. It builds a Lambda setup from a script and pulls context from other templates in the project.
Published Feb 24, 2025self-described: Employer-approved tooling; Python, Kubernetes, CDK
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Built a static World Clock app with the Q CLI, deployed it to S3 and CloudFront, updated it live, and deleted the infrastructure, all through prompts, and also lists real limits.
Published Apr 26, 2025
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Every concern practitioners raise, most raised first.
1Answer QualityAll 10 sources on it raise it as a concernIncorrect or shallow code and answers, including refusals and comparisons with other assistants.
Has a Q rule not to change code without confirming first. Q breaks it often and follows it again only after a reminder, apparently forgetting rules after a restart.
Published May 1, 2026
Practitioner account, pseudonymous; direct use; counts toward Operational control
Testing Q Developer on the free tier with Claude Sonnet 4.5, Heller saw its first C++ pi program fail to compile until a fix was requested; in the Q CLI it fixed a websocket chat example with a simple three-line addition. Says Q has improved significantly and "I can certainly recommend it to AWS customers".
"Amazon Q Developer has improved significantly over the last year. I can certainly recommend it to AWS customers."
Excerpt, Martin Heller
Published Dec 4, 2025Hands-on review in VS Code and the Q CLI, compared with Codex
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
Using the Q CLI on a real CDK TypeScript project, Mahdi Azarboon found it hallucinated, forgot instructions, and broke with updates, yet sped up mundane work when tightly controlled.
Published Oct 12, 2025self-described: AWS CDK TypeScript project
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
A junior engineer writing CDK at an AWS-centric company uses Q Developer with Claude 4 in VS Code for requirements and design documents. Good results take a long time, and the engineer expects to move to Kiro.
Published Jul 30, 2025self-described: Organization that mainly uses AWS; junior engineer writing CDK
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Used Amazon Q in VS Code to scaffold the HTML, CSS, and JavaScript front end of a side project. It was great for UI and less so for build scripts and cron workflows.
Published Sep 9, 2025self-described: Side project, self-hosted on a Raspberry Pi
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Had Amazon Q drive GitHub through the gh CLI and it worked well, merging when checks passed, though it hallucinated JSON schema details every new session.
Published May 22, 2025
Practitioner account, pseudonymous; direct use; counts toward Reliability
Argues renaming AWS Chatbot to Amazon Q Developer muddles a dozen products under one name, and that Q has improved but 'usually' accurate is not enough for alerts.
Published Feb 27, 2025self-described: Own AWS environment with chat alerts for console changes, cost anomalies and health events
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Adoption and upkeep
A senior .NET developer on a company-licensed Amazon Q in Visual Studio reports that since "last month" the agent asks permission for every file and folder; one change took more than 500 allow clicks and over 2 hours against 5 minutes by hand. Calls the overall experience "very worst and bad".
Published Jul 17, 2026self-described: Company-provided Q license, .NET Core in Visual Studio 2022 and 2026
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Operational control
On both Free and Pro, Claude Sonnet 4 kept returning a high-load error for days, so they moved the project to Cursor and are considering switching for good.
Published Jul 22, 2025
Practitioner account, pseudonymous; direct use; counts toward Reliability
Asks whether the Q plugin still crashes PyCharm and whether Amazon Q was asked to check if the plugin "would keep crashing PyCharm until it is uninstalled", adding that the author isn't keen on wasting time on alpha code.
Published Apr 21, 2025
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Says the Q CLI injects so much into shell profiles that terminal start-up slows by seconds, and it lacked support for streamable HTTP and SSE MCP servers.
Published Jul 14, 2025self-described: DevOps practitioner, in tech since 2005
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
A big fan of the Q CLI for AWS work, Dockerfiles, shell scripts, and prototype projects asks why they should move to Kiro CLI, finding the run of new tools confusing.
Published Nov 19, 2025
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
A self-described AWS fan whose organization runs its base infrastructure on AWS says Q Developer was OK early but declined once agentic features arrived and is not competitive with other coding tools.
Published Oct 11, 2025self-described: Organization running its base compute and storage on AWS
Practitioner account, pseudonymous; opinion; not counted until substantiated
Amazon Q was imposed at their workplace in an alpha state and stayed miles behind competitors for a year until the team moved back to Copilot. Now distrusts AWS AI tooling.
Published Jul 14, 2025self-described: Workplace where Amazon Q was mandated, later replaced by Copilot
Practitioner account, pseudonymous; direct use; not counted, takes no position
Says the Q Developer CLI and IDE plugins work as well as the Claude models they wrap, but naming everything Amazon Q confuses the console assistant with the developer tools.
Published Jul 14, 2025
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Argues renaming AWS Chatbot to Amazon Q Developer muddles a dozen products under one name, and that Q has improved but 'usually' accurate is not enough for alerts.
Published Feb 27, 2025self-described: Own AWS environment with chat alerts for console changes, cost anomalies and health events
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Adoption and upkeep
Found Amazon Q in the AWS console useless, worse than a Google search, and expects little from AWS's next coding tool as a result.
Published Jul 14, 2025
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.AWS closed new sign-ups on May 15, 2026 and ends support for the IDE plugins and paid subscriptions on April 30, 2027. Amazon Q in the console, the documentation site, the mobile app, Slack, and Microsoft Teams is not affected. AWS DevOps Blog: Amazon Q Developer end-of-support announcement
Q's extension and CLI saved hours on AWS infrastructure and IAM, S3, and ECS debugging, but generated IaC needed fixes before CloudFormation accepted it, and its code review works like a linter.
Published Aug 11, 2025
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes
Mixed
Stephen A. Fuqua, Director, Software Engineering at Ed-Fi Alliance
Fuqua reports that Q found null-handling edge cases and saved about 20 minutes on C# unit tests, although he had to convert its XUnit output to NUnit. He allows his teams to use coding assistants while retaining mandatory peer review and security checks.
"Overall, I estimate it saved me about 20 minutes time on that task. And it helped find a low probability bug in the system-under-test that I may have missed. That was useful."
Excerpt, Stephen A. Fuqua
"Mandatory peer review and merge process into the protected main branch that generates our binary releases."
Same speaker
Published Jan 14, 2025Director evaluating coding assistants for open source engineering teams
Practitioner account, self-described; direct use; counts toward Delivered outcomes
Using the Q CLI on a real CDK TypeScript project, Mahdi Azarboon found it hallucinated, forgot instructions, and broke with updates, yet sped up mundane work when tightly controlled.
Published Oct 12, 2025self-described: AWS CDK TypeScript project
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability
For Terraform creating an IAM user, KMS key and encrypted S3 bucket, Q Developer produced clean code with no deprecated parameters and AWS security defaults, where ChatGPT did not.
Published Mar 31, 2025self-described: Terraform for IAM, S3 and KMS
Questions the sources split on, with the count on each side.
Evidence remains mixed
Among engineers who used Q Developer and another assistant, which works better as the main tool?
67
Q Developer works better, 6 sources
Some prefer Q for its flat price, Visual Studio support, AWS-correct infrastructure code, or results that beat Copilot, Cline, or ChatGPT on their task. One Amazon engineer ranks Q in IntelliJ above every other tool they have tried.
Another assistant works better, 7 sources
Others moved to Copilot, Cursor, or Claude Code, citing slow inline suggestions, an unavailable model, a product that fell behind, or weaker context on adjacent systems.
Evidence remains mixed
How much should Q Developer complete before a human checkpoint?
52
Broader delegation, 5 sources
Some give Q a goal with checkable criteria and let it run for half an hour or more, and others ask for a setting that runs commands without a click each time.
Tighter steering, 2 sources
Others have Q write a plan to a file and execute it phase by phase, or keep it tightly controlled because it forgets instructions.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 6 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
14 sources. These accounts focus on how Amazon Q Developer works across a team: rollout through IAM Identity Center, rules files, review load, and the AWS work it takes on.
Individual builders
56 sources. These accounts focus on raw capability, AWS knowledge, the flat price, and how Q Developer compares with the assistant each builder already uses.
All practitioners
70 sources. This gives the broadest read, but combines work settings that can reach materially different conclusions.
70 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual practitionerSolo developers and independent builders56 sources, counted here
Emphasizes AWS knowledge, flat price, and how Q compares with other assistants
Very small team2 to 10 engineersNo sources from this setting yet
Professional team11 to 50 engineers, or a named company's team10 sources, counted here
Emphasizes Rules files, reviews, and IAM Identity Center sign-in
Technical leadershipLeaders setting adoption across teams3 sources, counted here
Emphasizes Procurement and data terms through AWS
Organization-wideEnterprise or company-wide rollout1 sources, counted here
Emphasizes Active-user share, budgeting, and risk review
What changes with scale. Individual builders weigh Q Developer's agentic work, the Q CLI, and its AWS knowledge against the quality of its answers. Team and company accounts are fewer and more negative: they turn to sign-in through IAM Identity Center, slow inline suggestions, and whether to keep a tool AWS is retiring.
Where the sources come from
Where this group's sources were published.
Counted for All practitioners, from 70 sources. Change group
84 sources for this group, 14 of them documentation
Developer Communities58, 69% of 84 sources
Product Documentation14, 17% of 84 sources
Engineering Blogs & Reviews11, 13% of 84 sources
Videos & Talks1, 1% of 84 sources
Older evidence is retained when it still applies. Some sources depend on the Q CLI, which is now Kiro CLI, on a changed request limit, or on a model AWS has since replaced. They stay in the history, marked Needs a recheck.
Nov 1, 2026: by the owner's decision, a record whose own words state no overall view of Amazon Q Developer now casts no vote; it still counts toward its topics and is listed, and 18 records that counted leave the vote this way. Leaders and teams stay unscored, individual builders stay at +18 and all practitioners move from +7 to +10.
Oct 31, 2026: rewrote 8 summaries that two blind coders found overstated their sources, so each says what its source says. A comment about another tool's credit states no view of Q Developer and no longer counts, and a Visual Studio developer who calls the experience very bad now reads negative. Individual builders move from +19 to +18 and all practitioners from +9 to +8.
Builds the Amazon Q Developer evidence base from English-language public sources only: every source links to the page it comes from and names its author and publication date.
Shows a finding for a group only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
Leaves out code transformation and code review themes. On October 25, 2026 GILD found first-hand transformation accounts only in AWS-published customer stories and a 2024 test run before general availability. Code review accounts were only first impressions written before general availability. A team planning a Java upgrade with Q should pilot it on one Maven service and count the manual fixes before transformation ends with the IDE plugins' end of support.
Leaves out an agent safety theme, which rests mainly on one researcher's disclosed and fixed vulnerability. The rules-file, self-directed-speed, and AWS-procurement statements fall short of 5 sources from 3 authors; the disagreement about time saved overall lacks 2 sources per side.
Checks every documentation link against AWS's current Amazon Q Developer documentation, pricing, end-of-support notice, and Kiro migration guides.
Counts a GitHub bug report as mixed unless its author drops Q Developer or recommends against it. Four Visual Studio issues (ignored rules, per-file permission prompts, sign-outs, and a failed install) moved from negative to mixed.
Oct 25, 2026: added Needs Close Steering from what existing accounts state. Of these, 1 reports reminding Q of its rules to keep it on task, and 3 describe planning or long unattended runs without concern.
Oct 25, 2026: added five sources from outside the forums: two posts by Mission Cloud's CTO, an engineer's blog, an InfoWorld review, and Gergely Orosz on Q's use inside Amazon. Requires Strong Review now has at least 5 sources from 3 authors.
Lists two Hacker News comments by an Amazon engineer without counting them, because Amazon makes Q Developer. All practitioners move from +23 to +21 and individual builders from +29 to +26.
Method
A running review of what engineering teams report about Amazon Q Developer, from individual builders to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Engineering leaders and teams
Very small team, Professional team, Technical leadership, Organization-wide
Individual builders
Individual practitioner
All practitioners
Everyone in the leaders and teams and individual builders groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among engineering leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. On the AI coding agent hubs, each account's overall stance comes from GILD's blind coding: two models from different families read the source's own words without seeing each other's codes, and a third settled where they differed. An account that states no overall view there, such as a bug report, casts no vote and still counts toward its topics. Other hubs count the stance stored on each record. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +8 mixed (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Under both methods it reads +9 Mixed. No evidence changed.
Correction, Nov 1, 2026. GILD now takes each account's overall stance from its blind two-model coding, and accounts that state no overall view cast no vote. It read +7 Mixed and now reads +10 Mixed.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 2 of 6, individual builders 19 of 37, all practitioners 21 of 43.
Limits
GILD reviewed 70 public sources. The set includes 39 Hacker News comments, 11 r/aws posts, and 7 GitHub issues, which favor problem reports. A GitHub bug report counts as mixed unless its author drops Q Developer or recommends against it. Fourteen sources describe a team or company. Two of them come from engineering directors and one from a CTO, and no finding qualifies for leaders and teams. Nine sources follow the April 30, 2026 announcement: two comments by an Amazon engineer, listed and not counted because Amazon makes Q Developer, and seven GitHub issues. GILD excluded posts for AWS's 2025 game-building T-shirt campaign and posts by AWS employees writing as the vendor. AWS customer stories appear separately as Operator Insights. The counts describe the reviewed sources and cannot estimate the views of all Q users.
Sources record the surface, plan, and model inconsistently. Each source shows what it states. Amazon Q Developer changed substantially in the window. Agentic chat reached every IDE in June 2025, and the Q CLI became Kiro CLI on November 17, 2025. New sign-ups closed on May 15, 2026; the IDE plugins and paid subscriptions reach end of support on April 30, 2027. Sources about the Q CLI, request limits, or a specific model are marked Needs a recheck.
Every count, and the sources behind it
17 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
Limits & Cost. The Free tier includes 50 agentic requests a month across the IDE and CLI. Pro costs US$19 per user per month with higher limits the pricing page does not quantify. Transformation beyond 4,000 lines per user per month, pooled at the payer account, costs US$0.003 per line. Amazon Q Developer pricing, checked Oct 12, 2026
