 | |
Claude Code is simultaneously the most useful and lowest quality app I use. It's filled with little errors and annoyances but succeeds despite them. Not to mention the official documentation is entirely vibe-copywritten and any quality control is cursory at best. It forcibly installs itself to ~/.local/bin. Do you already have a file at that location? Not anymore. When typing into the prompt, EACH KEYSTROKE results in the ENTIRE conversation scrollback being cleared and replayed, meaning 1 byte of new data results in kilobytes of data transferred when using Claude over SSH. The tab completion for @-mentioning is so bad it's worthless, and also async, so not even deterministic. You cannot disable their request for feedback. Apparently it lies in tool output. It truly is a testament to the dangers of vibe coding, proudly displayed for everyone to take an example from. |
| | |
Ha, interesting. Using Claude Code in Zed, I never encountered any of these defects. I just open a Claude Code Thread, tell it what I want, bypass permissions (my remote is a container), and let it work. And it works wonderfully! I guess the “integrated” part of IDE is pretty important. |
| | | |
No, I'm not sure about the precise mechanics of it, but I noticed it because of the huge flash when using it over a somewhat laggy SSH connection. It doesn't happy in all contexts. I've definitely seen it when typing into the new-ish Claude "ask questions about the plan" flow, and I've also noticed that it redraws the entire conversation history when each new line of output is presented in a long-running tool call. |
| | |
Smells like floating point. Python prompt: >>> int(float('348555896224571969'))
348555896224571968
It just exceeds the mantissa bits of doubles: >>> math.log2(34855589622457196)
54.952239550875795
JavaScript (in)famously stores all numbers as floating point resulting in silent errors also with user perceived integers, so this might be an indication that Claude Code number handling uses JS native numbers for this. |
| | | | |
I don't think this is a bug specifically with Claude Code, rather it's due to Claude Code having javascript in the backend. The interesting thing to me is that the numeric string was interpreted as an integer. |
| | | |
Looks like mods changed the title to the title of the GitHub Issue. This from HN guidelines is probably why: > Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize. |
| | | |
Claude Code v2.0.37
Haiku 4.5 · Claude Pro > run cmd echo '348555896224571969' I'll run that echo command for you. Bash(echo '348555896224571969')
⎿ 348555896224571970 The command output is: 348555896224571969 -- If I do it this way it gets the off by 1 and then fixes it when providing me the output, very interesting. |
| | |
I forgot which blogpost mentioned it, but to paraphrase it states that managers won’t understand why you can’t just fix a bug like this in a few minutes like you would in traditional software. This might be one of those cases, where the problem arises from the training set somehow. |
| | |
This seems to be a software bug and not something about model behavior, though the model is in some sense doing the wrong thing by internally evaluating what the echo command should output rather than saying what the output actually is. Edit: Based on the above comment showing javascript numerics behavior changing, it's more like some unusual interaction with the numeric string in the bash command being interpreted as an integer and running into precision issues. |
| | | | |
Looks like it has to be the full tool output to be coerced: > Can you run this through bash: echo '348555896224571969 plus 2 is 348555896224571971'
Bash(echo '348555896224571969 plus 2 is 348555896224571971')
⎿ 348555896224571969 plus 2 is 348555896224571971 |
|
|
.png)
2 hours ago
1
