Repository navigation
Kiro account credit limits in Usage #27111
Replies: 2 comments 1 reply
|
I reproduced this on macOS with Kiro CLI 2.37.1 and a paid account. The unadvertised V3 method works here too. Verification:
I also tested a local implementation showing monthly plan credits and reset information in Usage → Limits, and confirmed the result in the web app. Focused tests cover parsing, fallback selection, authentication failures and timeouts; affected-package typechecks, lint and formatting pass. Mobile was typechecked, not device-tested. Before/after screenshots are available. My initial implementation used V2 when V3 did not advertise this method. Your draft prompted the direct test above, which demonstrates that absence from the advertisement does not establish that the method is unsupported. The explicit V2 usage command is also verified as a compatibility path; V3 headless chat Would maintainers prefer a V2 fallback only when the direct V3 request explicitly reports an unsupported method, or keep this V3-only? Happy to coordinate on the existing implementation and contribute compatibility tests. No competing upstream PR has been opened. |
|
Note 🤖 Claude Opus 5.5 responding on behalf of @Nichokas
How I checked:
The response has the same shape as the 2.35.2 fixture in MrFruitDude/t3code#1: There is one difference the draft doesn't cover. This account has a non-empty { "name": "Trial credits", "used": 0, "total": 500, "daysUntilExpiry": 364 }The draft's fixture has I'd use this in T3 Code daily. Right now Usage → Limits shows "No provider on the selected environments reports subscription limits" for Kiro. |

Uh oh!
There was an error while loading. Please reload this page.
Would you accept live Kiro account credit limits alongside the native Kiro provider in #14693?
We have a tested implementation showing remaining credits, overage status and billing reset in Usage → Limits and
/usage-limits, separate from context usage and historical credit consumption. It builds on #14693 and reads account usage without opening a Kiro session.Implementation draft: MrFruitDude#1
The main tradeoff is that
_kiro/account/getUsageis not advertised in Kiro's ACP extension list. We verified it against CLI 2.33.1, 2.34.2, 2.35.0 and 2.35.2; unsupported and failed reads are handled explicitly. Focused tests, typechecks and a live account probe pass.Happy to open a focused upstream PR if this direction and scope fit.
All reactions