Text of code.claude.com › docs › en › fullscreen as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Fullscreen rendering - Claude Code Docs

Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. Fullscreen rendering is a research preview . Whether you start in fullscreen or in the classic renderer depends on your setup. Run /tui fullscreen or /tui default to switch in your current conversation.

Behavior may change based on feedback. Fullscreen rendering is an alternative rendering path for the Claude Code CLI that eliminates flicker, keeps memory usage flat in long conversations, and adds mouse support. It draws the interface on the terminal’s alternate screen buffer, like vim or htop , and only renders messages that are currently visible. This reduces the amount of data sent to your terminal on each update.

The difference is most noticeable in terminal emulators where rendering throughput is the bottleneck, such as the VS Code integrated terminal, tmux, and iTerm2. If your terminal scroll position jumps to the top while Claude is working, or the screen flashes as tool output streams in, this mode addresses those. The term fullscreen describes how Claude Code takes over the terminal’s drawing surface, the way vim does. It has nothing to do with maximizing your terminal window, and works at any window size.

Enable fullscreen rendering Run /tui fullscreen inside any Claude Code conversation. The CLI saves the tui setting and relaunches into fullscreen. Run /tui default to switch back to the classic renderer, or /tui with no argument to print which renderer is active. In screen reader mode , Claude Code always uses the classic renderer except in attached background sessions , which still render fullscreen. If you run /tui fullscreen in any other session, Claude Code prints an explanation instead of switching and doesn’t change the saved tui setting.

Claude Code carries these into the relaunched session: The conversation as it appears on screen. After a /rewind , that means: If you rewound earlier in the session, Claude Code relaunches from the rewound point, not from the longer transcript saved on disk. For example, if you rewound past your last three messages, the relaunched session opens without them If you rewound to before your first message, Claude Code relaunches with an empty conversation Your permission mode and effort level The model you last picked with /model Rules you passed with --allowed-tools or --disallowed-tools , and your --agent , --agents , --append-system-prompt , and --system-prompt-snapshot flags A --chrome or --no-chrome flag you launched with, so Chrome integration stays on or off as you chose for this session Claude Code declines to relaunch if the session has a restriction it can’t pass to the restarted process.

Restrictions it can’t pass include: Launch flags such as a --system-prompt replacement, a --tools allowlist, or --setting-sources Deny or ask rules that a hook or SDK permission update added for this session only In that case Claude Code prints Cannot switch renderers in this session with the reasons. It doesn’t switch or save anything. You can also set the CLAUDE_CODE_NO_FLICKER environment variable before starting Claude Code: CLAUDE_CODE_NO_FLICKER = 1 claude For how the tui setting and the variable combine when both are set, see the setting’s entry.

After a failed fullscreen start , Claude Code still honors the variable but not the setting. The /tui command clears CLAUDE_CODE_NO_FLICKER from the relaunched process so the setting it writes takes effect. Fullscreen by default Attached background sessions render fullscreen, and other sessions in screen reader mode use the classic renderer. Otherwise, Claude Code starts you in the renderer from the first row of this table that matches your setup: Your situation Renderer you start in You set CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 or CLAUDE_CODE_NO_FLICKER=0 Classic You set CLAUDE_CODE_NO_FLICKER=1 Fullscreen Claude Code turned fullscreen off after a failed fullscreen start on this machine Classic You’re in iTerm2’s tmux -CC integration mode , or you’re connected over SSH to Claude Code running on Windows Classic You saved a tui setting The renderer the setting names Your session doesn’t fetch feature flags from Anthropic , and Claude Code has stopped offering the startup dialog on this machine Classic Your session doesn’t fetch feature flags from Anthropic, and this machine’s first Claude Code launch ran v2.1.239 or later Fullscreen Your session fetches feature flags from Anthropic, and you first used Claude Code on or after May 6, 2026 Fullscreen Anything else Classic Sessions that don’t fetch feature flags include those through Amazon Bedrock , Google Cloud’s Agent Platform , or Microsoft Foundry , and those with telemetry turned off.

If you start in the classic renderer and haven’t saved a tui setting, Claude Code may open a dialog at startup offering the switch: If you accept, Claude Code relaunches the same way /tui fullscreen does, carrying the same session state, and saves the setting once the relaunched session has started successfully . If you choose Not now , Claude Code doesn’t offer again on this machine. Claude Code stops offering after it has shown the dialog on three launches, answered or not.

What changes Fullscreen rendering changes how the CLI draws to your terminal. The input box stays fixed at the bottom of the screen instead of moving as output streams in. If the input doesn’t move while Claude is working, fullscreen rendering is active. Only visible messages are kept in the render tree, so memory stays constant regardless of conversation length. Because the conversation lives in the alternate screen buffer instead of your terminal’s scrollback, a few things work differently: Before Now Details Cmd+f or tmux search to find text Ctrl+o for transcript mode, then / to search or [ to write to scrollback Search and review the conversation Terminal’s native click-and-drag to select and copy In-app selection, copies automatically on mouse release Use the mouse Cmd -click to open a URL Cmd -click on macOS, Ctrl -click elsewhere Use the mouse If mouse capture interferes with your workflow, you can turn it off while keeping the flicker-free rendering.

Use the mouse Fullscreen rendering captures mouse events and handles them inside Claude Code: Click in the prompt input to position your cursor anywhere in the text you’re typing. Click a suggestion in the / command or @ file list to accept it. Hovering highlights the row under your cursor. Click an option in a select menu to choose it. This covers permission prompts, /model , /config , and other dialogs that show a list of options.

Click an option in a multi-select menu to toggle it, and click the submit button to confirm your choices. Clicking a free-text row, such as the Other row in a multiple-choice question, focuses its input field so you can type an answer. Click a setting’s value in the /config panel to change it, and scroll the settings list with the mouse wheel. Requires Claude Code v2.1.271 or later. Scroll a select or multi-select menu with the mouse wheel when it has more options than it shows at once, such as the /model list in a short terminal window.

The wheel scrolls the list while the pointer is over its options. Requires Claude Code v2.1.280 or later. Scroll an overflowing list with its scrollbar. In list panels such as /skills , /mcp , and /plugin ’s Installed list, a scrollbar appears beside a list with more rows than fit while the pointer is over it. Click the track to jump to that point, or drag the thumb. Requires Claude Code v2.1.281 or later. Where the bar has ↑ and ↓ arrows at its ends, click an arrow to scroll a single row, or hold it to keep scrolling.

The arrows require Claude Code v2.1.286 or later. Click the ↑ N more or ↓ N more row at the edge of a list to jump to that end of the

The rest of this page is on the live site.