An unexpected error occurred

[johan12]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

darwin

Kiro Version

0.8.206

Bug Description

Kiro agent returns "An unexpected error occurred, please retry." on any user input

Technical Details:
Primary Error: RangeError: Maximum call stack size exceeded at workbench.desktop.main.js:523.
Secondary Symptom: UI displays: "An unexpected error occurred, please retry."

Steps to Reproduce

write any prompt

Expected Behavior

A useful response

Conversation ID

2203ea8c-fd79-486d-bc0f-d79b05623a23

Additional Context

No response

[johan12]

I tried clearing cache and reinstalling, also tried adding .kiroignore, but doesn't solve the issue. It's only happening on reasonably big project, other project is working fine

[AnilMaktala]

Hi @johan12, thanks for reporting this and for the additional context about project size. A few questions:

• Project structure: Approximately how many files/folders are in this project? Any deeply nested directories?
• Symlinks: Does your project contain any symbolic links that might be circular?
• File types: Any unusually large files (logs, generated files, node_modules, etc.) that aren't gitignored?
• .kiroignore: What patterns did you add?
• Logs: Could you share the kiro logs?

[johan12]

I have confirmed that the issue was caused by a single directory, allure-results/, which contained approximately 166,000 unignored test artifact files.

Action Taken:

1. Removed the allure-results/ directory.
2. Verified project file count.
   Results:

• The project file count has dropped from ~200,739 to 34,912.
• Scanning performance has returned to normal speeds.
  This confirms the scanner was stalling due to the high volume of files in that specific unignored folder. I have added allure-results/ to my .kiroignore to prevent this from recurring.

However, a critical finding:
The allure-results/ directory WAS ALREADY present in my .gitignore (line 44), but Kiro scanned it anyway.

[AnilMaktala]

Hey @johan12, great debugging — thanks for tracking this down and sharing the details. Glad it's resolved.

On the .gitignore vs .kiroignore point-- you're right, Kiro currently uses its own .kiroignore and doesn't automatically pick up .gitignore patterns. I've flagged this with the team that gitignored directories shouldn't be scanned. For now, adding large directories to .kiroignore is the way to go.