One Env Variable That Makes Claude Code Smoother

An experimental Claude Code rendering option that improved flicker in one reported test; support and behavior can change.

One Env Variable That Makes Claude Code Smoother — AI

If you use Claude Code in the terminal, you've seen it — the screen flashes every time a response streams in. Code blocks flicker. Tables redraw. The whole output jumps as markdown gets re-parsed token by token.

There's a fix. One environment variable.


What's Happening

Terminal rendering behavior depends on the Claude Code build and terminal emulator. This article describes a rendering experiment rather than a guarantee about every installation.

CLAUDE_CODE_NO_FLICKER is an experimental option. Its internal implementation and long-term support are not established by the observation reported here.


Enable It

Set the environment variable CLAUDE_CODE_NO_FLICKER=1 before launching Claude Code.

If you use an alias like I do, embed it there:

alias claude-smooth='CLAUDE_CODE_NO_FLICKER=1 claude'

Or export it globally in your .zshrc:

export CLAUDE_CODE_NO_FLICKER=1

The alias approach keeps the experiment self-contained and easy to remove.


What Changes

I tested it with complex streaming output: multi-language code blocks, ASCII architecture diagrams, dense data tables, deeply nested lists, even a Mandelbrot set in ASCII art.

Everything streamed in line-by-line without the screen flashing or jumping. Code blocks with syntax highlighting rendered smoothly. Table columns stayed aligned as they filled in. The difference is immediately noticeable.

Test mouse interaction and scrolling in your own terminal; the rendering observation above does not establish a universal input-feature change.


Will It Break Later?

This experimental option improved rendering in the test described above. The original test did not record a precise Claude Code build and terminal version, so treat it as an observation to reproduce on your setup.


If the option causes problems, remove it from the launcher and restart the session. Future support and behavior may change; do not assume a later release will silently ignore it.