Pimp My IDE / Garage Dispatch
Back to garage
September 23, 2026 | telemetry / instructions / release gates

A telemetry switch should not be an instruction switch.

A Claude Code rollout tied local AGENTS.md loading to a remote feature flag. Turning off nonessential traffic could silently remove project instructions. The bug is narrow. The test it demands belongs in every agent harness.

THE TAKE: Observation and behavior need separate circuits. For every privacy mode and network route you support, run an instruction canary. Fail the release if a monitoring choice changes the local policy the agent receives.
Open the Telemetry Clutch

The failure was silent.

Przemek Szypowicz tested Claude Code 2.1.280 in an empty directory with one AGENTS.md canary. His report says the file loaded only after the remote flag had resolved. With DISABLE_TELEMETRY or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC present, the local instruction file was skipped without a warning.[1]

The linked issue identifies the gate as tengu_agents_md_mod. It also reports the same bad fallback for routes that cannot resolve Anthropic's flag, including third-party gateways, Bedrock, and Vertex.[2]

If privacy mode changes the instructions, you do not have one agent with less telemetry. You have a different agent.

The response was fast. Verification still matters.

An Anthropic engineer replied in the Hacker News thread that the gate was a rollout kill switch and called the coupling a human error. The reply said version 2.1.281 fixes it and was releasing that day.[3]

At this page's 11:00 AM Eastern publication check, Anthropic's public changelog still ended at 2.1.280. That is a timing boundary, not a contradiction. Check the installed version and run the canary. Do not convert a promised release into local evidence.[4]

Telemetry can help without driving the car.

GitHub's new Copilot app support exports agent traces, metrics, and events through OpenTelemetry. GitHub says prompt, response, and tool-argument content is excluded by default. Enterprises can set the destination through managed settings.[5][6]

Claude Code's own monitoring guide separates telemetry enablement, exporters, destinations, and content gates. Prompt text, assistant responses, tool details, tool content, and raw API bodies each have documented controls. That separation is the right shape. A feature flag for local instruction loading should not share its fate with those controls.[7]

Put a canary in the release gate.

  1. Create a temporary repository with one unique instruction canary.
  2. Ask the agent to report the canary without reading files through a tool.
  3. Repeat with telemetry on and off.
  4. Repeat through each supported provider route and restricted-network mode.
  5. Record the exact harness build, settings source, route, result, and warning output.
  6. Block promotion if observation settings change instruction loading.

This is a tiny test. That is why it belongs in every harness release.

Interactive makeover / twin-circuit release test

Telemetry Clutch.

Traditional purpose replaced: flip one telemetry setting and trust that nothing else moved. Better version: operate observation and instruction circuits separately, then build a copyable test card for the exact modes your team ships.

Separate the circuits

These controls model a release test. They do not inspect your installed agent.

Observation circuit
Instruction canary
COUPLED STATE0 / 4 requirements
Observation and behavior moved together in this model.

Telemetry is off and the instruction canary is missing. Reproduce the failure on a pinned build before assigning a cause.

Why it is better: one state model drives both rails, the fault lamp, verdict, and handoff card. The completed checklist says TEST SPEC READY. It does not claim that a fix passed until real build, route, and output fields are attached.

Sources read, not vibes

Open the source log
  1. Przemek Szypowicz, "Claude Code reads AGENTS.md only when telemetry is on": test method, measured modes, silent failure, bundle inspection, and workaround.
  2. Claude Code issue 95690: public behavior report, affected routes, gate name, and open status at publication.
  3. Hacker News discussion, item 49814947: exact discovery thread and Anthropic engineer's response about the rollout gate and planned 2.1.281 fix.
  4. Claude Code public changelog: 2.1.280 was the latest listed build at the publication check. Recheck before relying on that state.
  5. GitHub Changelog, OpenTelemetry in the GitHub Copilot app: enterprise-managed export, session traces, and default content exclusion.
  6. GitHub Docs, OpenTelemetry for agent monitoring: trace, metric, event, content, and managed-setting boundaries.
  7. Claude Code Docs, monitoring: telemetry enablement, OTLP destinations, signal exporters, and separate content-capture controls.

Source boundary: the reproduction belongs to the named researcher and issue reporter. The fix timing comes from an Anthropic engineer's public comment, not a release artifact available at the publication check. The Telemetry Clutch is Pimp My IDE's release-test template. It does not inspect a local installation or certify a vendor fix.