## Crash #18 — April 11, 2026 — Kiro IDE Grey Screen Crash

[lanafrances]

Before opening, please confirm:

• I have searched for duplicate or closed issues

Operating System

win32

Kiro Version

0.11.131

Bug Description

Time: April 11, 2026, during holosuite dark mode text fix / settings parity work

• Trigger: Kiro IDE grey screen crash mid-conversation
• Context: User had just confirmed the accessibility widget fix worked and the settings page was now showing correctly on holosuite. Was about to work on dark mode text readability issue when the grey screen appeared.
• What Was Completed Before Crash: Accessibility widget double-toggle fix (public/js/accessibility-widget.js), storage symlink fix on holosuite server, settings page files confirmed for upload
• What Was In Progress: About to fix dark mode text contrast on holosuiteindustries.com
• Data Lost: Conversation context
• Root Cause: Unknown — standard grey screen crash pattern
• Impact: Moderate — no code loss, conversation context lost
• Platform: Windows / Kiro IDE
• Severity: HIGH — Ongoing pattern of grey screen crashes
• Status: Recovered — continuing dark mode fix in new session

Steps to Reproduce

Time: April 11, 2026, during holosuite dark mode text fix / settings parity work

• Trigger: Kiro IDE grey screen crash mid-conversation
• Context: User had just confirmed the accessibility widget fix worked and the settings page was now showing correctly on holosuite. Was about to work on dark mode text readability issue when the grey screen appeared.
• What Was Completed Before Crash: Accessibility widget double-toggle fix (public/js/accessibility-widget.js), storage symlink fix on holosuite server, settings page files confirmed for upload
• What Was In Progress: About to fix dark mode text contrast on holosuiteindustries.com
• Data Lost: Conversation context
• Root Cause: Unknown — standard grey screen crash pattern
• Impact: Moderate — no code loss, conversation context lost
• Platform: Windows / Kiro IDE
• Severity: HIGH — Ongoing pattern of grey screen crashes
• Status: Recovered — continuing dark mode fix in new session

Expected Behavior

Time: April 11, 2026, during holosuite dark mode text fix / settings parity work

• Trigger: Kiro IDE grey screen crash mid-conversation
• Context: User had just confirmed the accessibility widget fix worked and the settings page was now showing correctly on holosuite. Was about to work on dark mode text readability issue when the grey screen appeared.
• What Was Completed Before Crash: Accessibility widget double-toggle fix (public/js/accessibility-widget.js), storage symlink fix on holosuite server, settings page files confirmed for upload
• What Was In Progress: About to fix dark mode text contrast on holosuiteindustries.com
• Data Lost: Conversation context
• Root Cause: Unknown — standard grey screen crash pattern
• Impact: Moderate — no code loss, conversation context lost
• Platform: Windows / Kiro IDE
• Severity: HIGH — Ongoing pattern of grey screen crashes
• Status: Recovered — continuing dark mode fix in new session

Conversation ID

f107c269-c097-4ba9-852d-a0fb650d8f40
f107c269-c097-4ba9-852d-a0fb650d8f40
f107c269-c097-4ba9-852d-a0fb650d8f40
f107c269-c097-4ba9-852d-a0fb650d8f40
f107c269-c097-4ba9-852d-a0fb650d8f40

Additional Context

No response

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #4865: Can't Chat With Kiro - the chat session area goes grey every 5 mins (95% similar)
• #6395: kiro stopped working or responding (85% similar)
• #5936: crash on pattern search (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ If this is not a duplicate, you can prevent automatic closure by adding a comment or reacting with 👎 to this message.
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both report the same grey screen crash issue in Kiro IDE - issue #4865 describes 'chat session area goes grey every 5 mins' which matches the 'grey screen crash' pattern described in the new issue

[csvan]

Are you aware that your reports are leaking project internals and details, or do you simply not care at this point?

[github-actions]

Thank you for your feedback! 🙏

The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.