Sorry folks, this is a rollout artifact, we needed a way to turn this off remotely via feature flags if it broke something, and with telemetry off you don't get those. It's already been fixed as part of v2.1.281 releasing today.
The mod is source available here: https://github.com/anthropics/claude-code/tree/main/mods/age...
Apologies again folks, this was a fully human error on my part - I should've found a better way to launch with a kill-switch.
So what Anthropic calls "telemetry" is really "telechangeability"? That's sits with me even less comfortably than did the idea that some features are only available with telemetry enabled.
>Apologies again folks, this was a fully human error on my part
Blink twice if you need help
Much respect for the prompt response, humility, and frank disclosure.
Ouch.
I've had to send such messages, but internally at work, not on HN!
Have a great day, human.
Hey, it seems you work there. I had a tangential question. Did any Anthropic exec threaten to do something unsavoury if any engineer ever tried to not name the claude cli binary as the version number itself? Because if they did, I'd understand. Or if you dare change it all the vibe-coded ts/react/etc dominoes will go for a fall in unison? I'd understand that too.
Thanks for admitting to the mistake, but my understanding was that coding was fully solved now?
I can understand honest mistakes, but like, usually when I develop anything with agents (which I assume is what you're doing internally at Anthropic), they're almost too enthusiastic about trying to add test cases to the point where they sometimes try to glue together things in ways that are structurally impossible in the actual code in order to try to test that behavior. I'm honestly a bit mystified that adding a new feature didn't get bundled in with tests that the feature works for arbitrary configurations.
Really loved this Tibo-level responsiveness, if Anthropic can keep it up with this level of service, I am pretty sure a lot of people will just ditch their ChatGPT subscription and just move to Claude.
> a fully human error
Would be interesting to know how much time you/your team spent on that design decision
The same guy writing readme's for my vibeslopped toy projects is also the readme writer at Anthropic, what a coincidence ;)
> Sorry folks, this is a rollout artifact
Aka: "an issue even a junior would've spotted if we didn't rely on Claude of 100% of our tasks"
It was obvious this was the reason, it’s a very easy thing to forget about
is there reason I can't update claude to 2.1.281? I just run claude update
> claude update Current version: 2.1.280 Checking for updates to latest version... Claude Code is up to date (2.1.280)
I hope disabling /r if telemetry is disabled is also unintentional...
How are you planning to turn this off remotely when telemetry off?
is it common to deploy software with a remote kill switch installed?
Well now, this is how you do community outreach
people are overeacting
telling people Anthropic remote-control their users computers isn't the smartest thing to do
I don't understand, isn't coding solved already?
"Rollout artifact"? This is Claude-speak isn't it? I have never ever heard anyone call a bug like this a "rollout artifact" before.
The AGENTS.md support was implemented via our new extensibility system for CC, called Mods, which is launching soon-ish. A mod is a plugin with a new type of hook, which we call a function hook.
If folks play around with it, I would love feedback on the relevant issue: https://github.com/anthropics/claude-code/issues/91870
Mods allow quite a bit more customizability and control. I really believe in the idea.