1) everyone on the team uses Claude code differently.
2) Claude Code has been around for almost a year and is being built by an entire team, yet doesn't seem to have benefited from this approach. The program is becoming buggier and less reliable over time, and development speed seems indistinguishable from anything else.
3) Everything this person says should be taken with a massive grain of salt considering their various conflicts of interest.
Exactly, he has to dogfood it. He can't just say "actually this is a massively annoying way of developing software and probably slows me down".
This "outside of VSCode", was it still with a webview-based terminal?
That being said, this isn't a huge issue for CC - you can just use the extension, which offers a similar experience.
It's the worst experience in tmux! They lectured us about how the roots of the problem go deep, but I don't have this issue with any other CLI agent tool like Codex.
https://x.com/trq212/status/2001439019713073626
I don't have that problem using it on iTerm2 however. I also don't use Tmux with it.
Edit: for a while I thought this was by design since it was a very visceral / graphical way to feel that you're hitting the edge of context and should probably end the session.
If I get to the flicker point I generally start a new session. The flicker point always happens though from what I have observed.
Normally I would cut them some slack but it doesn’t really make sense, couldn’t someone kick off a PR today and get it done?
Not my experience at all (macOS Tahoe/iTerm2, no tmux).
Speaking of either Claude Code as a tool, or Claude 4.5 as an LLM used with coding.
You know, this bugs me out. Claude code, macOS, Windows... they're all becoming buggy, filled with papercuts everywhere... and this coincided with layoffs + mass adoption of LLM coding tools and services.
Shhh, this is not what you’re supposed to look at.
Look! Bazillion more agents! Gorrilion more agents! Productivity! Fire those lazy code monkeys, buy our product! Make me riiiich.