- 52comments
- 117comments
- 5comments
- 2comments
- 779comments
- —discuss
- 1000comments
- 1comments
- —discuss
- 4comments
- 6comments
- 18comments
- 231comments
- 407comments
- 5comments
- 35comments
- 9comments
- 211comments
- 158comments
- 60comments
- 484comments
- 158comments
- 496comments
- 26comments
- 150comments
- 3comments
- 111comments
- 12comments
- 98comments
- 366comments
Crazy part is: can’t tell if this intended or a bug
Can you think of a bug that makes sense in this case?
Vibe coding
It is most certainly the kind of subtle bug the LLMs love to slip in and burn you in production
Not sure what y’all are thinking with these unwritten conspiracy theories that begin and end with “it’s intentional”
Assuming that it's intentional, what's the motivation?
I like to give my graces to people and the companies who are typically not trillions of dollars. Have an incredible amount of resources that many countries would like to have, with fewer of the obligations. I'm going to chalk this up to its intended
Someone on the Claude Code team is probably wondering the same...
Claude/Anthropic has been sus from the start:
https://www.thatprivacyguy.com/blog/anthropic-spyware/
+ not letting users change their email, or remove their payment methods, etc.
many of these can also be chalked up to the fact that all of their products are extremely vibed
I cannot set a password for login, on logging in it says we've sent a login code but it's a link instead...
Vibe-coding at its best.
Nice find, though I'd rather read the prompt that was used to write this article. It is about ten times longer than it needs to and is quite painful to read.
Based on my experience with these tools so far, this seems exactly the kind of subtle but extremely severe bug that sneaks in when you start piling up layers of AI generated patches to a codebase without caring too much about the code.
Yep, especially with long contexts (and moreso if the last thing you were working on in the same context involved telemetry too). AI sneaks in weird conditions like this and then does the entire "You're absolutely right" thing if you're paying enough attention to catch it.
It seems to be exactly the opposite, a "fully human error":
https://news.ycombinator.com/item?id=49815363
Nothing to do with AI patches at all, nor was it a bug. It was intentional human behavior, a temporary rollout setting, that seems to have made sense.
But I guess that doesn't fit the "narrative".
Except that, and this I find slightly amusing, is a situation where they definitely don't want to publicly blame the ai model when there are mistakes.
I used to actively use Msty for local models because it just worked and had a lot of nice advanced features. A few months ago they released their beta version of a Claw-like UI and mentioned using a version of it to develop Msty itself. Well, that was around the time I stopped using Msty because every update started breaking things and two updates in a row included bugs which wiped all my configs, chats, and history.
Issue 95690, opened 3 days ago, 500k+ engineers, a simple CLI...
AGI was reached like 2 weeks ago, latest claude 5.x models rule supreme and oftware engineering is solved?
Isn't that how they just release all features? So they can do progressive roll outs and telemetry on issues with it?
Not sure if they later move the code from inside the flag check to the main code or that they keep the flag check.
But if they would keep all features behind a flag that would not make most sense as you then would have not many features without telemetry.
This is what's written in their release notes for 2.1.277:
My dumb brain tells me none of this is rolled out progressively. You either have it or not.
I use cursor and claude, its kinda annoying having to have the same skills in both so I made a ~/.agents/skills folder then ln both cursor and claude skills to point to that folder.
which works except that claude uses .skills/synced which is uses to sync changes to skills from claude servers into the skills folder.
every other agent I have used just directly syncs into .skills so it ends up duplicating skills
can i ask claude to change these settings for me, and will it enable telemetry as implied checkpoint when i ask it to enable AGENTS.md?
I am once again (for the third time) [0] asking you to stop using a closed-source harness.
[0] https://news.ycombinator.com/item?id=49760449
Uhm I turned off everything there is to turn off in my Pro plan, and Claude just read my agents.md with no issue? So... What telemetry am I missing? Or did they JUST update? (I updated my docker image 40 minutes ago to get Opus 5.5, am on version 2.1.280, so not the mentioned 2.1.277, so it's fixed?)
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.
Much respect for the prompt response, humility, and frank disclosure.
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.
The only difference between CLAUDE.md and AGENTS.md is the filename. Do you really need a whole plugin system to support that use case? Feels like this could have been a one line change.
One line change? Pffft. That means you're still looking at the code, you're behind the times.
I don't think this is a reasonable assumption. The document format in CLAUDE.md is whatever Anthropic specifies, where AGENTS.md is a common ground format that is expected to be supported by any agent, be it from Anthropic or not.
https://agents.md/
You might argue that differences are small or negligible, but that is just an expectation.
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.
On the other hand, if Anthropic is to follow the industry standards, this would never have happened in the first place.
The same guy writing readme's for my vibeslopped toy projects is also the readme writer at Anthropic, what a coincidence ;)
Well now, this is how you do community outreach
Ouch.
I've had to send such messages, but internally at work, not on HN!
Have a great day, human.
Blink twice if you need help
Would be interesting to know how much time you/your team spent on that design decision
Even if this was an honest rollout mistake, the design is indefensible. Reading a local file should never depend on a remote feature flag, and silently skipping it with no warning is worse. I've tried to give Claude Code the benefit of the doubt, but this crosses a line.
Not everything is malicious. The author of the feature already responded on why this happened
Claude Code also doesn't read AGENTS.md by default if there's a CLAUDE.md it can read instead. This isn't limited to your repo, e.g. if you have a ~/CLAUDE.md then no AGENTS.md will be read.
To always read both, you have to switch the 'Project instructions' setting to the non-default `claude-md-and-agents-md`.
Just in case anyone is wondering why their AGENTS.md still isn't being read.
This is not the only case where Anthropic has done stuff silently without giving users any information about changes that would hurt them.
The number of people raw-dogging software that executes arbitrary instructions on their machine coming from a 3rd party server just absolutely baffles me.
The same people who've spent years of their career making sure that never happens.
Urm... no tests caught this? How?
Claude Code Remote control only works with telemetry enabled too.