Thread

Claude Code reads AGENTS.md only when telemetry is on [fixed]

486 points · 284 comments · pszypowicz

mpoteat · 1790168190 · focus · HN ↗
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: <a href="https://github.com/anthropics/claude-code/tree/main/mods/agents-md" rel="nofollow">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.
1. dotancohen · 1790176007 · focus · HN ↗
  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.
  1. post-it · 1790176990 · focus · HN ↗
    Not necessarily. They probably have an integrated service that handles some telemetry and also feature flags, like Braze. They toggled the whole thing off based on telemetry settings. It's a bug I've made before too.
  2. stravant · 1790177616 · focus · HN ↗
    That's just how big companies roll out software changes for software that auto-updates.
    It's much preferable to be able to instantly fix it if the rollout of a new feature goes wrong than have everyone who installed the broken version bring stuck with problems until the company realizes the issue and rolls forwards with a fixed version.
    <a href="https://martinfowler.com/articles/feature-toggles.html" rel="nofollow">https://martinfowler.com/articles/feature-toggles.html
    VulgarExigency · 1790179458 · focus · HN ↗
    I've used feature flags extensively throughout my career as a SaaS developer, but I've never considered their usage in desktop software. Not sure how I feel about it.
    scottyah · 1790180686 · focus · HN ↗
    Desktop software is like web-based software, except there's no sandbox or anyone trying to protect your privacy.
  3. dannyw · 1790185217 · focus · HN ↗
    I’d just assume good intent here. Feature flags, telemetry, and fast rollouts / rollbacks are standard practice in software. Have a look at chrome://flags perhaps.
    I fully believe GP that there was zero intent to gate this behind collecting telemetry. Sounds like a little tech debt and a little oversight, and the simplest explanation is that it is.
    lbourdages · 1790205984 · focus · HN ↗
    You can have flags work in a pull fashion, though. At boot, and every 5 minutes, query an endpoint which returns flag values. You don't need the client to send any information about what the user is doing.
    lionkor · 1790206557 · focus · HN ↗
    Well yes but as soon as you log this on the backend, you have telemetry, no?
    lbourdages · 1790275804 · focus · HN ↗
    There is a meaningful difference between a generic "load all flag values" call that is identical for all users and some actual telemetry which sends application context to the back-end.
  4. tyre · 1790198974 · focus · HN ↗
    Seems like they overloaded whatever they use for telemetry to do feature flags.
    It’s not a crazy conspiracy. They messed up, it’s fine.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.