[BUG] CLAUDE_CODE_NO_FLICKER=1 produces weird rendering artifacts with zellij
Status Fixed / completed
Reported on v2.1.89
Maintainer reply None cached
Activity 3 comments · opened Apr 3, 2026 · closed Apr 7, 2026
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?
Zellij version: 0.44.0
Claude Code version: 2.1.89
Terminal: Kitty on macOS
Issue: When in full-screen mode (CLAUDE_CODE_NO_FLICKER=1), pressing Fn+Up/Fn+Down or using the mouse wheel to scroll produces rendering artifacts (see video).
Legacy scrollback mode renders correctly.
https://github.com/user-attachments/assets/79dd166b-e5ec-4ada-b13c-8eee9d70fbe0
What Should Happen?
The rendering should be normal.
Error Messages/Logs
Steps to Reproduce
- Open claude code under a zellij session
CLAUDE_CODE_NO_FLICKER=1 claude. - Try to scroll to see the rendering issue.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.89
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Other
Additional Information
_No response_
3 Comments
Why was this issue closed without comment or update?
I have verified that this issue persists in version 2.1.92; it remains unresolved.
hey. it's fixed at the terminal level here
https://github.com/Dcouple-Inc/Pane/pull/120
open source, using xtermjs which is the same terminal as VS Code. feel free to copy this fix or download the latest release to run claude code on any operating system with the fix in place. i was so mad and frustrated at this that I had to fix it myself.
yeah i had to switch off cursor/vscode and build myself an ide that managed xtermjs (the library they both use) well enough for the complex TUIs to not break.
works great and i have a fix for the scroll jump i just implemented rn here
https://github.com/Dcouple-Inc/Pane/pull/120
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.