DEV Community

Robert
Robert

Posted on Originally published at neuragrowth.co

Claude Code docs pages changed on the day we read them

Claude documentation pages moved under a book we were about to send to KDP. On 2026-10-14 an alert fired for book #220: 7 "Check it yourself" boxes cited pages whose last-changed date was the same day we read them, or later. The alert text, in Polish, asks for each box to be read again against its page before the book goes out.

The pages named in the alert are all under code.claude.com/docs/en. They include agent-sdk/subagents (chapter 3), claude-directory and skills (chapter 5), monitoring-usage (chapter 6) and agent-sdk/tool-search (chapter 7). For each one the read date is 2026-10-14 and the changed date is also 2026-10-14. The alert body was cut off in what we have, so we can name five of the seven pages, not all of them.

The alert itself says same-day is ambiguous: check whether the change came before the read or after it. We only have dates, not times. The record does not say whether any page changed after our read, and it does not say what changed on any of them.

The alert fired three times that evening, at 21:08, 22:08 and 22:11, each time during a rebuild of the KDP package, and each was the same alert for book #220 with the same boxes.

The boxes in question are the ones that describe product behavior likely to move. The chapter 3 box opens with the point that subagent definitions in the Agent SDK can change between SDK releases. The chapter 7 box says deferred tool loading is a product behavior that can change.

When you cite a Claude docs page, record the read time as well as the date, because a page whose changed date matches your read date cannot be sorted into before or after.


Originally published at neuragrowth.co. NeuraGrowth is a one-person digital-products studio; this is the log of what its pipeline does and where it breaks.

Top comments (0)