Skip to content
BENIBIX Learn

CLAUDE_CODE_NO_FLICKER vs CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN

People think these two do the same thing, since both are about the screen. They do the opposite. NO_FLICKER turns fullscreen mode on. DISABLE_ALTERNATE_SCREEN turns it off. It keeps the chat in your terminal's own history. If both are set, the second wins.

AI⌨️ Claude Code

CLAUDE_CODE_NO_FLICKER

Set to 1, it turns on fullscreen mode, with less flicker.

CLAUDE_CODE_NO_FLICKER set to 1 turns on fullscreen mode. In fullscreen, Claude Code draws in its own screen, with less flicker and steady memory in long chats. It is a research preview. It wins over the tui setting, and /tui fullscreen does the same.

Example
Emma's long chats made her terminal flicker and slow down. She sets this, and the screen stays still.
Why it matters
In long sessions, the classic mode can flicker and use more memory. Fullscreen fixes both.
Full entry
AI⌨️ Claude Code

CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN

Set to 1, it keeps the classic mode, with the terminal's own scroll.

CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN set to 1 turns fullscreen off. Claude Code uses the classic mode. The chat stays in your terminal's own history, so Cmd+F and tmux copy work as usual. It wins over NO_FLICKER and the tui setting. Agent view still uses fullscreen.

Example
Jack copies output with tmux copy mode all day. Fullscreen broke that. He sets this, and copy mode works again.
Why it matters
Some people rely on their terminal's own search and copy. Classic mode keeps those.
Full entry

In one line

CLAUDE_CODE_NO_FLICKER
Set to 1, it turns on fullscreen mode, with less flicker.
CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN
Set to 1, it keeps the classic mode, with the terminal's own scroll.