[BUG] Claude Desktop App (macOS) v1.7196.1 — chat content fails to render until forced refresh (Cmd+R)

Update — narrower reproduction pattern identified

I've found a more specific trigger for this bug that should help engineering reproduce it.

The freezing is not universal across all chats. It only affects chats that were active during a specific time window, which correlates with a session where I was using the Gmail MCP integration heavily and tool-call errors were occurring during that session.

• Chats from outside that time window (older chats and brand-new chats started afterward) render normally on the desktop app.
• Chats from inside that window consistently fail to render until Cmd+R is pressed.
• The same affected chats render normally in the browser (claude.ai) and on the mobile app.

Working hypothesis

Malformed or partial tool-call result data from the errored Gmail MCP calls was saved into the affected chats' conversation history. The desktop app's renderer cannot handle that data and fails to paint the message stream. The browser and mobile renderers apparently handle the same stored data gracefully (different render paths, different error handling), which is why those clients show no symptoms on the exact same chats.

Why this hypothesis is consistent with everything observed

• Only specific chats affected, not all → per-chat data corruption, not a global app bug
• Reset App Data did not fix it → the bad data lives server-side in the chat history, not in local cache
• Mobile and browser unaffected on the same chats → different render paths, different error handling
• Bug onset on May 15 → coincides with a heavy Gmail MCP usage session
• Cmd+R partially works → forces a fresh render that gets past the bad payload

Likely scope

This is probably not Gmail-specific. Any MCP tool integration (Gmail, Calendar, Drive, Slack, etc.) that produces partial or malformed tool-call results during a session could plant the same kind of unrenderable data into a chat's history. Users heavily using MCP integrations on the consumer desktop app are most exposed.

Reproduction suggestion for engineering

Inspect the stored conversation history of an affected chat for malformed tool_use / tool_result blocks (incomplete JSON, truncated responses, error states). Compare desktop renderer error handling vs. browser/mobile renderer error handling for those block types.

Happy to share specific chat metadata if needed via the linked support ticket.

Hello!

I recently started using Claude and already upgraded to Pro. Now I started using it more intensively for like a week.
I have the same issue just occurred yesterday for the first time.
It happens in all of my chats no matter what or how.

CMD and R helps but thats not a solution though. I re-installed, cleared cache and app data but nothing works. The mobile version is working fine. It happens on Mac App and on Safari Browser.

Good morning, thanks for posting — it really helps to know this isn't isolated. My wife is also having the same issue on a separate Pro account, so that's three of us now.
A few things to compare notes on:
For me, the issue only happens on certain chats — specifically chats from a particular time window. Is yours every chat, or also clustered?
Mine started around May 15. When did you first notice it?
I noticed my affected chats correlate with a session where I was using the Gmail integration heavily and tool-call errors were occurring. Have you used any Claude integrations recently — Gmail, Calendar, Drive, or anything similar?
Mine is only on the desktop app — mobile and browser both work fine. You mentioned Safari is also affected for you. Have you tried Chrome or Firefox to see if it's Safari-specific or broader?
Also, FYI: it turns out the anthropics/claude-code repo isn't actually the right place for consumer desktop app bugs (Anthropic support eventually confirmed there's no public tracker for the consumer app). My issue got auto-labeled "invalid" by a bot. The issue is still readable though, so this comment thread is useful regardless.
Hopefully if more people are reporting these issues, Anthropic will move on it quickly.

Greetings,

It first appeared also round about on May 15 - 16.. I have no plugins or any integrations. It's just "basic" Claude. Very weird. I only got the information from Fin AI that it seems to be a client-side rendering problem.
It happens with every chat. If I press on all my chats and switch between I get this issue every time, so he could not load any of my chats. Force reload with CMD and R helps... but thats not a solution for the future.
I tried Chrome but it's not working on chrome as well. My mobile versions works fine. But I work mainly from computer so my mobile is not an option.... just for smaller tasks etc.
hopefully this issue will get more attention.

EDIT: I tried it on Windows and I got the same issue on windows App

Will this be fixed, do you guys think, or no? It's a minor inconvenience, but still is an issue nonetheless.

Although I can't speak for what Anthropic is going to do, I think multiple users having the same issue will likely push them to address it soon. Based on everything I've gathered: the issue is documented, multiple users across plan tiers are confirming it, and Anthropic support has acknowledged it as a client-side rendering problem. They ship desktop app patches fairly often, so I'd expect a fix in a reasonable timeframe, though I can't promise when. In the meantime, Cmd+R is the only workaround I've found that consistently helps. Mobile and the browser (Chrome/Firefox, not Safari for some users) are also working as a fallback.

Hey guys,

today I updated the Application on Mac and this problem is solved. I have tried out a few times to re-produce and they load as usual. I'll keep an eye on it though.
version updated today: Claude 1.7196.3 (ca0c62) 2026-05-16T23:42:08.000Z

Yes, mine also started working well after the update and apparently we have yet another update--1.8089.1

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.