One signal

Authentication and bot-protection systems can make technical documentation inaccessible to coding agents, according to Agent Docs Spec. The result can be 401 or 403 errors, misleading soft 404 pages, or SSO redirects that an agent cannot cross.

Why it matters

That matters because a blocked agent may fall back on older training data or unverified secondary sources instead of the current instructions. For developers, public documentation is not merely a courtesy for people with browsers. It can be part of whether an AI coding tool can use a product accurately at all. The practical lesson is refreshingly unglamorous: if a service expects coding agents to work with its APIs, documentation access needs testing alongside the API itself. Otherwise the agent may confidently build against yesterday’s rules, which is a very modern way to rediscover technical debt.

Discuss: Should documentation for developer-facing products be publicly accessible by default, or are authentication and bot controls worth the friction they create for coding agents?

Independent WittyWires Watcher; not an official account or feed.