Claude Code's New No-Flicker Mode Rewrites How the Terminal Renders

Claude Code has had a flickering problem since launch. You’d be mid-session, tools streaming output, and the whole terminal would flash and tear. Scroll position would jump to the top. The screen would redraw itself in visible chunks. It was distracting at best, nauseating at worst.

Today, Anthropic shipped their answer: a new fullscreen rendering mode that you can turn on with a single environment variable.

Boris Cherny, the creator of Claude Code, announced the feature on X. The mode uses an experimental renderer that draws the interface on the terminal’s alternate screen buffer, the same approach used by vim and htop. Most internal users at Anthropic already prefer it over the old renderer.

How to Turn It On

One environment variable:

CLAUDE_CODE_NO_FLICKER=1 claude

To make it permanent, add this to your ~/.zshrc or ~/.bashrc:

export CLAUDE_CODE_NO_FLICKER=1

You need Claude Code v2.1.88 or later. This is a research preview, so the behavior may change based on feedback.

What It Actually Does

The old renderer drew Claude Code’s output into your terminal’s normal scrollback buffer. Every time something changed (a tool finished, new text streamed in, a diff appeared), it had to clear and redraw that region. Terminals don’t support incremental scrollback updates, so a full redraw was the only option. That’s where the tearing came from.

The new fullscreen mode moves everything to the alternate screen buffer. Only the messages visible on screen get rendered. The input box stays pinned at the bottom instead of moving as output streams in. If the input stays put while Claude works, you know fullscreen mode is active.

The practical benefits:

• No more flickering. The alternate screen buffer lets Claude Code control exactly what appears on screen without fighting the terminal’s scrollback behavior.
• Flat memory usage. Because only visible messages live in the render tree, memory stays constant regardless of conversation length. Long sessions used to eat RAM as the component tree grew; that’s gone now.
• Mouse support. Click to position your cursor in the input, click collapsed tool results to expand them, click URLs and file paths to open them, click and drag to select text.
• In-app scrolling. Mouse wheel and keyboard shortcuts (PgUp/PgDn, Ctrl+Home/Ctrl+End) let you move through the conversation without leaving the interface.

The Backstory: Why Flickering Was So Hard to Fix

Claude Code’s rendering pipeline is unusual. It’s built on React with a custom terminal renderer, and it operates more like a game engine than a typical TUI app. The pipeline goes:

React scene graph, layout, 2D rasterization, diff against previous frame, ANSI escape sequence generation.

All of that has to happen within roughly a 16ms frame budget, with about 5ms available for the React-to-ANSI conversion.

Earlier this year, Anthropic shipped a differential renderer that brought flickering down by about 85%. After that update, only about a third of sessions saw any flicker at all. They also pushed upstream patches to add synchronized output (DEC mode 2026) to VSCode’s terminal and tmux, which eliminates flickering entirely in terminals that support it.

But the diff renderer was still working within the constraints of the normal scrollback buffer. No amount of clever diffing could fix the fundamental problem: when scrollback content changes, the terminal has to redraw it, and that redraw is visible. The alternate screen buffer sidesteps the issue entirely.

What Changes Day-to-Day

Because the conversation lives on the alternate screen buffer instead of native scrollback, a few things work differently.

Search: Your terminal’s Cmd+F won’t see the conversation anymore. Instead, press Ctrl+O to enter transcript mode, then / to search with less-style navigation (n/N for next/previous match). If you need native search, press [ in transcript mode to dump the full conversation into your terminal’s scrollback.

Text selection: Click and drag to select text inside Claude Code. Double-click grabs a word (file paths select as one unit). Selected text copies to your clipboard automatically on mouse release. If you want your terminal’s native click-and-drag selection back, you can disable mouse capture:

CLAUDE_CODE_NO_FLICKER=1 CLAUDE_CODE_DISABLE_MOUSE=1 claude

You keep the flicker-free rendering and flat memory, but lose mouse scrolling and click interactions.

Scrolling speed: Some terminals (like VSCode’s integrated terminal) send one scroll event per mouse wheel notch with no multiplier. If scrolling feels slow, bump it up:

export CLAUDE_CODE_SCROLL_SPEED=3

Values from 1 to 20. A value of 3 matches vim’s default.

Terminal Compatibility

The difference is most noticeable in terminal emulators where rendering throughput is the bottleneck: VSCode’s integrated terminal, tmux, and iTerm2. If your scroll position was jumping to the top while Claude worked, or the screen flashed during tool output, those problems are gone in this mode.

tmux: Works, but mouse wheel scrolling requires set -g mouse on in your .tmux.conf. Keyboard scrolling works either way. One caveat: fullscreen rendering is incompatible with iTerm2’s tmux integration mode (tmux -CC). Regular tmux inside iTerm2 is fine.

Ghostty: If you’re on Ghostty, you were probably already flicker-free thanks to its DEC 2026 synchronized output support. The new mode still helps with memory usage in long sessions.

The Environment Variables

Three new variables control the fullscreen rendering:

Variable	What it does
CLAUDE_CODE_NO_FLICKER=1	Enables fullscreen rendering (the main switch)
CLAUDE_CODE_DISABLE_MOUSE=1	Turns off mouse capture, keeps native text selection
CLAUDE_CODE_SCROLL_SPEED=N	Mouse wheel scroll multiplier (1-20)

To turn it off, unset the variable or set CLAUDE_CODE_NO_FLICKER=0.

Should You Turn It On?

If flickering has been bothering you, yes, immediately. If you use VSCode’s integrated terminal or tmux, the improvement will be obvious. If you’re on Ghostty and never noticed flickering, you’ll still benefit from the flat memory usage in long conversations.

The tradeoffs are real but manageable. You lose native Cmd+F search (replaced by Ctrl+O then /). Mouse capture changes how text selection works (fixable with CLAUDE_CODE_DISABLE_MOUSE=1). And it’s still a research preview, so edge cases on unusual terminal configurations are possible.

For most people who spend hours a day in Claude Code, the stability is worth the adjustment.

Docs: Fullscreen rendering | Environment variables