rrwright

I agree with what I think you meant: it is not a bug in Claude. However "javascript on the backend" is exactly what Claude Code is! It's a node.js implementation of automation components that feed and pull from the Claude model.

I have a VERY hard time believing that they only use JSON serialization between the model and the TUI. If they're seriealizing JSON between agents, tools, or other components, then this problem is going to continue to persist for a very long time.

This symptom was affecting display of numbers in the TUI, but the real bug/design flaw is using jq or JSON as a transport mechanism between components or between tools. JSON's number range is famously poor and it even architecture-dependent. So if you use jq or JSON to connect components or tools, you will have this same problem silently occurring elsewhere without visibility in the UI.

This is a bigger deal than it seems like! A confidence-inducing fix would include a blog post describing a top-to-bottom audit of jq/JSON used as a transport layer between tools and components. Not just a patch to the most visible problem.

Good catch on the guidelines. But that github issue title obviously misses the point. The whole point is that it's a silent error in Claude Code.

Try it yourself: `echo '348555896224571969'`

This question sounds like it was asked by a private equity investor looking to sample the tech zeitgeist before buying up and destroying some beloved tool.

Completely agree. I had to turn on iOS reader mode to tolerate it. But then it was very worthwhile.

+1 to this.

That book has a few sections describing policy arguments on the floor of the New York Senate which are so well written that they are absolutely riveting! It sounds ridiculous to say that political arguments (from 100+ years ago) could keep you on the edge of your seat, but they do. It’s why this book the Pulitzer Prize.

The irony of that advice from a user with that username is comedic gold! Thank you for that. It made my day.