[BUG] /context command doesn't load and causes screen flickers
Resolved 💬 17 comments Opened Jan 16, 2026 by deeepanshu Closed Apr 18, 2026
💡 Likely answer: A maintainer (ashwin-ant, collaborator)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Using Claude code 2.1.9, after update,
- running /context command doesnt show the context as quickly as previous versions.
- when context actually loads, scrolling through context abruptly hides the context screen, so you are back to chat.
- there is weird ui flickering or bouncing that happens.
What Should Happen?
When running the /context command. I ran on wezterm.
Error Messages/Logs
Steps to Reproduce
- Launch claude code.
- run /context command.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.2
Claude Code Version
2.1.9
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
17 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Also experiencing this. Video of what's happening in v2.1.9:
https://github.com/user-attachments/assets/e176c2f1-2cd5-4c84-ad76-ad253a7985c3
@PaulRBerg Do you happen to have a custom statusline? I am debugging exactly the same thing since the last update. When I disable my statusline, the output is slightly better.
~Another thing I noticed that the output (of /context) disappears after about 10 seconds. I dont recall this being the case before~
@aimran-adroll I do have a custom statusline, yes.
I am using https://github.com/sirmalloc/ccstatusline
This happens w/o a statusline too. I removed mine to test.
same issue
same issue
Same issue. Unusable command. extremely disappointing. Gets worse on tmux.
Is that Warp Terminal?
Still happening in 2.1.12
@seanGSISG yes, it's Warp
FWIW: Mine terminal is ghost.
Fixed in v2.1.14
!Image
in 2.1.19 these issues are gone, but when running /context, the context data gets printed twice.
Same issue on my side: running
/contextprints the output twice.Also, why does it show overall context usage as 0% when the breakdown clearly shows tokens being used (System prompt, tools, messages, etc.)?
If tokens are already being consumed by my messages, the total usage shouldn’t still be 0%, so what exactly is that number measuring?
This was fixed in v2.1.14 — The /context overlay now opens as a proper modal that doesn't auto-close or flicker 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.