Omniscio

OmniscioGuidesClaude Code fullscreen

Claude Code fullscreen: flicker, scroll and mouse

Fullscreen rendering is the Claude Code interface drawn on the terminal's alternate screen buffer, the same surface vim and htop take over. It removes flicker, keeps memory flat in long conversations, and adds mouse support.

This page covers what changes when you turn it on, the keys that scroll and search, how to select and copy text, the tmux settings that keep the mouse wheel alive, and what to do when the screen looks wrong.

Last checked against Anthropic's Claude Code documentation on November 20, 2026. By the Omniscio team. Updated .

What fullscreen rendering is

Anthropic describes fullscreen rendering as an alternative rendering path for the Claude Code CLI. It draws the interface on the terminal's alternate screen buffer and renders only the messages currently visible, which cuts the amount of data sent to the terminal on every update.

Two things follow from that. The input box stays fixed at the bottom of the screen instead of moving as output streams in, so if the prompt line does not move while Claude is working, fullscreen rendering is active. And Anthropic documents memory as staying flat however long the conversation runs, because only visible messages are kept in the render tree.

The difference is most noticeable where terminal rendering throughput is the bottleneck: the VS Code integrated terminal, tmux, and iTerm2. If your terminal jumps to the top while Claude works, or the screen flashes as tool output streams in, this is the mode Anthropic offers for it.

The name misleads people. Fullscreen describes how Claude Code takes over the terminal's drawing surface, the way vim does. It has nothing to do with maximizing the terminal window, and it works at any window size.

Source: Fullscreen rendering in Anthropic's Claude Code documentation, read November 20, 2026.

Turn it on, and turn it off

Run /tui fullscreen inside any conversation. Claude Code saves the tui setting and relaunches the session in fullscreen. Run /tui default to switch back to the classic renderer, or /tui with no argument to print which renderer is active.

The relaunch carries the conversation as it appears on screen, along with your permission mode, effort level, the model you last picked, your --allowed-tools, --disallowed-tools and prompt flags, and a --chrome or --no-chrome choice. After a /rewind, it relaunches from the point you rewound to, not from the longer transcript on disk.

Some sessions are refused instead of relaunched. Claude Code prints Cannot switch renderers in this session with the reasons when it cannot pass a restriction to the new process, such as a --system-prompt replacement, a --tools allowlist, --setting-sources, or a deny or ask rule that a hook added for that session only. Nothing is switched and nothing is saved in that case.

Two environment variables do the same job before launch. CLAUDE_CODE_NO_FLICKER=1 starts a session in fullscreen — the name is historical, and it is the switch that turns the flicker fix on. and CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 forces the classic renderer no matter what the saved setting says. The /tui command clears CLAUDE_CODE_NO_FLICKER from the relaunched process so the setting it writes takes effect.

Whether you start in fullscreen without asking depends on your setup: the release you first used, whether your session fetches feature flags from Anthropic, whether a saved tui setting exists, and states such as screen-reader mode, a failed fullscreen start, or iTerm2's tmux -CC. If you start in the classic renderer and have never saved the setting, Claude Code may offer the switch in a dialog at startup; it stops offering after three launches.

Sources: "Enable fullscreen rendering" and "Fullscreen by default" in Fullscreen rendering, read November 20, 2026.

Scroll the conversation

Fullscreen rendering handles scrolling inside the app rather than handing it to the terminal. Anthropic's table is short:

  • PgUp and PgDn scroll half a screen.
  • Ctrl+Home jumps to the start of the conversation.
  • Ctrl+End jumps to the latest message and resumes auto-follow.
  • The mouse wheel scrolls a few lines at a time.

Scrolling up pauses auto-follow, so new output does not pull you back to the bottom. A Jump to bottom button floats over the bottom of the transcript while you are scrolled up and shows a count such as 3 new messages when output arrives. Click it, press Ctrl+End, or scroll to the bottom to follow again.

MacBook keyboards have no dedicated PgUp, PgDn, Home or End keys. Hold Fn with an arrow key: Fn+↑ sends PgUp, Fn+↓ sends PgDn, and the left and right arrows send Home and End. Anthropic notes that Ctrl+Fn+→, the Mac equivalent of Ctrl+End, does not reach Claude Code on macOS, so there is no default jump-to-bottom chord on that keyboard; the button and the mouse wheel both work.

If the wheel feels slow, set CLAUDE_CODE_SCROLL_SPEED to a multiplier, where 3 matches the default in vim. The value accepts anything positive up to 20, including fractions below 1 for a trackpad that already accelerates. /scroll-speed opens a dialog that adjusts the same value live, and writes it to ~/.claude/settings.json. To keep a constant rate per notch instead of speeding up on a fast spin, set wheelScrollAccelerationEnabled to false.

Under iTerm2 the wheel needs its own setting. If the wheel does nothing but PgUp and PgDn work, open Settings → Profiles → Terminal and turn on Enable mouse reporting; the same setting is required for click-to-expand and text selection.

Sources: "Scroll the conversation", "Auto-follow" and "Mouse wheel scrolling" in Fullscreen rendering, read November 20, 2026.

Select text with the mouse, or without it

Fullscreen rendering captures mouse events and handles them itself. Click in the prompt to place the cursor, click a suggestion in the / or @ list to accept it, click an option in a menu to choose it, and click a collapsed tool result to expand it. Hold Cmd on macOS, or Ctrl elsewhere, and click a URL or file path to open it; a plain click does not open links.

Click and drag selects text inside Claude Code, and the selection is copied to your clipboard automatically on mouse release. Double-click selects a word, double-clicking a URL selects the whole URL, and triple-click selects the line. To stop the automatic copy, turn off Copy on select in /config; then Ctrl+Shift+c copies, and on terminals that support the kitty keyboard protocol, so does Cmd+c.

Because the selection lives inside Claude Code, your terminal's own copy-on-select and tools like tmux copy mode do not see it. For a one-off native selection, hold the key your terminal uses while you click and drag: Fn in Terminal.app, Option in iTerm2, and Shift in the VS Code terminal and most others. Claude Code shows the right key in its on-screen hint.

If mouse capture gets in the way more than it helps, two variables trade it back:

  • CLAUDE_CODE_DISABLE_MOUSE=1 keeps the flicker-free rendering and flat memory, and gives selection back to your terminal. Keyboard scrolling still works. You lose click-to-position, click-to-expand, URL clicking and wheel scrolling inside Claude Code.
  • CLAUDE_CODE_DISABLE_MOUSE_CLICKS=1 keeps the wheel but turns off click, drag and hover handling. CLAUDE_CODE_DISABLE_MOUSE wins when both are set.

Sources: "Use the mouse" and "Keep native text selection" in Fullscreen rendering, read November 20, 2026.

Fullscreen in tmux

Fullscreen rendering works inside tmux, with three caveats from Anthropic's page. The one people hit first is the wheel: to scroll Claude Code with the mouse wheel while another tmux pane is active, turn on tmux's mouse mode in ~/.tmux.conf and reload the config.

set -g mouse on

The second is a mode to avoid. Fullscreen rendering is incompatible with iTerm2's tmux integration mode, the one you enter with tmux -CC, because iTerm2 draws each pane natively and the alternate screen buffer and mouse tracking do not work there. Regular tmux inside iTerm2, without -CC, is fine.

The third is flicker. tmux releases through the 3.6 series do not implement synchronized output, so redraws can flicker more than they would outside tmux. Claude Code probes the terminal for support at startup and uses it when the terminal reports it, so the fix is a newer tmux, or running Claude Code in its own terminal tab.

The tmux guide covers setting up Claude Code inside tmux and driving another pane with send-keys.

Source: "Use with tmux" in Fullscreen rendering, read November 20, 2026.

When the screen looks wrong

Garbled or partly blank display. Press Ctrl+L to redraw. The conversation and your input stay in place. Cmd+K does the same where your terminal passes it through; iTerm2 handles Cmd+K itself and Claude Code repaints afterwards.

Stale fragments of earlier output. Fullscreen rendering sends only the cells that changed between frames, and some terminals, most commonly Windows Terminal and other ConPTY-backed hosts, coalesce those writes incorrectly. Setting CLAUDE_CODE_ALT_SCREEN_FULL_REPAINT=1 repaints every cell on every frame instead. On Windows this is already on for background sessions and agent view, so you only need it for an interactive fullscreen session you started yourself.

The CLI keeps starting in the classic renderer. If a fullscreen session crashed before it finished starting, the next session starts classic and prints a line saying so. One failed start means Claude Code tries fullscreen again next time; two in a row means it stays classic until you update Claude Code or run /tui fullscreen. /tui with no argument prints the reason on its Current renderer line. A session counts as started once it has drawn its first frame and either stayed up for ten seconds or ended with /exit, Ctrl+C or Ctrl+D.

tmux copy mode cannot select. That is expected while Claude Code captures the mouse. Use Claude Code's own selection, or press Ctrl+O and then [ to write the conversation into the scrollback where tmux can reach it.

What this mode does not do

It is a research preview. Anthropic says it has been tested on common terminal emulators and that you may hit rendering problems on less common ones, and it directs feedback to /feedback or the claude-code GitHub repo with your emulator name and version.

It does not change your permission mode, your model, or what Claude can do. It changes where the interface is drawn and what your terminal's native tools can see.

Where these answers come from

  • Everything on this page: Fullscreen rendering, read November 20, 2026.
  • The renderer the CLI starts in, the tui setting and its interaction with CLAUDE_CODE_NO_FLICKER: the "Fullscreen by default" section of the same page.
  • Compacted sessions and the transcript file: Explore the context window, read the same day.

No part of this page was tested on this site's own machine: every claim is quoted from Anthropic's page, which is a research preview and may change between releases.

Common questions

Is fullscreen rendering on by default?

Sometimes. Anthropic's table starts sessions fullscreen when you set CLAUDE_CODE_NO_FLICKER=1 or first used Claude Code on or after May 6, 2026 with feature flags fetching, and classic in several other cases. A saved tui setting decides next, but it is not final: CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 and CLAUDE_CODE_NO_FLICKER=0 force the classic renderer regardless, and attached background sessions always render fullscreen.

Can I keep the flicker fix but not the mouse?

Yes. CLAUDE_CODE_DISABLE_MOUSE=1 turns off mouse capture while keeping the flicker-free rendering and flat memory. Keyboard scrolling keeps working.

Why did the wheel speed change?

Claude Code accelerates scrolling when you spin the wheel quickly. Set wheelScrollAccelerationEnabled to false for a constant rate, or change the base speed with CLAUDE_CODE_SCROLL_SPEED or /scroll-speed.

Does the diff panel still work?

Yes, and it opens beside the conversation rather than in place, so you can watch changes accumulate while Claude works.