[BUG] 2.1.89 - terminal content disappearing.

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/41814
2. https://github.com/anthropics/claude-code/issues/41996
3. https://github.com/anthropics/claude-code/issues/42024

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

this is a different issue, this is not compaction. I can confirm i also have this issue on 2.1.89

What Should Happen?
It should show the conversation as normal.

Error Messages/Logs
Steps to Reproduce
_1._ Start conversation
_2._ Make a plan
_3._ All previous context gone, he remembered, but the text wasn't there, just the new plan

Claude Model
Opus

Is this a regression?
Yes, this worked in a previous version

Last Working Version
2.1.87

Claude Code Version
2.1.89

Platform
Anthropic Max Account

Operating System
Ubuntu 24.04/Debian Linux

Terminal/Shell
Ghostty

Edited:
workaround in: https://github.com/anthropics/claude-code/issues/41965

#41965

Same issue as https://github.com/anthropics/claude-code/issues/41968

Can confirm this regression on Linux as well. I encountered the same terminal content disappearing issue on v2.1.89, which is one of the reasons I rolled back to and stayed on v2.1.81.

My environment

• OS: Linux (Ubuntu-based)
• Terminal: Multiple (direct terminal + tmux + Tailscale SSH)
• Claude Code: v2.1.89 exhibited the issue; rolled back to v2.1.81 (patched) where it does not occur

Observed behavior

After updating to 2.1.89, terminal output from Claude Code would intermittently vanish — the header and input area remained visible, but streamed content and tool output would disappear. This was reproducible across different terminal emulators and persisted across sessions.

Additional context

v2.1.89 also has unresolved prompt caching bugs (#40524, #34629) that cause excessive token consumption. Between the terminal rendering regression and the cache issues, I'd recommend staying on an earlier version if possible.

For anyone affected: v2.1.81 does not exhibit this terminal rendering issue, and with a cache fix patch, it also resolves the token inflation problem. Details on the cache fix (which also documents version compatibility):
👉 https://github.com/ArkNill/claude-code-cache-analysis

Same as my issue: #41968

ㅈ같네 정말

Update (April 2): v2.1.90 resolves the cache regression that was present in v2.1.89.

Benchmark confirms v2.1.90 achieves 95-99% cache read in stable sessions (both npm and standalone). If you haven't already, update and pin:

claude update
# Then add to ~/.claude/settings.json:
# { "env": { "DISABLE_AUTOUPDATER": "1" } }

Details: https://github.com/ArkNill/claude-code-cache-analysis

Same issue here on 2.1.90 https://github.com/anthropics/claude-code/issues/42491

@pvujic Thanks for linking #42491. The terminal content disappearing issue may interact with token consumption in unexpected ways — if the client is re-sending context that was supposed to be cached but the terminal output got corrupted or re-rendered, it could invalidate cache breakpoints. Worth checking if the drain correlates specifically with sessions where the terminal rendering bug occurs.

https://github.com/anthropics/claude-code/issues/41814

April 3 update: The cache regression (Bugs 1-2) is fixed in v2.1.91. However, systematic proxy testing revealed additional unfixed mechanisms — a 200K tool result budget cap, a client-side false rate limiter (151 synthetic entries found), and silent microcompact clearing (327 events). Anthropic responded on X (Lydia Hallie) acknowledging peak-hour tightening but stating "none were over-charging you" — our measured data shows mechanisms their statement does not cover. Full analysis: claude-code-cache-analysis

This is a duplicate of #41814, which was fixed as of version 2.1.101.

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.