ClaudeCode No Flicker Mode Changes Everything!
Claude Code released a 'no flicker mode' that eliminates screen flashing and memory bloat issues in terminal usage. The update includes mouse support and uses an alternate screen buffer to provide a smoother, more stable coding experience.
Summary
Claude Code has introduced a significant update called 'no flicker mode' that addresses one of the most persistent problems with terminal-based AI coding tools. The flicker issue occurred because Claude Code is built with React rendering to terminals, which weren't designed for interactive UIs, causing the entire terminal buffer to redraw with every update. The Anthropic team had previously reduced flickering by 85% through a rendering system rewrite, but about a third of sessions still experienced flickers, especially in VS Code Terminal, TMux, and iTerm 2. The new no flicker mode can be activated with the environment variable 'CLAUDE_CODE_NO_FLICKER=1' and switches to an alternate screen buffer similar to Vim or htop. This approach keeps the input box fixed at the bottom, only renders visible messages rather than entire conversation history, and maintains flat memory usage even in long sessions. Unexpectedly, the update also includes full mouse support in the terminal, allowing users to click to move cursor position, expand tool outputs, scroll with mouse wheel, and click URLs directly. Users can disable mouse capture while keeping flicker-free rendering using 'CLAUDE_CODE_DISABLE_MOUSE=1'. The feature is marked as a research preview and requires Claude Code v2.188 or later. There are some trade-offs including conversation history living in the alternate buffer rather than terminal scrollback, and potential clipboard copy issues over SSH due to OSC 52 escape sequences. Anthropic has been working on multiple fixes including upstream patches to VS Code's terminal and TMux for synchronized output support, making this part of a comprehensive approach to improving terminal-based AI coding tools.
Key Insights
- Claude Code's flicker problem occurs because it's built with React rendering to terminals that weren't designed for interactive UIs, causing entire terminal buffer redraws with every update
- Anthropic previously reduced flickering by 85% through a rendering system rewrite, but about a third of sessions still experienced at least one flicker
- No flicker mode uses an alternate screen buffer and only renders messages visible on screen rather than the entire conversation history, keeping memory usage flat even in long sessions
- The update unexpectedly includes full mouse support in the terminal, allowing users to click to move cursor, expand outputs, scroll, and click URLs directly
- Anthropic has been pushing upstream fixes including patches accepted into VS Code's terminal and TMux to add synchronized output support, eliminating flicker at the source
Topics
Full transcript available for MurmurCast members
Sign Up to Access