/usage tips block leaks into terminal after dialog dismissal

Resolved 💬 4 comments Opened Apr 27, 2026 by jesserobbins Closed May 7, 2026

What I was doing

Running /usage in Claude Code (v2.1.117) on macOS, then dismissing the status dialog and typing my next prompt.

What happened

After the dialog is dismissed (Status dialog dismissed), the contextual tips block from the bottom of /usage remains drawn in the terminal scrollback / prompt area. When I start typing, my input visually collides with the leftover tip text — the tips appear to "override" the prompt rather than being cleared.

Example of what stayed on screen, with my typed text on the first line getting tangled into the leftover tip output:

how do I get rid of the 45% of your usage came from subagent-heavy sessions
   Each subagent runs its own requests. Be deliberate about spawning them — and
   consider configuring a cheaper model for simpler subagents.
  44% of your usage was at >150k context
   Longer sessions are more expensive even when cached. /compact mid-task,
   /clear when switching to new tasks.
  20% of your usage was while 4+ sessions ran in parallel
   All sessions share one limit. If you don't need them all at once, queueing
   uses it more evenly.
  d to day · w to week that appears at usage

The first line is my prompt text colliding with 45% of your usage came from subagent-heavy sessions. Subsequent lines are leftover tip body and the footer hint (d to day · w to week).

Why it matters

/usage becomes hard to read and the prompt area becomes unusable until the screen is cleared manually. There's also no documented setting to disable those contextual tips, so there's no workaround beyond clear after every /usage invocation.

Environment

  • Claude Code: 2.1.117
  • OS: macOS (Darwin 25.4.0)
  • Shell: zsh
  • Terminal: iTerm2

View original on GitHub ↗

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