The Signature Flicker

Claude kills the flicker; commenters feud over “just make a normal app” vs terminal purists

TLDR: Anthropic’s Claude Code update 2.0.72 finally stops the notorious flicker while keeping familiar terminal behavior. Comments split: fans cheer the native feel, critics say they should’ve gone full-screen or just build a normal app, with extra snark about unexplained acronyms—proof that the UI wars never end.

Hell froze over: Claude Code’s infamous screen flicker is gone. Anthropic’s update (2.0.72) quietly rewrote its text renderer so the app behaves like a normal terminal, letting you scroll, select, and search without weird full-screen tricks. The cheers? Loud. The drama? Even louder. One camp is thrilled that Anthropic avoided “alt mode,” the full-screen approach many tools use that breaks familiar actions like copy/paste. They’re calling this a win for developer muscle memory and common sense. But the hot takes are on fire. A skeptical crowd argues Anthropic should’ve switched to alt mode ages ago, calling the post “aged like milk” after other companies tried full-screen UIs, got roasted, and rolled them back. Another chorus says, forget terminals—just make a regular GUI people can click, drag, and close without arcane key combos. And then there’s the acronym police, scolding writers for tossing around “TUI” (text-based user interface) without explaining it. Memes flew: “My terminal stopped doing nightclub strobe,” “CTRL-S to copy? Hard pass,” and “If it flickers, it’s a feature.” Meanwhile, shout-outs rolled in for Mario Zechner’s “pi” as the gold standard for smooth text updates, while Amp and OpenCode were cited as cautionary tales of full-screen weirdness. Verdict: flicker’s dead, debate lives.

Key Points

  • Anthropic’s Claude Code 2.0.72 update resolves terminal flickering by adopting a custom React-based incremental renderer.
  • The article contrasts alt-screen mode with differential rendering, favoring re-rendering only changed parts in the primary buffer.
  • Ink initially used by Claude Code lacked fine-grained updates for long-running UIs; Anthropic rebuilt the renderer for tighter control.
  • Other coding agents have embraced alt-mode with tradeoffs: Amp switched and faced non-native UX elements; Google rolled back an alt-mode TUI after user feedback.
  • OpenAI’s Codex remains in the primary screen buffer, preserving native terminal interactions; Mario Zechner’s pi is highlighted as a leading example of differential rendering.

Hottest takes

"Why do TUI developers insist on doing such weird stuff when they could just make a GUI" — spencerchubb
"This post has aged like milk given the rollback" — CSSer
"Don’t write articles with uncommon acronyms ("TUI")" — cubefox
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.