Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /usage tips block leaks into terminal after dialog dismissal [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54100•Fetched 2026-04-28 06:39:15
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
jesserobbinsjesserobbins
Participants
github-actions[bot]github-actions[bot]jesserobbinsjesserobbins
Timeline (top)
labeled ×3commented ×1

Fix Action

Fix / Workaround

/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.

Code Example

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
RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

The issue can be mitigated by manually clearing the screen after invoking /usage or exploring ways to disable the contextual tips.

Guidance

  • Investigate if there's an undocumented setting or flag to disable contextual tips in Claude Code.
  • Consider using a shell script or alias to automatically clear the screen after /usage is invoked.
  • Look into iTerm2 settings to see if there's an option to prevent the terminal scrollback from interfering with the prompt area.
  • Verify if this issue persists across different terminals or shells to determine if it's specific to iTerm2 or zsh.

Example

No code example is provided due to the lack of specific technical details about Claude Code's internal workings.

Notes

The solution may vary depending on the internal implementation of Claude Code and its interaction with the terminal environment. Further investigation into Claude Code's documentation or source code may be necessary.

Recommendation

Apply workaround: Manually clear the screen after invoking /usage until a more permanent solution is found, as there is no clear indication of a fixed version or a straightforward way to disable the contextual tips.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#docker error#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix /usage tips block leaks into terminal after dialog dismissal [1 comments, 2 participants]