[BUG] Windows Desktop App freezes after daily token limit — input locked, banner persists after reset

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?

Every time the daily usage limit is reached, the Windows Desktop App enters a broken state that does not recover after the limit resets. This happens consistently — not a one-time occurrence.
What Should Happen?
After the limit resets, the app should return to a fully functional state automatically.

What Should Happen?

Restart the session normally when time is up

Error Messages/Logs

"Usage limit reached" banner persists even after the limit resets
Chat input in Projects is completely unresponsive (cannot type, delete characters, or press Enter)
Code tab behaves erratically
Error shown: Turn failed — API Error: Prompt is too long
Restarting the app does not resolve the issue
Only workaround found: creating a new conversation thread within the project

Steps to Reproduce

Use the Claude Windows Desktop App within a Project
Reach the daily usage limit
Wait for the limit to reset
Observe that the "Usage limit reached" banner remains
Attempt to type in the chat input — no input is accepted
Restart the app with the latest version, cache, etc — issue persists

Claude Model

Not sure / Multiple models

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Version 1.3109.0 (35cbf6)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Environment:

App version: (Version 1.3109.0 (35cbf6))
Windows version: (Windows 11 Pro 25H2)
Feature affected: Projects chat + Code tab

Troubleshooting attempted (no resolution):

Fully closed and restarted the app (including system tray)
Cleared app cache (%APPDATA%\Claude\Cache)
Created a new conversation thread within the affected Project — input works there, confirming the issue is tied to the conversation state after a limit event, not the app globally

Affected conversation:

Project name: Fabric Datalake Project from scratch v2,
Conversation title/name: (nombre del hilo afectado)
Approximate date/time when limit was hit: (ej. April 18, 2026, ~afternoon EST)

Additional context:

This appears to be a state management issue — the app does not reset its UI state after a token limit event. The Prompt is too long API error suggests the conversation context is not being cleared either.