#✅ - Kiro going on loop if I ask it to fix some issues in Spec mode

1 messages · Page 1 of 1 (latest)

little owl
#

I do not have any specific logs to attach to this thread. But this is a pattern that I've noticed multiple times.

  • Usually, a task starts and after completing the task, it fails to fix a type or build error, then it goes on a loop
  • Even if I switch to a new session a just mention about fixing that particular issue it's pretty much the same response. This got me thinking if creating a new session is taking context from previous sessions. Obviously I'm not sure weather this is the case, but this is a pattern I've been noticing over last few days.
marsh dagger
#

Hi @little owl Can you share an example, where you encounter this issue? I'm unable to replicate this issue.

little owl
#

It usually happens after a long task has been completed and then it runs for eg: npm run build to verify, then the code might be failing it tries to fix it, then it goes on a loop. Same loop can be observed even if I copy paste the issue in a new session. But yeah, would be difficult to replicate.

#

The issue gets fixed if I copy paste the same issue to other tools such as claude

#

My hypothesis is it has something to do with context bloating

marsh dagger
raven radishBOT
#

✅ - Kiro going on loop if I ask it to fix some issues in Spec mode

raven radishBOT