Most people's mental model of Claude Code is that "it's just a TUI" but it should really be closer to "a small game engine". For each frame our pipeline constructs a scene graph with React then -> layouts elements -> rasterizes them to a 2d screen -> diffs that against the previous

While we test Claude Code rigorously, our users run Claude in a huge combination of terminal and operating system setups. Here we found that in some setups we were triggering Garbage Collection too often in our rendering pipeline. Somethings you can't find until you ship.

This was a legacy migration, we had to port our entire rendering engine while making sure nothing user-facing broke. Doing this without Claude Code could have taken on the order of 1-2 years for a single engineer, something we would have never been able to prioritize.

It was feature flagged, I made the call to not advertise it because it was the holidays and we wouldn't be able to support as much. But maybe should have shared it.

Wanted to clarify this 1-2 years thing. Of course this was just a back of the envelope estimate, it's entirely possible it's wrong. And Claude Code itself is like a year old, so how could this take longer? As a team and company grows, your codebase moves under you more often,

Tons of ways to interact with Claude Code right now if you prefer not CLI, I like the desktop for example.

the native Claude installer uses Bun!