{ "@context": "https://schema.org", "@id": "https://aggr.aymericbeaumet.com/items/steipete-me/2025-12-18-the-signature-flicker/#webpage", "@type": [ "WebPage", "ArchiveComponent" ], "articleBody": "**tl;dr: Hell froze over. Anthropic fixed Claude Code’s signature flicker in their latest update (2.0.72)**\n\n![Claude Code flickering](https://steipete.me/assets/img/2025/signature-flicker/claude-flicker.gif)\n\nIf there’s one thing everybody noticed about Claude Code (apart from it revolutionizing how we build software), [it’s the flickering](https://www.reddit.com/r/ClaudeAI/comments/1lxs53r/what_is_this_madness/). It’s unfair to point to Anthropic since they are not alone: other TUIs such as Cursor, or really anything based on [Ink](https://github.com/vadimdemedes/ink) have the same issue. It’s also not an easy problem at all. Claude Code uses React under the hood.[^1]\n\n## The Issue\n\nTerminals haven’t really been designed for interactivity. It’s possible to use [ANSI escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code) to reposition the cursor and write over existing text, but that easily leads to flickering if not done well.\n\nThere are two ways to solve this:\n\n1. Switch to [alt mode](https://ratatui.rs/concepts/backends/alternate-screen/#:~:text=The%20alternate%20screen%20is%20a,content%20of%20the%20main%20screen.) and take complete control over the terminal viewport.\n2. Carefully re-render changed parts while leaving the scrollback unchanged.\n\nNeither option is great, and each comes with tradeoffs. [Mario Zechner explains these really well](https://mariozechner.at/posts/2025-11-30-pi-coding-agent/#toc_6) in his write-up on building pi-coding-agent, so I won’t repeat the details here. I’ve spent time with option 2 myself, having ported [pi-tui](https://github.com/badlogic/pi-mono/tree/main/packages/tui) to Swift as [TauTUI](https://github.com/steipete/TauTUI) (Codex did most of the auto-translation).\n\nFor a coding agent that mostly emits text with limited interactivity, I believe carefully re-rendering only changed parts — while remaining a good terminal citizen — is the better approach.\n\nAnthropic seems to agree. Ink, the React-based terminal renderer Claude Code originally used, didn’t support the kind of fine-grained incremental updates needed for a long-running interactive UI. [This has since improved upstream](https://github.com/vadimdemedes/ink/pull/781), but Anthropic needed tighter control, so they [rewrote the renderer from scratch](https://github.com/anthropics/claude-code/issues/769#issuecomment-3667315590) — while still keeping React as the component model.\n\n> This is kind of like if a website were to do their own text rendering, highlighting, mouse movement, context menu, etc. — it would not feel like your browser. (…) We value this native experience a lot. We may explore alternate screen mode in the future, but our bar is quite high. — [Thariq](https://x.com/trq212/status/2001552877698056370), Anthropic\n\n## The Landscape\n\nOver the last year, most new coding agents have converged on alt-screen TUIs — often after fighting flicker — but the results haven’t been great. So what’s my big gripe with alt mode? It breaks features such as text selection, [native scrolling](https://x.com/mitchellh/status/1978934533170041118) or [search](https://x.com/mitchellh/status/1993728538344906978). Of course this can be implemented in the TUI, but it won’t feel *right*.\n\n### Amp\n\nAmp used Ink and shared Claude’s flickering but [eventually wrote their own renderer, switching to alt mode in September](https://ampcode.com/news/look-ma-no-flicker).\n\n![amp find demo](https://steipete.me/assets/img/2025/signature-flicker/amp-find.gif)\n\n- `find` fails unless the text is currently on-screen\n- No native-feeling selection/context menu flow\n- Custom scrollbar; workable but not quite the terminal\n\n### Gemini\n\nGoogle [did a big announcement on their blog](https://developers.googleblog.com/en/making-the-terminal-beautiful-one-pixel-at-a-time/) about their new alt-mode TUI, only to learn that users hate it and then [rolled it back not even a week later](https://github.com/google-gemini/gemini-cli/discussions/13633). In the new TUI, [you have to press CTRL-S to enter selection mode to copy text](https://github.com/google-gemini/gemini-cli/discussions/13067).\n\n![gemini text selection demo](https://steipete.me/assets/img/2025/signature-flicker/gemini-textselect.gif)\n\n### OpenCode\n\nOpenCode did some great engineering and built [opentui](https://github.com/sst/opentui) in TypeScript and Zig, which renders SolidJS or React. It’s not without downsides, e.g. [it doesn’t work in the standard macOS Terminal](https://github.com/sst/opencode/issues/4043#issuecomment-3519627447) for anything below macOS 26 or [GNOME’s Terminal](https://github.com/sst/opencode/issues/4320).\n\n![opencode text demo](https://steipete.me/assets/img/2025/signature-flicker/opencode-text.gif)\n\n- Auto-scroll near the viewport border makes small screens painful\n- No scrollbar; search doesn’t work the way you expect\n- Right click → paste into the input box doesn’t work\n\n### Codex\n\nCompare to OpenAI’s Codex, which stays in the primary screen buffer and lets me interact with text just like I expect:\n\n![codex real demo](https://steipete.me/assets/img/2025/signature-flicker/codex-real.gif)\n\nCodex isn’t perfect — it sometimes overwrites lines of text — but it already nails the part that matters most: it behaves like a terminal. That makes [their current direction toward an alt-mode TUI](https://github.com/openai/codex/blob/main/codex-rs/tui2/docs/tui_viewport_and_history.md) feel like a regression, not an upgrade. Here’s hoping they reverse course.\n\n### pi\n\nMario Zechner’s [pi](https://shittycodingagent.ai/) is currently the gold-standard for differential rendering, while also using all tricks of modern terminals — including showing inline images:\n\n![pi demo](https://steipete.me/assets/img/2025/signature-flicker/pi-demo.gif)\n\n## Verdict\n\nClaude Code and [pi](https://shittycodingagent.ai/) prove you can kill flicker without giving up the terminal’s muscle memory.\n\nAlt mode can be great for dashboards. For coding agents, though, I want the terminal’s built-ins to stay *native*:\n\n- Select text like it’s a terminal\n- Scrollback like it’s a terminal\n- Search like it’s a terminal\n\nIt’s 2025. We can have smooth rendering *and* keep the terminal’s superpowers.\n\n[^1]: Yes, I made the same weird look when I first learned about this, but it’s kinda beautiful. React’s concepts are flexible enough that it doesn’t require a browser as a frontend — and Ink is such an alternative render backend.\n", "authors": [], "captured_at": "2026-09-27T19:29:15.293681927+00:00", "category": "programming", "content_html": "

tl;dr: Hell froze over. Anthropic fixed Claude Code’s signature flicker in their latest update (2.0.72)

\n

\"Claude

\n

If there’s one thing everybody noticed about Claude Code (apart from it revolutionizing how we build software), it’s the flickering. It’s unfair to point to Anthropic since they are not alone: other TUIs such as Cursor, or really anything based on Ink have the same issue. It’s also not an easy problem at all. Claude Code uses React under the hood.1

\n

The Issue

\n

Terminals haven’t really been designed for interactivity. It’s possible to use ANSI escape codes to reposition the cursor and write over existing text, but that easily leads to flickering if not done well.

\n

There are two ways to solve this:

\n
    \n
  1. Switch to alt mode and take complete control over the terminal viewport.
    2. \n
  2. Carefully re-render changed parts while leaving the scrollback unchanged.
    3. \n
\n

Neither option is great, and each comes with tradeoffs. Mario Zechner explains these really well in his write-up on building pi-coding-agent, so I won’t repeat the details here. I’ve spent time with option 2 myself, having ported pi-tui to Swift as TauTUI (Codex did most of the auto-translation).

\n

For a coding agent that mostly emits text with limited interactivity, I believe carefully re-rendering only changed parts — while remaining a good terminal citizen — is the better approach.

\n

Anthropic seems to agree. Ink, the React-based terminal renderer Claude Code originally used, didn’t support the kind of fine-grained incremental updates needed for a long-running interactive UI. This has since improved upstream, but Anthropic needed tighter control, so they rewrote the renderer from scratch — while still keeping React as the component model.

\n
\n

This is kind of like if a website were to do their own text rendering, highlighting, mouse movement, context menu, etc. — it would not feel like your browser. (…) We value this native experience a lot. We may explore alternate screen mode in the future, but our bar is quite high. — Thariq, Anthropic

\n
\n

The Landscape

\n

Over the last year, most new coding agents have converged on alt-screen TUIs — often after fighting flicker — but the results haven’t been great. So what’s my big gripe with alt mode? It breaks features such as text selection, native scrolling or search. Of course this can be implemented in the TUI, but it won’t feel right.

\n

Amp

\n

Amp used Ink and shared Claude’s flickering but eventually wrote their own renderer, switching to alt mode in September.

\n

\"amp

\n\n

Gemini

\n

Google did a big announcement on their blog about their new alt-mode TUI, only to learn that users hate it and then rolled it back not even a week later. In the new TUI, you have to press CTRL-S to enter selection mode to copy text.

\n

\"gemini

\n

OpenCode

\n

OpenCode did some great engineering and built opentui in TypeScript and Zig, which renders SolidJS or React. It’s not without downsides, e.g. it doesn’t work in the standard macOS Terminal for anything below macOS 26 or GNOME’s Terminal.

\n

\"opencode

\n\n

Codex

\n

Compare to OpenAI’s Codex, which stays in the primary screen buffer and lets me interact with text just like I expect:

\n

\"codex

\n

Codex isn’t perfect — it sometimes overwrites lines of text — but it already nails the part that matters most: it behaves like a terminal. That makes their current direction toward an alt-mode TUI feel like a regression, not an upgrade. Here’s hoping they reverse course.

\n

pi

\n

Mario Zechner’s pi is currently the gold-standard for differential rendering, while also using all tricks of modern terminals — including showing inline images:

\n

\"pi

\n

Verdict

\n

Claude Code and pi prove you can kill flicker without giving up the terminal’s muscle memory.

\n

Alt mode can be great for dashboards. For coding agents, though, I want the terminal’s built-ins to stay native:

\n\n

It’s 2025. We can have smooth rendering and keep the terminal’s superpowers.

\n
\n
    \n
  1. \n

    Yes, I made the same weird look when I first learned about this, but it’s kinda beautiful. React’s concepts are flexible enough that it doesn’t require a browser as a frontend — and Ink is such an alternative render backend. ↩

    \n
    2. \n
\n
\n", "content_markdown": "**tl;dr: Hell froze over. Anthropic fixed Claude Code’s signature flicker in their latest update (2.0.72)**\n\n![Claude Code flickering](https://steipete.me/assets/img/2025/signature-flicker/claude-flicker.gif)\n\nIf there’s one thing everybody noticed about Claude Code (apart from it revolutionizing how we build software), [it’s the flickering](https://www.reddit.com/r/ClaudeAI/comments/1lxs53r/what_is_this_madness/). It’s unfair to point to Anthropic since they are not alone: other TUIs such as Cursor, or really anything based on [Ink](https://github.com/vadimdemedes/ink) have the same issue. It’s also not an easy problem at all. Claude Code uses React under the hood.[^1]\n\n## The Issue\n\nTerminals haven’t really been designed for interactivity. It’s possible to use [ANSI escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code) to reposition the cursor and write over existing text, but that easily leads to flickering if not done well.\n\nThere are two ways to solve this:\n\n1. Switch to [alt mode](https://ratatui.rs/concepts/backends/alternate-screen/#:~:text=The%20alternate%20screen%20is%20a,content%20of%20the%20main%20screen.) and take complete control over the terminal viewport.\n2. Carefully re-render changed parts while leaving the scrollback unchanged.\n\nNeither option is great, and each comes with tradeoffs. [Mario Zechner explains these really well](https://mariozechner.at/posts/2025-11-30-pi-coding-agent/#toc_6) in his write-up on building pi-coding-agent, so I won’t repeat the details here. I’ve spent time with option 2 myself, having ported [pi-tui](https://github.com/badlogic/pi-mono/tree/main/packages/tui) to Swift as [TauTUI](https://github.com/steipete/TauTUI) (Codex did most of the auto-translation).\n\nFor a coding agent that mostly emits text with limited interactivity, I believe carefully re-rendering only changed parts — while remaining a good terminal citizen — is the better approach.\n\nAnthropic seems to agree. Ink, the React-based terminal renderer Claude Code originally used, didn’t support the kind of fine-grained incremental updates needed for a long-running interactive UI. [This has since improved upstream](https://github.com/vadimdemedes/ink/pull/781), but Anthropic needed tighter control, so they [rewrote the renderer from scratch](https://github.com/anthropics/claude-code/issues/769#issuecomment-3667315590) — while still keeping React as the component model.\n\n> This is kind of like if a website were to do their own text rendering, highlighting, mouse movement, context menu, etc. — it would not feel like your browser. (…) We value this native experience a lot. We may explore alternate screen mode in the future, but our bar is quite high. — [Thariq](https://x.com/trq212/status/2001552877698056370), Anthropic\n\n## The Landscape\n\nOver the last year, most new coding agents have converged on alt-screen TUIs — often after fighting flicker — but the results haven’t been great. So what’s my big gripe with alt mode? It breaks features such as text selection, [native scrolling](https://x.com/mitchellh/status/1978934533170041118) or [search](https://x.com/mitchellh/status/1993728538344906978). Of course this can be implemented in the TUI, but it won’t feel *right*.\n\n### Amp\n\nAmp used Ink and shared Claude’s flickering but [eventually wrote their own renderer, switching to alt mode in September](https://ampcode.com/news/look-ma-no-flicker).\n\n![amp find demo](https://steipete.me/assets/img/2025/signature-flicker/amp-find.gif)\n\n- `find` fails unless the text is currently on-screen\n- No native-feeling selection/context menu flow\n- Custom scrollbar; workable but not quite the terminal\n\n### Gemini\n\nGoogle [did a big announcement on their blog](https://developers.googleblog.com/en/making-the-terminal-beautiful-one-pixel-at-a-time/) about their new alt-mode TUI, only to learn that users hate it and then [rolled it back not even a week later](https://github.com/google-gemini/gemini-cli/discussions/13633). In the new TUI, [you have to press CTRL-S to enter selection mode to copy text](https://github.com/google-gemini/gemini-cli/discussions/13067).\n\n![gemini text selection demo](https://steipete.me/assets/img/2025/signature-flicker/gemini-textselect.gif)\n\n### OpenCode\n\nOpenCode did some great engineering and built [opentui](https://github.com/sst/opentui) in TypeScript and Zig, which renders SolidJS or React. It’s not without downsides, e.g. [it doesn’t work in the standard macOS Terminal](https://github.com/sst/opencode/issues/4043#issuecomment-3519627447) for anything below macOS 26 or [GNOME’s Terminal](https://github.com/sst/opencode/issues/4320).\n\n![opencode text demo](https://steipete.me/assets/img/2025/signature-flicker/opencode-text.gif)\n\n- Auto-scroll near the viewport border makes small screens painful\n- No scrollbar; search doesn’t work the way you expect\n- Right click → paste into the input box doesn’t work\n\n### Codex\n\nCompare to OpenAI’s Codex, which stays in the primary screen buffer and lets me interact with text just like I expect:\n\n![codex real demo](https://steipete.me/assets/img/2025/signature-flicker/codex-real.gif)\n\nCodex isn’t perfect — it sometimes overwrites lines of text — but it already nails the part that matters most: it behaves like a terminal. That makes [their current direction toward an alt-mode TUI](https://github.com/openai/codex/blob/main/codex-rs/tui2/docs/tui_viewport_and_history.md) feel like a regression, not an upgrade. Here’s hoping they reverse course.\n\n### pi\n\nMario Zechner’s [pi](https://shittycodingagent.ai/) is currently the gold-standard for differential rendering, while also using all tricks of modern terminals — including showing inline images:\n\n![pi demo](https://steipete.me/assets/img/2025/signature-flicker/pi-demo.gif)\n\n## Verdict\n\nClaude Code and [pi](https://shittycodingagent.ai/) prove you can kill flicker without giving up the terminal’s muscle memory.\n\nAlt mode can be great for dashboards. For coding agents, though, I want the terminal’s built-ins to stay *native*:\n\n- Select text like it’s a terminal\n- Scrollback like it’s a terminal\n- Search like it’s a terminal\n\nIt’s 2025. We can have smooth rendering *and* keep the terminal’s superpowers.\n\n[^1]: Yes, I made the same weird look when I first learned about this, but it’s kinda beautiful. React’s concepts are flexible enough that it doesn’t require a browser as a frontend — and Ink is such an alternative render backend.\n", "dateCreated": "2026-09-27T19:29:15.293681927+00:00", "date_created": "2025-12-18T00:00:00+00:00", "date_modified": "2025-12-18T00:00:00+00:00", "date_published": "2025-12-18T00:00:00+00:00", "description": "Hell froze over. Anthropic fixed Claude Code's signature flicker in their latest update (2.0.72)", "external_url": "https://steipete.me/posts/2025/signature-flicker/", "git": { "commit": "ebb0941c5c06a2ab2377342d607535262a3e969e", "path": "items/steipete-me/2025/12/2025-12-18-the-signature-flicker.md", "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/ebb0941c5c06a2ab2377342d607535262a3e969e/items/steipete-me/2025/12/2025-12-18-the-signature-flicker.md" }, "id": "urn:aggr:item:ca212a0cd1814e553bd8c038a354da6c128e57d2", "isBasedOn": { "@id": "https://steipete.me/posts/2025/signature-flicker/" }, "mainEntity": { "@id": "https://steipete.me/posts/2025/signature-flicker/", "@type": "CreativeWork", "archivedAt": { "@id": "https://aggr.aymericbeaumet.com/items/steipete-me/2025-12-18-the-signature-flicker/#webpage" }, "dateModified": "2025-12-18T00:00:00+00:00", "datePublished": "2025-12-18T00:00:00+00:00", "headline": "The Signature Flicker", "timeRequired": "PT4M", "url": "https://steipete.me/posts/2025/signature-flicker/", "wordCount": 745 }, "name": "Archived snapshot: The Signature Flicker", "preview": null, "reading_minutes": 4, "replicated_at": null, "source": "steipete-me", "source_name": "Peter Steinberger", "summary": "Hell froze over. Anthropic fixed Claude Code's signature flicker in their latest update (2.0.72)", "tags": [], "temporalCoverage": "2026-09-27T19:29:15.293681927+00:00", "title": "The Signature Flicker", "url": "https://aggr.aymericbeaumet.com/items/steipete-me/2025-12-18-the-signature-flicker/", "word_count": 745 }