aws / aws/aws-toolkit-vscode

Cannot reset Amazon Q monthly limit with Kiro credits

Open
#8,513 1 comment 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

Once the monthly limit of Amazon Q is reached, one cannot reset it.

## Steps to reproduce the issue

1. Click on "Subscribe to Q Developer Pro" button in the alert panel "Monthly request limit reached".
2. A notification is displayed sayin "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)"
3. Once logged in Kiro I have an estimated usage of 0/50 credits (free plan), plus a bonus of "223.02 / 500 used (26 days left)".
4. Then I signed out from extension and resigned in again, got redirected to the consent screen for Kiro usage in AWS IDE Extensions.
5. Accepted it and back to vs code I still can't use the chat, keeps telling me "Monthly request limit reached"...

## Expected behavior

## System details (run `AWS: About` and/or `Amazon Q: About`)

- OS: windows 11
- Visual Studio Code version: 1.108.1
- AWS Toolkit version: NOT INSTALLED
- Amazon Q version: 1.107.0

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the listed flow in VS Code 1.108.1 with Amazon Q 1.107.0: reach the monthly request limit, activate Kiro credits, sign out, sign back in, and accept the consent screen. The expected behavior is blank, so first clarify whether Kiro activation should reset or grant access to Q, then verify the monthly-limit message changes appropriately.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript, vscode
Domain
authentication, cloud, 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.