What Happened
Claude Code now reads AGENTS.md only when telemetry is on. Earlier, the tool loaded the file unconditionally. The fix was announced in the blog post Claude Code reads AGENTS.md only when telemetry is on [fixed].
If telemetry is disabled, the file is ignored unless you supply the configuration elsewhere. The change respects privacy and cuts unnecessary I/O, but it introduces a dependency on telemetry for agent initialization.
Why This Matters for Builders
- Telemetry control: In compliance environments that disable telemetry, agents will not load unless you provide the configuration via environment variables or a config endpoint.
- Workflow reliability: Orchestrators like n8n load agent definitions at start‑up. A silent switch can cause workflows to fall back to defaults and produce hard‑to‑trace errors.
- Performance: Reducing file I/O helps in resource‑constrained containers or edge deployments. If you rely on dynamic agent updates, ensure those updates still propagate.
- Security: Linking AGENTS.md loading to telemetry aligns with privacy best practices. Builders can disable telemetry without risking accidental data exfiltration.
Practical steps for automation teams
- Audit telemetry: Verify whether telemetry is enabled in your Claude Code deployment. If not, plan how to supply agent definitions.
- Externalize config: Store agent definitions in a secure vault or environment variable and load them during workflow initialization.
- Add health checks: Verify that agents are loaded before executing downstream tasks to catch silent failures early.
- Document the change: Update runbooks to note that AGENTS.md is no longer automatically read unless telemetry is on.
FAQ
Q: Will my existing n8n workflows break if telemetry is disabled?
A: Yes. Workflows that rely on automatic AGENTS.md loading may fail. Supply the definitions through another channel.
Q: Can I enable telemetry only for the agent loading step?
A: Telemetry is a global setting. To control agent loading without full telemetry, supply the config programmatically or via a separate file.
Q: Is there a way to revert to the old behavior?
A: The change is part of a fix and is not intended to roll back. Adjust your deployment to supply agent definitions explicitly if telemetry remains off.
Originally published on Automations Cookbook.
