aws / aws/aws-toolkit-vscode

Amazon Q extenstion not working both in VSCode and Kiro

Open
#8,577 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

## Problem
Amazon Q replies with the below message with no option for clarification or what to do about it:
```
You have reached the limit.

Request ID: d8a9e87f-2cbb-4cc5-8085-c3336cd8bf98
```

Image

And so I went to the Amazon Q extension and clicked _Manage Q Developer Pro Subscription_ from its extension menu, and it gave me this notification:

> To increase your limit, subscribe to a Kiro subscription. Choose the right [plan](https://kiro.dev/pricing/) and log in to [app.kiro.dev](https://app.kiro.dev/signin), pick the plan, and once active, you should be able to continue and use Q and Kiro services with the new limits. If you have questions, refer to our [FAQs](https://aws.amazon.com/q/developer/faqs/?p=qdev&z=subnav&loc=8#general)

Image

[Here is VSCode log file of Amazon Q](https://github.com/user-attachments/files/25326598/Amazon.Q.Logs.log), I took a look at it and saw this portion which could possibly point to a monthly limit:
```json
{"requestId":"d8a9e87f-2cbb-4cc5-8085-c3336cd8bf98","reasonDesc":"You have reached the limit.","credentialStartUrl":"https://view.awsapps.com/start","result":"Succeeded","enabled":true,"languageServerVersion":"1.58.0"}
2026-02-15 16:45:00.646 [info] [Error - 4:45:00 PM] [2026-02-15T13:45:00.644Z] lserver: {
"code": "QModelResponse",
"requestId": "d8a9e87f-2cbb-4cc5-8085-c3336cd8bf98",
"name": "Error",
"message": "You have reached the limit.",
"cause": {
"$fault": "client",
"$metadata": {
"httpStatusCode": 402,
"requestId": "d8a9e87f-2cbb-4cc5-8085-c3336cd8bf98",
"attempts": 1,
"totalRetryDelay": 0
},
"name": "ServiceQuotaExceededException",
"reason": "MONTHLY_REQUEST_COUNT"
}
}
```
So I proceeded to download _Kiro_ and then added _Amazon Q_ extention to it.Then gave the same prompt to Amazon Q, and still Amazon Q gives a reply with:
```
You have reached the limit.

Request ID: 3240deda-f5a7-4399-a9a4-f28e1aad2bfd
```

So I did the same thing I did on _VSCode_ on _Kiro_. I went to the Amazon Q extension menu and clicked _Manage Q Developer Pro Subscription_ and still, the below same message appears, eventhough **_I have Kiro credits_**, you can see from the image I already have _50 Kiro credits_:

> To increase your limit, subscribe to a Kiro subscription. Choose the right [plan](https://kiro.dev/pricing/) and log in to [app.kiro.dev](https://app.kiro.dev/signin), pick the plan, and once active, you should be able to continue and use Q and Kiro services with the new limits. If you have questions, refer to our [FAQs](https://aws.amazon.com/q/developer/faqs/?p=qdev&z=subnav&loc=8#general)

Image

So if it a monthly limit then why is Amazon Q pointing me to _Kiro_? Using Kiro didn't make any difference. And also why is there no way to see **Quotas** and **Limits** regarding Amazon Q anywhere? I checked **_AWS Console_** and doesn't show anything related to that. And why is there no option to _**see the date where the limit gets reset**_?

## Expected behavior
A functional Amazon Q.

## System details

### 1. VSCode
- OS: Windows_NT x64 10.0.19045
- Visual Studio Code extension host: 1.109.3
- Amazon Q: 1.109.0
- node: 22.21.1
- electron: 39.3.0

### 2. Kiro
- OS: Windows_NT x64 10.0.19045
- Visual Studio Code extension host: 1.107.1
- Amazon Q: 1.109.0
- node: 22.21.1
- electron: 39.2.3

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the attached VSCode Amazon Q log, especially the ServiceQuotaExceededException and MONTHLY_REQUEST_COUNT details, then reproduce the behavior in VSCode and Kiro using the listed extension versions. Compare how both hosts handle the limit response and subscription guidance; done means identifying a reproducible extension defect with a clear fix or confirming that the behavior is controlled by the external service.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.