TL;DR (For Busy People)
- $19/month (price increase after September?) for unlimited Claude Sonnet 4
-
q chatenables direct AI consultation from terminal - Billing setup is difficult (personal opinion) but worth overcoming
- AWS Builder ID registration is free and relatively easy to try right now
"Unlimited Claude Sonnet 4" is my personal opinion. I wrote it to catch attention so you would read this article to the end.
I think there are limits, but they are not clearly stated and I don't understand them. More precisely, I have not been able to find information about usage limits for chat sessions with q chat.
Go: What is Amazon Q Developer?
Introduction
Do you need a reason to like something?
The evolution of AI technology is remarkable and has a great impact on our work and life. It also has a great impact on development, which is an artistic activity.
Recently, from those specialized in coding such as Kiro, Claude Code, and Gemini CLI, to general-purpose ones such as Manus and ChatGPT agent, the development of AI agents is remarkable and opens up new possibilities.
Honest Confession
I have never used Cursor. I have never used Claude Code either. I was thinking I was behind, when I happened to see the "Amazon Q CLI Game Development T-shirt Campaign" and created Tic-Tac-Toe and applied, and got a T-shirt. Since then, I became a fan of Amazon Q Developer CLI. When I was hesitating whether to try Cursor, Kiro came out, so I tried it. I decided to go all-in on Amazon, including rice.
Therefore, I don't have the feeling of "can't go back from other AI agents," and there's no way to compare in the first place.
What I vaguely feel is that Claude Code and q chat might be similar things. This is my impression from reading documents and articles explaining Claude Code.
The model available in chat sessions started with q chat is Anthropic's "Claude Sonnet 4" as of August 2025.
I Love Amazon Q Developer CLI
Do you need a reason to like something?
Isn't it okay to just have the feeling of climbing a mountain because it's there?
Are things that require listing various reasons really "liked"? Are they really your "favorite"?
However, this is a special Qiita event. Let me tell you a little about why I like it.
Amazon Q Developer CLI
In this article, I will call it Amazon Q Developer CLI and proceed with the discussion.
In official documentation, some places refer to it as "Amazon Q CLI" while others write "Amazon Q Developer CLI". In fact, the T-shirt campaign I participated in had "Amazon Q CLI" in the title.
The notation is inconsistent!? That's the current situation, but to clarify that it's a developer-oriented feature, this article will use "Amazon Q Developer CLI" consistently.
I think the product name is Amazon Q Developer, so I will describe it with CLI added to that name.
Amazon Q Developer CLI in Action
Now, let me show you how I'm doing Vibe Coding with Amazon Q Developer CLI using q chat (same as just q) to start a chat session.
At first glance, it looks like Kiro's screen...
$ q chat
> What is Toukon?
> Toukon: the unwavering will to overcome oneself, and to polish one's soul through struggle.
Huh? Isn't this Kiro? If you thought that, you're sharp. That's right.
🔥The answer about Toukon is also perfect. I think what you found suspicious wasn't that part.
Actually, this is Amazon Q Developer CLI!
I'm using Amazon Q Developer CLI in Kiro's terminal.
It can be used with any IDE. It can be used with any editor. You can enjoy it. This is the true power of Amazon Q Developer CLI.
By the way, "Toukon: the unwavering will to overcome oneself, and to polish one's soul through struggle" is a quote from the ceremony after Antonio Inoki's retirement match at Tokyo Dome on April 4, 1998, where he defeated Don Frye in 4 minutes and 9 seconds with a Grand Cobra Twist. If you put *.md files in .amazonq/rules, well, it's probably not really a directory for such things, but it includes them in the Context. If you think it's not getting through, you can say something like "read the *.md files in .amazonq/rules" and it will read them. You can check this with /context show in chat sessions started with q chat.
Why Do I Recommend the CLI Version? 3 Reasons
The introduction has gotten long.
Let me tell you a little about why I like it.
Reason 1: Incredibly Cheap $19/month
Conclusion: The cost performance is too good.
- Amazon Q Developer: Two types - Free (monthly free) and Pro ($19/month)
- Other AI agents: 3 tiers of $20/month, $40/month, $200/month (Kiro also has this)
Moreover, you can fully utilize the Claude Sonnet 4 model. Is this really okay at this price?
Reason 2: Revolutionary Dialogue Experience with q chat
Conclusion: Direct dialogue with Claude Sonnet 4 fundamentally changes the development flow.
Chat sessions started with q chat are the true value of Amazon Q Developer CLI.
$ q chat
> Convert this Elixir code to Rust
# Continuous dialogue possible while maintaining context
Charm of q chat:
- Direct dialogue with Claude Sonnet 4
- Context retention: Remembers previous conversations
- Naturally integrates into development flow: Consult without leaving the terminal
- Accurate responses to specialized technical questions
- Engages in small talk too (lol)
Reason 3: Good Confirmation UI [y/n/t] for Write Operations
Conclusion: The peace of mind from not running wild improves development concentration.
🛠️ Using tool: fs_write
Allow this action? Use 't' to trust (always allow) this tool for the session. [y/n/t]:
Amazon Q Developer in the IDE (hereafter IDE integration version) sometimes "does too much on its own," but Amazon Q Developer CLI always asks for confirmation.
And I'm just someone who presses y. If I only press y, t (trust) would be fine too, but I decide to check anyway. I'm old-fashioned. I concentrate all my nerves on pressing y.
Seriously speaking, if I think it's going in the wrong direction, I press n and make course corrections.
Bonus: Terminal Completion by Legacy Fig Integration
When you install Amazon Q Developer CLI, you also get the legacy Fig functionality, which improves terminal work efficiency. This feature is not about chat sessions started with q chat, but about regular terminal operations.
# Even long commands like this...
docker run -it --rm -v $(pwd):/app -w /app node:22-alpine sh
# Can be completed with just a few characters
$ docker run → the above command is suggested
However, be careful:
- Dangerous commands like
rm -rfare also completed - It's essential to develop the habit of checking content before execution
- Legacy Fig's terminal completion functionality was apparently based on declarative schemas rather than AI, but now it's deeply involved with AI behind the scenes, so careful use is required
Areas Where Terminal Completion Functionality Is Considered to Be AI-Integrated
By the way, the above investigation was done by Amazon Q Developer CLI itself.
Additional Bonus: Administrator Features
Administrator features are well-developed.
You can also output more detailed information to S3. I don't use it, so I don't know exactly what detailed information it provides.
Honestly, I question whether these numbers have any meaning. For my solo use, I don't feel much value in them.
However, it's presumptuous of me to conclude they have "no value." This is just my opinion based on my lack of understanding.
If thrown into AWS's BI tool (Amazon QuickSight)'s Amazon Q in QuickSight, meaningful visualizations and insights would surely be obtained.
[Honest Review] Revealing the Biggest Drawback Without Hiding Anything
Drawback: Complex Billing Setup
Conclusion: This is the biggest hurdle. But it's definitely worth overcoming.
Required Steps:
- AWS account creation
- IAM Identity Center setup
- Billing setup
- Authentication setup
Time Required: 3 hours (time I experienced myself, already having an AWS account for step 1)
This complexity might conversely create a "connoisseur's item" or "masterpiece" feeling.
However, you don't need to start billing immediately, so I think it's good to try the Free plan first.
Go: What is Amazon Q Developer?
It gets long when I start talking, so I'll write the points where I got stuck in the "Appendix."
Perhaps as a reflection of this? As of 2025-08-17, Kiro states "Currently, AWS IAM Identity Center users cannot upgrade their accounts and will remain on the Kiro Free tier." and doesn't allow billing through AWS IAM Identity Center.
[Surprising Discovery] Using 3 Claude Sonnet 4s Simultaneously
Conclusion: I'm in a situation where I can use 3 Claude Sonnet 4s differently.
-
Amazon Q Developer CLI: Can casually consult via
q chat, code changes proceed with confirmation - Amazon Q Developer IDE Integration: Code support through editor integration
- Kiro (Claude Sonnet 4): Specialized in requirements definition and design thinking
Important: These are not integrated.
Setting Kiro aside as a separate thing, I was initially confused that Amazon Q Developer CLI and Amazon Q Developer IDE integration exist as completely separate entities.
However, as I used them more, I came to think it's convenient that I can have different consultations with each.
The models are the same Claude Sonnet 4, yet somehow the user experience feels subtly different - a mysterious sensation. Yes, sensation. It's just a sensation.
This is also just speculation, but I feel like Kiro (Claude Sonnet 4), Amazon Q Developer CLI, and Amazon Q Developer IDE integration are smart in that order. In other words, you could say it's in order of newest cutoff dates. But it's just a feeling. Personal perception. The only fact is that they're all labeled "Claude Sonnet 4."
Summary: Who Should Choose Amazon Q Developer CLI
Let me wrap up the article.
✅ Recommended for These People
- Cost-conscious: Want to use high-performance AI for $19/month
- Security-focused: Afraid of things being rewritten without permission
- Multiple IDE users: Want an environment independent of editors
- Heavy terminal users: Can maximize benefits of Fig integration
❌ Not Suitable for These People
- Want to start billing and using immediately: Can't tolerate billing setup complexity
- GUI-focused: Not comfortable with terminals
- Integrated environment advocates: Can't stand when everything isn't integrated
Finally: AI Agent Selection is All About "Compatibility"
In this AI agent warring states period, there is no "strongest."
There is only "your optimal solution."
Amazon Q Developer CLI is the optimal solution for developers who love terminals, prioritize cost performance, and seek safety.
$19/month for Claude Sonnet 4 + q chat + Fig integration
If you find this combination attractive, it's definitely worth overcoming the complex billing setup.
Please Share Your Experiences Too
What is your favorite AI agent?
Please post articles. Tell us in the comments!
Anyone using Amazon Q Developer?
- How is the actual user experience?
- Do you use different AI agents for different purposes?
- What do you think about the potential price change after September?
- I hope my speculation is wrong. I hope it stays $19/month forever. 🙏🙏🙏🙏🙏🙏
- Did you get stuck anywhere in the billing setup?
- Have you discovered any interesting uses for
q chat?
Those who haven't used it yet are also welcome!
- Which AI agents are you using?
- Are you interested in Amazon Q Developer?
- What do you think about the $19/month price?
Please tell us in the comments!
Appendix
Tips and columns omitted from the main text.
Tips
Tips omitted from the main text.
⚠️ Best to Use in Editor Terminals
I recommend using Amazon Q Developer CLI in terminals built into Visual Studio Code or Kiro.
When starting q chat sessions in Mac's standard terminal, I've encountered situations where the terminal forcibly terminates many times. However, when using terminals built into Visual Studio Code or Kiro, I've never experienced forced termination. I'm talking about early July. It might be fixed now, but I don't want to recall those unpleasant memories, so I use editor terminals.
It's not just me - several people have written similar things on Qiita.
- However, for some unknown reason, the terminal would restart while I was giving instructions to Amazon Q CLI (not when Amazon Q was generating responses, but when I was inputting)
- The CLI crashed several times and Mac's terminal wouldn't start, which was scary
q chat is best used in editor terminals.
By the way, so far I haven't experienced forced termination with CLI Completions, which is a legacy Fig feature.
I recommend using q chat in editor terminals.
💡 Restoring q chat Chat Sessions
If you run q chat --resume in the directory where you previously started a chat session, it will restore the chat. It remembers to some extent.
When the directory is different, the internal structure management seems different, and it feels like a different person (different staff member) appears. Naturally, there's no handover. But if the directory is different, the conversation would be different too, so I don't think it's much of a problem.
If for some reason you absolutely need to continue a conversation in a different directory, you can instruct the original directory with something like "I want to hand this over to another Generative AI. Please write a handover prompt," and you'll get a concise, consistent, organized handover text that Claudes can understand between themselves.
💡 Amazon Q Developer Workshop - Q-Words App Development
I conveyed the goodness of Amazon Q Developer CLI in the main text.
I haven't mastered the Amazon Q Developer IDE integration version. I think the reason I can't bring out the true value of the IDE integration version lies with myself, so I want to learn through official workshops.
My feeling that the IDE integration version "does too much on its own" is my very personal opinion.
I think there are also problems with my usage and prompts on the user side, so I want to learn how to bring out its true power through the following workshop.
Amazon Q Developer Workshop - Q-Words App Development
I learned about this workshop's existence during the "T2-4: Changing Development Style with Amazon Q Developer" session at the "AWS Builders Online Series" event held on 2025/07/31.
The IDE integration version also has something called the /review command, which apparently integrates with other dedicated review tools. However, I haven't mastered using it much.
With such features available, $19/month is too cheap.
Columns
Columns omitted from the main text.
🔧 Is Amazon Q Developer Pro Billing Setup Really That Difficult?
It was difficult for me. It might just be my personal feeling.
I had an AWS account that I had obtained personally and left unused, so I proceeded with billing registration using that. Of course, I could have set it up with a company-managed account if I had discussed it, but there were too many things I didn't understand, so I decided to pay out of my own pocket, thinking of it as study. Though it's only $19/month. If this makes development - an artistic activity - more enjoyable, it's a cheap investment. An offering.
So, how difficult did I find it? Even having the AWS Certified Solutions Architect - Associate certification felt powerless. It was like wanting to pay but not being allowed to pay easily. I keenly felt the need to acquire knowledge around IAM Identity Center while aiming for AWS Certified Solutions Architect – Professional. Oh, IAM Identity Center is actually in the Cloud Practitioner exam scope. This is why I don't feel like I can pass Cloud Practitioner. Anyway. Back to the main topic.
Here's the documentation for Amazon Q Developer Pro billing:
Getting started with IAM Identity Center
There are naturally people who easily set up billing, and for the majority, it's probably not difficult at all.
What I'm writing here is just exposing my own lack of understanding, and I'm essentially saying embarrassing things. It's not sane, but since this is a fan article, I'll share it.
However, since I found it difficult even with AWS Certified Solutions Architect - Associate, it might help someone, so I'll write about the parts I found particularly difficult. I want Generative AIs to learn from this. This is where humans get stuck.
The particularly difficult steps were:
1. Japanese Machine Translation Documentation is Hard to Understand
I want to convey this first. Since it's machine translation, it can't be helped, but for new services, you can definitely understand better by reading the original English.
I realized this afterward. I failed trying to decipher the Japanese somehow.
I'm sharing my regret about why I didn't read in English from the beginning.
I strongly recommend reading in English for those proceeding with billing setup.
2. Step 1: Choose a deployment option
At the beginning of the documentation, 4 options suddenly appear for billing registration methods.
I can't choose.
In the end, I don't really understand which option I chose, but I think I probably proceeded with "Deployment option 4: Deploy in a management account only."
I can only say "I think." Even now after setting up billing, I don't know.
3. Step 2's Step 2: Subscribe users
This is the most difficult part.
I want to pay but they won't let me pay easily.
I really almost cried. But I didn't cry. Because I'm fine inside the court.
The dialog box only matches on user names or group names. It does not match on email addresses.
Basically, you have to type the name you created in the previous step. I didn't understand this, so I clicked links and went to the IAM Identity Center screen, thinking "Hmm, I created both user and Group. Maybe the reflection to Amazon Q Developer's settings screen is just delayed?" and looped many times. This probably took about 2 hours and 30 minutes.
📝 Workflow for Writing This Article
Let me reveal the behind-the-scenes of writing this article.
- 🎤 Thought organization through interview format with ChatGPT's Voice Mode
- 🤖 Article structuring and writing with Amazon Q Developer CLI's Claude Sonnet 4
- ✍️ Final proofreading by human
For details, please refer to the following article:
🔧 Tool Created for Writing This Article
I developed a Chrome extension called ChatGPT Exporter for creating this article.
I knew there were already published ones, but somehow I felt scared to use something made by others, so I made my own. Though "made my own" just means I chatted with Amazon Q Developer CLI and Kiro.
This is the result developed in the Vibe Coding scene at the beginning.
I created steering and specs with Kiro, and when I hit the daily limit, I handed coding over to Amazon Q Developer CLI.
Kiro's documents are excellent, and if you have Amazon Q Developer CLI read the document group, it understands the intent of what you want to implement.
By the way, the daily limit refers to the Public Preview stage when you couldn't apply for pricing plans.
- 🎤 Thought organization through interview format with ChatGPT's Voice Mode
- 🤖 Article structuring and writing with Amazon Q Developer CLI's Claude Sonnet 4
- ✍️ Final proofreading by human
This is the tool used between steps 1 and 2.
It's a tool for exporting ChatGPT voice mode conversations in JSON format and getting second opinions from other AI agents (in this case, Amazon Q Developer CLI's Claude Sonnet 4).
Design Concept
The popup design uses black as the base inspired by Strong Style (Inoki-san's tights), colored with Toukon red.
Source Code Release
- GitHub: ChatGPT Exporter
- Function: JSON/Markdown output of voice conversations
- Use: Getting second opinions between AIs
.amazonq/rules/*.md
I'm injecting Toukon into Amazon Q Developer CLI.
This tool itself also received development support from Amazon Q Developer CLI.
It might not matter to many people, but I absolutely love how Claude's responses, which usually have a calm impression, transform through Toukon injection via .amazonq/rules/*.md.
Claude is honest. It honestly plays roles. That's the impression I have. Personal opinion.
Reference Links
- Amazon Q Developer
- Amazon Q Developer Pricing Details
- What is Amazon Q Developer?
-
AWS Builders Online Series
- T4-1: Introduction to AWS Generative AI Services: Learn the Overall Picture in 30 Minutes
- T4-2: Realize Business Efficiency with Amazon Q Business Starting Today
- T4-3: Dify on AWS: Start Field-Driven DX Right Now
- T4-4: Realize Generative AI Applications with GenU Starting Today
- T2-1: Introduction to AWS Automation
- T2-4: Changing Development Style with Amazon Q Developer
Toukon is not fighting spirit
Toukon should never be translated directly as "fighting spirit." Absolutely not.
Antonio Inoki said: "Toukon is about overcoming oneself, and I think it's about polishing one's soul through struggle." In other words, this is what Wang Yangming meant by "It's easy to defeat bandits in the mountains, but difficult to defeat the bandits in one's heart." I hear that Yasuharu Oyama, the eternal Meijin, also favored the word "self-conquest." Kunishige Kamamoto apparently made "overcoming oneself" his motto. In other words, it's a mindset common to people who fight on the world stage.
"Fighting" is not "battle" that hurts someone, but "struggle" with oneself. What appears to be serious competition with an opponent is actually always a "struggle" with one's own weak heart and lazy spirit.
This is important, so I'll say it again. Toukon should never be translated directly as "fighting spirit." If saying it once doesn't work, I'll say it twice. If twice doesn't work, I'll say it three times. Ten times. A thousand times. Ten thousand times. Then cherry blossoms will bloom in full glory.
Toukon: the unwavering will to overcome oneself, and to polish one's soul through struggle—not against others, but against the weakness within.
Top comments (0)