AIbase Report: Claude Code has recently released a new terminal rendering solution - NO_FLICKER mode, which can be enabled with a single environment variable. This mode uses an experimental new renderer to completely solve the long-standing issues of terminal flickering and content jumping, and unexpectedly brings full mouse interaction support, significantly improving the efficiency of developers working in the terminal.
Core Improvements: Flicker-free Rendering, More Stable Resource Usage
Traditional terminal rendering often causes screen flickering and content jumping during long conversations or multi-agent operations, and memory and CPU usage continue to rise as the conversation length increases. NO_FLICKER mode switches to a backup screen buffer (similar to the full-screen takeover method used by vim or htop), rendering only the currently visible viewport content, achieving a true flicker-free experience.
User feedback shows that after enabling it, long conversations no longer lag, and scrolling through history is smoother, with resource consumption becoming stable. For developers who use Claude Code for code generation and multi-agent collaboration for extended periods, this is a significant experience upgrade.
Surprising Addition: Terminal Finally Supports Mouse Operations
One of the biggest highlights of NO_FLICKER mode is native support for mouse events, making terminal operations more similar to graphical interfaces:
- More Convenient Cursor Positioning: Click directly on the input box to move the cursor to the desired position, without repeatedly pressing arrow keys to adjust step by step.
- Clickable Interactive Elements: Folded tool call results can be expanded or collapsed by clicking; clicking on a URL opens it automatically in the browser, and clicking on a file path opens it in the default editor.
- Smart Selection and Copy: After dragging to select text and releasing the mouse, the content is automatically copied to the clipboard (can be disabled in settings); the mouse wheel can smoothly scroll through conversation history.
- Advanced Selection Support: Double-click to select words, triple-click to select lines. In terminals supporting the Kitty keyboard protocol (such as kitty, WezTerm, Ghostty, iTerm2), when in selection mode, Ctrl+C performs copy instead of canceling the operation.
These mouse features make the terminal experience in Claude Code more intuitive and efficient, especially suitable for scenarios requiring frequent editing of prompts, viewing outputs, or jumping between links.
Easy to Enable, Just One Command
Users just need to enter the following command in the terminal to experience it immediately:
CLAUDE_CODE_NO_FLICKER=1claude
To make it permanent, add CLAUDE_CODE_NO_FLICKER=1 to your shell configuration file (such as ~/.zshrc) or to Claude Code's settings.json. This mode was introduced in version 2.1.88 and is currently in the experimental phase. The Anthropic team is collecting user feedback to further optimize it.
Notes and Trade-offs
Although the new renderer brings significant improvements, there are some trade-offs: native Cmd+F search may not work directly and needs to be done using built-in shortcuts (such as Ctrl+O followed by /). Some terminal behaviors require adaptation to the new mechanism. Most internal users have expressed a preference for this mode, but we recommend developers test it based on their actual workflow before deciding whether to enable it permanently.
Claude Code's latest update reflects Anthropic's ongoing investment in the terminal toolchain, aiming to lower the entry barrier and enhance the experience of AI coding assistants. The developer community has generally responded positively to the NO_FLICKER mode, believing it effectively addresses the long-standing issue of "terminal flickering."
AIbase Review: For programmers who heavily rely on Claude Code, the NO_FLICKER mode is undoubtedly a quality upgrade worth trying immediately. It not only solves visual interference but also introduces mouse interaction into the terminal, quietly narrowing the experience gap between the command line and modern IDEs. We recommend everyone try it out and welcome sharing real-world usage experiences in the community.
