Skip to content

Unexpected Credit Usage Caused by Kiro Freezing on “Working” #6860

@gilbertosleited1

Description

@gilbertosleited1

Before opening, please confirm:

Operating System

linux

Kiro Version

0.11.63

Bug Description

Dear team,

I am having a problem with Kiro. I subscribed to the 1,000-credit plan, and that was fine at first. However, those credits were used up in just 8 days. I noticed that sometimes it gets stuck on “Working” and never moves past that. In addition, there are times when it only replies with “understood” and then does nothing.

Even so, this still consumes credits. Since I used 1,000 credits in 8 days, I upgraded my plan, and now another 1,000 credits were consumed in just 2 or 3 days. It also seems that the number of times it gets stuck on “Working” has increased, consuming a considerable amount of credits, along with these “understood” responses that use credits without producing any actual progress.

Steps to Reproduce

Scenario 1 - Kiro gets stuck on “Working” and keeps consuming credits
I open Kiro.
I create or start developing a Spec.
Kiro starts working on the tasks.
It indicates that the process has started.
It shows the files being generated or modified.
Then it gets stuck on “Working”.
It never leaves that state, and if I cancel it, a very large amount of credits is consumed without any actual result.
If I send another message, it starts working again, but it still consumes an excessive amount of credits.
Scenario 2 - Kiro replies “understood” and does nothing
I open Kiro.
I create or start developing a Spec.
Kiro replies with “understood” and does nothing else.
Even so, it consumes 2

Image Image

or more credits just for that.

Expected Behavior

My expectation is that it should respond properly, and if some kind of freeze happens, which is understandable and can occur, it should not consume credits. I lost a considerable amount of credits because of these scenarios.

Conversation ID

d51143cc-2924-445e-87cd-0d4bbdf69037
d51143cc-2924-445e-87cd-0d4bbdf69037
d51143cc-2924-445e-87cd-0d4bbdf69037
d51143cc-2924-445e-87cd-0d4bbdf69037
d51143cc-2924-445e-87cd-0d4bbdf69037

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    duplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions