Why
- The cutoff. The model learned from texts up to a certain month. It doesn’t know what came out later, and doesn’t know that it doesn’t know: “the latest Traefik” to it is the latest in its data.
- The weight of the old. Years of writing about Docker Compose v1 with
docker-composeandversion: "3.8"outweigh what exists about current versions. Without a hint, the model reaches for the common one. - No clock. “How many days until a certificate issued on 2026-08-01 expires?” — without today’s date, the model substitutes its own.
What to write
| What | Example |
|---|---|
| date | Today is 2026-10-18. |
| OS and shell | Ubuntu 24.04, bash 5.2 · Windows 11, PowerShell 5.1 |
| versions | Docker 29, Compose v5.6, Traefik 3.7, CrowdSec 1.6 — as --version prints them |
| language and libraries | Astro 7, Node 24; for code, the versions from package.json |
| anything newer than the cutoff | a piece of documentation or a changelog in <docs> tags |
Put the constant parts in CLAUDE.md or the project instructions (Long conversations) so you don’t write
them every time. Not the date, though: it goes stale. Agents in the editor usually insert the date themselves — check
whether it’s in the context.
How to check
Ask “what’s the latest version of Traefik?” without search. The model’s answer reflects its cutoff, not today’s
release; compare with docker run --rm traefik:v3 version or the releases page.