[BUG] Windows Terminal - Persistent terminal notifications during bugged/looped session (persists when chat resumed also)
Resolved 💬 4 comments Opened Sep 24, 2025 by spiveym Closed Jan 6, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
After resuming a Claude Code chat session that previously experienced a stuck/looping state (repeatedly returning React Server Components data instead of API results), a persistent notification plays whenever any action is taken in Windows Terminal. The notifications persist even after:
- Clearing Windows Action Center notifications
- No background processes or notification-related processes running
What Should Happen?
There shouldn't be any notifications at all. I have had to manually remove notifications from my Powershell profile because any actions would trigger it.
Error Messages/Logs
N/A
Steps to Reproduce
- Start a Claude Code session and execute commands that trigger API requests (e.g., multiple curl commands)
- Experience a session that gets "stuck" in a loop (in this case, repeatedly getting React SSR data instead of expected API responses)
- Session got stuck in a loop of loading the user prompt, indicating actions were being taken by Claude Code, and repeating over and over.
- Resume the chat session later
- Notice persistent notifications in Windows Terminal on any action performed.
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
1.0.123 (Claude Code)
Platform
Other
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
- The issue started when Claude Code went into the aforementioned loop
- It also specifically happens after resuming the same chat that had experienced looping API responses, even though it's no longer stuck in a loop
- The original loop was caused by curl requests returning React Server Components data instead of JSON API responses
- No error messages or logs are visible
- Sound notifications were successfully disabled via shell profile, but the visual icon persists
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗