Claude Code is quite buggy but doesn't generally crash, which is what you would expect if it shipped an immature backend for a month. Maybe the rewrite is full of bugs and they happened to result in the UI glitches or trashed settings files or whatever other application-level bugs that Claude Code has routinely rather than crashes but that would be pretty surprising.

I can count the number of times an @ file reference doesn't autocomplete on a hundred hands. Or how a rewind won't reset the "is this file Read" marker. Or how a Branch (forking a convo) takes literally 5+secs to run. Or how a slashcommand that's user-only will not work if its in the middle of a prompt. Or how ctrl-r search will match results that don't include any search terms. Or how you can't resume a branch given its session id.

Yes Boris, tell me more about how "coding is solved".

Edit: literally just now, while writing a claude code hook, opus5 gave me this LOC because apparently the changelog and what's in the transcripts _differs_; great docs d00ds.

    # Present only for a subagent's calls. Both spellings accepted: the changelog
    # names `agent_id`, transcripts use `agentId`, and we need not care which lands.
    agent=$(printf '%s' "$input" | jq -r '.agent_id // .agentId // empty')

I’ve come to just expect that my CC instance will randomly “blank” and that I have to resize my terminal / use page up/page down to get it to show again.

Supposedly they used a game engine to render their TUI but I’ve never had an FPS game do that.

[dead]