Why has public comms been so poor on this issue? There's been lots of Github issues posted in the Claude Code repo with lots of new comments each day screaming into the void, but radio silence from Anthropic since the revert in December. It's clearly causing a lot of frustration for users leading to clever workarounds like this.

It was obviously a complex issue (I appreciate that and your work!). But I think there's a lot to be improved on with communication. This issue in particular seems like it has lost a lot of user trust - not because it was hard to solve and took awhile - but because the comms and progress around it was so limited.

Eg issues:

* https://github.com/anthropics/claude-code/issues/1913

* https://github.com/anthropics/claude-code/issues/826

* https://github.com/anthropics/claude-code/issues/3648

On the Ghostty recommendation, read this first - https://mitchellh.com/writing/ghostty-memory-leak-fix

> A few months ago, users started reporting that Ghostty was consuming absurd amounts of memory, with one user reporting 37 GB after 10 days of uptime.

> ...

> The leak was present since at least Ghostty 1.0, but it is only recently that popular CLI applications (particularly Claude Code) started producing the correct conditions to trigger it at scale. The limited conditions that triggered the leak are what made it particularly tricky to diagnose.

> The fix is merged and is available in tip/nightly releases, and will be part of the tagged 1.3 release in March.

Have you guys seriously considered decoupling the TUI / UI so anyone can write their own on top of Claude Code proper? I love how Zed did it, but its not always the most stable experience, but it is definitely better than staring at a TUI.

Thanks for the update!

While I have you on the line, I'm also experiencing tons of API request timeouts using Claude Code's own TUI client (on the $200/mo plan!!) and I don't know how to mitigate that, and it is frustrating

I'm not even using it particularly hard. Usually only one agent is running with possibly one sub-agent on occasion. Which is confusing because I've heard of people running ten at once and only then running into this issue...

Possibly related, I DID only upgrade to the $200 tier a few days ago... might there be a now-stale API rate limit in place?? Or maybe it's the long-running multi-compacted context that's the problem?

My account is tied to lumbergh-at-gmail-dot-com

I'm a dev so of course, happy to help run it down from my end

This tool is amazing btw. I'm currently working on a never-existed-before app that would have been impossible before AI... And it's going quite well

> differential rendering

Now where have I seen that before.

> and only ~1/3 of sessions see at least a flicker

Sounds like only is a bit misplaced. IMHO such bugs that take forever to fix make Anthropic seem very unprofessional.

I wonder how much of Claude Code is developed using Claude?

Can you guys give this some love? https://github.com/anthropics/claude-code/issues/769

I had to use Codex today cause claude kept scrolling up every time the window lost focus. It was so annoying. macOS iTerm

> only ~1/3 of sessions see at least a flicker.

...after many months, for such a visible bug, is such a crazy thing to say.

In case the above comes across as too hostile, to balance this, I would say thank you to the claude code team for such an amazing product!

Seeing massive slowdowns in console interactions today... is there a correlation? Others here at my work are seeing it too!

> The good news: we shipped our differential renderer to everyone today. We rewrote our rendering system from scratch[1] and only ~1/3 of sessions see at least a flicker. Very, very few sessions see flickers in rapid succession which was so annoying before. Those numbers will keep dropping as people update.

I'm using the latest version and see terrible flicker in tmux still. You guys should be ashamed tbh.

i’ve noticed the issue with tmux more than with specific terminals.

basically, the rapid replay of the entire conversation history (the CC bug) somehow interacts destructively with something in tmux, causing it to be 10 times worse. The “flicker” becomes a multi-second delay while I wait twiddling my thumbs…

i’ve seen this in every terminal, including ghostty… as nice as ghostty is, expecting everyone to use it is kinda meh (at least support Wezterm too, lol)

The problem is they are using the Ink library which clears and redraws for each update.

https://github.com/anthropics/claude-code/issues/769

I locally patched the closed-source CLI npm package but it's not perfect. They would have to switch how their TUI is rendered on their side.

Apparently OpenAI Codex is rust+ratatui which does not have this issue.

I have a hypothesis: they haven't fixed this because they're using Claude Code to develop Claude Code. I'm a fan of Claude Code, but it isn't good enough to fix tricky issues like this. And because no one looks at the codebase themselves, they haven't been able to fix it after many months. Sometimes, all we need is an engineer to sit down for the weekend and fix the damn bug, not spin up 9 different Claude Agents prompted to fix itself.

> it’s because they don’t want people to see what a mess their code base is.

if Amodei hadn't said "90% of code will be written by AI", at least I wouldn't call them hypocrites, but the fact that the company that makes such wild claims can't fix a freaking flicker and scroll issue until an indie-dev steps in just shows how far behind their product is from their claims.

I have CC and use many models with it (Codex in CC, try it!), but I won't let Anthropic "lecture" us about how "the roots of the problem go deep". Literally no other CLI tool has these issues: opencode, codex, gemini, droid, etc.

I think its clear the team is drowning. They are just trying to keep their head above water. They have massive adoption, high churn in the underlying models, and unlimited numbers of github issues opened every day.

Should it be solved by now? Yes. If anyone on the team is dogfooding it in a typical tmux environment, its painful. But lets give them some leeway here.

The biggest strength in OpenAI’s codex vs claude code is that it’s written in Rust and smooth as butter

The joke is that AGI will be achieved when Claude Code can fix the flickering in Claude Code.

same, also it uses like 800M of ram... like why?

I wouldn't be able to ship this to anyone without fixing it. Sending 5,000 lines of text to a terminal just to clear them all immediately, and in a loop... i'd be so embarrassed. Apps that clear scrollback have their uses, but you don't spam the terminal with unusable garbage.

And we solved this problem over 30 years ago? Ncurses was made for this. The buffer is kept in memory, you hit page-up and it renders the previous page, page-down and it renders the next page, let it roll and it renders each successive page as a stream, or just the last page, etc.

Imagine the amount of slop PRs if it was open source. They don’t want to taste their own medicine

How does Ghostty break scroll? I've never noticed this and I just tested, seems to work fine. My problem is the lack of a scrollbar but I know they are working on that.

Maybe try tmux? There’s no smooth scrolling, but there’s lots of other bells and whistles I wouldn’t give up for that.

Thank you, that's the primary issue I have too, I'm surprised it's not being talked more here in this thread. I am on iTerm2 in macOS so not specific to your environment. It's really annoying and restarting doesn't fix it in my case, only a fresh session.

I was having this issue with Claude code, and even worse with Gemini, while using the VSCode terminal. I switched to Ghostty and I don't have any flickering or weird scrolling issues at all anymore.

> this got written by Claude Code

nit but CC itself doesn't write anything, much like a body w/o brain doesn't program anything. it's possible the OP was using other models like codex/gemini/etc. in CC.

I was just thinking that half a hour ago when using Claude via tmux via mosh via my phone.

It would be a game changer for mobile usage.

Thanks dang, but they didn't address the issue entirely and the scrolling issue still persists too.

Codex is written in Rust IIRC, probably makes a pretty big difference

Write it in Go!

yeah its like im being hypnotized and im forced to wait until programming is over

I read the other day that one of their devs has a vanilla CC setup that consists of 10 agents running in parallel. Why doesn’t he just ask one of those agents to fix it??

I mentioned this to Claude and this was the response:

Ha! The irony is not lost on anyone.

"We've built the world's most advanced AI coding assistant. It can refactor entire codebases, debug complex issues, and ship production features autonomously. Anyway, here's a terminal bug that makes your screen look like a slot machine. We'll get to it eventually."

Do you also write your bytecode by human hands? At which abstraction layer do we draw the line?

if it works then who cares?

An AI wrote it.

Why?