[Bug] Cache warning shown after /clear command before new messages

Resolved 💬 2 comments Opened Apr 22, 2026 by DJoeDt Closed May 6, 2026

Bug Description
I get a cache warning
although I just /cleared the conversation, is that valid? The message:
▐▛███▜▌ Claude Code v2.1.117
▝▜█████▛▘ Sonnet 4.6 with medium effort · Claude Pro
▘▘ ▝▝ ~/Documents/audioworks/audioworks/audio_mix_service

❯ /clear

⎿ (no content)

❯ /model

─────────────────────────────────────────────────────────────────────────────
───
Switch model?
Your next response will be slower and use more tokens

This conversation is cached for the current model. Switching to Opus 4.7
means the full history gets re-read on your next message.

❯ 1. Yes, switch to Opus 4.7

  1. No, go back

Environment Info

  • Platform: linux
  • Terminal: vte-based
  • Version: 2.1.117
  • Feedback ID: 8f4f777b-80f7-4d7e-8342-c10e81eb7ff1

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/jochen/.local/share/claude/versions/2.1.117 (expected in multi-process scenarios)\n    at Tn8 (/$bunfs/root/src/entrypoints/cli.js:2756:2177)\n    at tK_ (/$bunfs/root/src/entrypoints/cli.js:2756:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T21:14:14.458Z"}]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗