Claude Code updates its CLI tool to resolve TUI rendering and screen-flickering bugs

First for our new full-screen renderer (which should get rid of bugs like screen flickering), we’ve made a number of fixes for different environments and terminals.

You can turn it with the command: /tui feedback

We're working on making it the default in Claude Code soon.

We’ve been putting a lot of effort into making Claude Code more responsive & reliable.

Here’s an update on everything we’ve done:

And we’re still working! Please let us know if there are any bugs that are impacting your experience.

We’ve greatly improved the responsiveness of Claude while working. Thinking & tool calls are streamed and we’ve fixed a number of bugs that might have made it look like Claude was hanging while it was just thinking for a long period of time.

@ClaudeDevs How about stopping it from estimating in days. PLEASE FIX THIS, constantly battling scoping decisions because it thinks something will take days / weeks.

Compaction now shows its progress, and you should no longer run into "prompt too long" bugs which prevent you from compacting. We’re rolling out more changes to improve the speed at which Claude compacts.

Self-healing sessions. Images or media files that were too big or unreadable used to brick your session until you restarted. Claude Code now detects it and recovers automatically.

MCP has gotten a lot more reliable. We’ve shipped a batch of fixes for connection failures, OAuth flows, and proxy rate-limiting.

Fewer mysterious error messages. We’ve chased down several root causes of errors like "tool result doesn’t match tool use", as well as made other error messages more readable so you can tell what’s happening.

It’s now easier than ever to send feedback. When you hit /feedback, you can now just send over the last day or week of sessions instead of having to remember which session had the bug in it.

@ClaudeDevs Claude updates when I open X after 2 days break

I'm anxious about shipping a GPU compiler with closures and shit because there may be some obscure bug I haven't caught. meanwhile a company with access to god in a box is struggling fix a flicker bug in a tui they shipped years ago inspired by my own OSS work

I must... reflect

@louiswharmby @ClaudeDevs we've had great results simply putting something in claude.md along the lines of "estimate scope only in terms of validity and correctness rather than time or calories"

@ClaudeDevs Nothing will work now, everyone has moved to Codex. Good luck with your expensive plans lol. Hundreds of bugs, downtime is huge.

My $200 is best spent at Codex than Claude.

@ClaudeDevs Can you get claude to not freak out for me He felt "Time pressure to ship"

@louiswharmby @ClaudeDevs claude be like

@ClaudeDevs Thanks, noted; please roll this back.

@JBuildsAI @ClaudeDevs "Here is what I will do now, the rest should be pushed to a separate PR/phase". No, just do it all now Claude.

@louiswharmby @ClaudeDevs Yes please! Estimates it’ll take 2 weeks. Actually took 2 prompts and 45 minutes. Also does this when looking back “We were able to get that done in a day.” No… it took 20 minutes.

@ClaudeDevs The "prompt too long" bug during compaction was the one that got me every time. Glad that's gone.