The Claude Code Setting Almost Nobody Turns On (And Why It Makes the Terminal the Best Place to Use Claude)

TL;DR: Claude Code has an opt-in mode called fullscreen rendering (also known as no-flicker mode). Turn it on with the command /tui fullscreen. It stops the terminal from flickering on long sessions and adds full mouse support, so you can finally click anywhere to position your cursor and drag to select text. It is not a brand-new release, it has been available since Claude Code v2.1.89, most people just never flipped it on.

If you use Claude Code in the terminal, there is a good chance you have been fighting it without realizing there was a setting that fixes the two most annoying things about it. This is that setting.

The two annoyances that made the terminal feel like a black box

The terminal is one of the most powerful places to use Claude Code. You stay in one window, you keep full context, and you move at the speed of typing. But the classic renderer had two real problems.

First, the flicker. On long sessions the whole screen would clear and redraw on every update. ANSI escape codes have no way to repaint only the rows that changed, so each update forced a full-screen clear. That is the flicker, and on a long conversation it is exhausting.

Second, and worse, you could not click your cursor into the middle of your text. If you pasted a big block, or you use voice-to-text like a lot of people now do, editing it meant holding backspace and waiting. There was no clicking into the middle to fix one word. That single limitation is what made the terminal feel clumsy compared to a full editor.

The fix: fullscreen rendering (no-flicker mode)

Anthropic’s engineers built an alternate rendering path for the Claude Code CLI. Instead of redrawing into your scrollback, fullscreen rendering draws the interface on the terminal’s alternate screen buffer, the same approach vim and htop use. The input box stays pinned to the bottom, and only the messages currently on screen get rendered.

That one architectural change does two things at once:

• The flicker disappears, and CPU and memory stay flat no matter how long the conversation runs.
• Mouse support turns on.

How to turn it on

Enabling it takes one command.

1. Make sure you are on Claude Code v2.1.89 or later. If you are not sure, update.
2. Confirm your terminal supports mouse reporting. Most modern terminals do by default. In iTerm2 you may need to enable mouse reporting in Settings, Profiles, Terminal.
3. Inside Claude Code, type /tui fullscreen and hit enter.

That is it. To switch back at any time, type /tui default.

On older versions, before v2.1.110, there is no /tui command. In that case, set the environment variable CLAUDE_CODE_NO_FLICKER=1 before you launch Claude Code.

What you actually unlock

Once fullscreen rendering is on, the terminal starts behaving like a real editor:

• Click anywhere in the input box to position your cursor instantly.
• Drag to select any block of text. Double-click a word, triple-click a line.
• Click collapsed tool results to expand them, and click URLs and file paths directly.
• No flicker on long sessions, with flat CPU and memory.
• Smooth mouse-wheel scrolling through the conversation.

The editing friction is the headline. The first time you click into the middle of a prompt and fix one word instead of deleting the last fifty characters, the terminal stops feeling like a downgrade from your IDE.

Why this matters most if you are new to vibe coding

If you are just getting into building with AI, the terminal can feel intimidating. It looks like a black box. The flicker and the inability to edit your own text make that worse, and a lot of beginners bounce straight to a heavier IDE because of it.

Turning on fullscreen rendering removes most of that friction. You get the power of working directly with Claude Code, without the part that made it feel hard. For a beginner, this is genuinely one of the most important settings to flip on early, because it changes whether the terminal feels like something you fight or something you flow with.

Honest caveats

A few things worth knowing before you commit to it:

• It is officially a research preview, so behavior may change between versions.
• Native Cmd+F search is replaced. Use Ctrl+O then / to search the transcript.
• Over SSH or inside tmux, the mouse capture can interfere with your native copy-paste. If that happens, set CLAUDE_CODE_DISABLE_MOUSE=1 to keep the no-flicker rendering while dropping the mouse features.
• If you do not like it, /tui default puts you right back.

FAQ

Is this a new update that just launched? No. Fullscreen rendering is an opt-in research preview that has been available since Claude Code v2.1.89 and refined across many releases since. Most people simply never turned it on.

What is the exact command? /tui fullscreen on current versions. CLAUDE_CODE_NO_FLICKER=1 as an environment variable on versions before v2.1.110.

Do I need a special terminal? You need a terminal that supports mouse reporting, which most modern terminals do. iTerm2 may need it enabled in settings.

Can I turn it off? Yes, /tui default switches back to the classic renderer instantly.

Bottom line

Fullscreen rendering is the rare setting that takes one command and meaningfully changes how it feels to work. It kills the flicker, it gives you a mouse, and it turns the terminal from an annoying black box into the most powerful place to use Claude. You probably already have it. Go turn it on.