[BUG] /context command window flickers for 3-4 seconds then closes immediately
Status Fixed / completed
Reported on v2.1.9
Maintainer reply ✓ Yes — ashwin-ant
Activity 8 comments · opened Jan 16, 2026 · closed Apr 18, 2026
💡 Likely answer: A maintainer (ashwin-ant, collaborator)
responded on this thread — see the highlighted reply below.
Bug Description
The /context command opens a window that flickers/flashes for 3-4 seconds, then immediately closes without displaying any content. Previously this worked correctly.
Environment
- Claude Code version: 2.1.9
- OS: macOS 15.7.3 (Sequoia)
- Terminal: iTerm2 3.6.6
- Shell: zsh
- Node: Tested on both v25.3.0 and v22.22.0 (LTS) - issue persists on both
Steps to Reproduce
- Start a Claude Code session
- Type
/contextand press Enter - Observe: window flickers/flashes for 3-4 seconds
- Window closes immediately without showing context usage
Expected Behavior
The /context command should display a stable window showing context usage breakdown (tokens used by conversation, files, tools, etc.)
Actual Behavior
Window appears briefly, flickers for 3-4 seconds, then closes. No content visible.
Additional Context
- This worked correctly in previous versions
- Issue occurs in iTerm2 (not tested in other terminals)
8 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
FYI Issue remains in v2.1.12
same issue
still present
Still present for Ghostty
Same in Sequoia 15.7.3 Terminal. The command use to be a blocking command so now a fresh cli startup, /context provides no immediate or obvious output until the required network/model query completes (for me, about 2 seconds lag). This could be the reason for the "flickering" behavior reported and observed. Previous behavior (early December version) was preference by me and clearly others.
This was fixed in v2.1.14 — /context, /config, /model, and /todos overlays no longer flicker and close immediately while background processing is running. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.
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.