[BUG] Claude Desktop app - chat area renders blank on load, Ctrl+R required to display messages

[rosopwnd]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

When opening any chat in the Claude Desktop app (Windows), the conversation area loads blank — only the Anthropic logo is visible and no messages render. Pressing Ctrl+R forces the chat to display correctly, but this happens consistently across multiple chats every session.

Steps already tried:

• Fully quit and relaunched the app
• Deleted the Cache folder from %AppData%\Claude manually
• Used built-in Help → Troubleshooting → Clear Cache and Restart
• Used built-in Help → Troubleshooting → Reset App Data

None of the above resolved the issue. Ctrl+R remains the only reliable workaround.

App version: 1.7196.0
OS: Windows 11

What Should Happen?

Chats should render and display messages immediately on load without requiring a manual Ctrl+R refresh

Error Messages/Logs

1. Open the Claude Desktop app on Windows
2. Click on any existing chat from the sidebar
3. Chat area loads blank — only the Anthropic logo spinner is visible
4. Press Ctrl+R — messages then render correctly
5. Repeat with any other chat — issue occurs consistently every session

Steps to Reproduce

1. Open the Claude Desktop app on Windows
2. Click on any existing chat from the sidebar
3. Chat area loads blank — only the Anthropic logo spinner is visible
4. Press Ctrl+R — messages then render correctly
5. Repeat with any other chat — issue occurs consistently every session

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

1.7196.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

[wad-seinjeon]

Same issue on Windows (Claude Desktop). Two related symptoms in my case:

1. Blank screen on launch — matches the original report. The app window opens but no content renders.

2. Inconsistent Recents list between launches — possibly related. On the same Windows machine, same account, fully closing and relaunching the app sometimes shows a different set of recent conversations. Conversations are replaced by a different set rather than just disappearing, and earlier ones sometimes reappear in a later launch. No specific trigger — happens at random.

Clearing the local cache temporarily restores a coherent state, but both symptoms recur.

This suggests the desktop client's local state for conversation history is not consistently reading from the same source between launches.

Happy to provide app version, screenshots across launches, or timestamps if useful.

[ruslan0108]

I can confirm this issue on my end as well.

Environment:

• OS: Windows 11
• Platform: Claude Desktop App + Claude Web (claude.ai) — identical behavior on both
• Account type: Paid (Pro/Team)

My reproduction steps:

1. Have multiple chats listed in the left sidebar
2. Switch from one chat to another by clicking it
3. Chat view is completely blank — no messages, nothing to scroll

Workaround I found:
Sending any message (e.g. a short "hey, where is my text messages?") triggers the full history to load and animate from top to bottom. But this pollutes the conversation with unnecessary messages.

Additional note:
The issue occurs both in the Desktop app and in the web version (claude.ai) when logged into the same account — so it appears to be server-side rendering behavior, not app-specific.

Switching between the web version and the Windows application does nothing, re-login does nothing, my account has a paid corporate version.

Hoping this gets prioritized — it's quite disorienting for paid users who rely on conversation continuity.

[timrv6a]

+1, same issue on Windows 11, Claude Desktop and claude.ai in Chrome including incognito. Started May 18.

[Dnominated]

Same issue. Big blank window of nothing when clicking on a previous conversation.

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.