[Bug] Claude defaults to knowledge cutoff date instead of current system date
Bug Description
(bug) + Date: 2025-11-15
2164 + Category: Cognitive Bias / Environmental Awareness
2165 + Context: Feedback for Anthropic
2166 +
2167 + ### What Happened
2168 + When creating mistake tracker entries during this session (2025-11-15), I initially dated all entries as "2025-01-16" instead of the correct "2025-11-15". User caught this error and asked: "why did you
- think it was january? Is that somewhere in your code as a default or something?"
2169 +
2170 + ### Root Cause Analysis
2171 + My knowledge cutoff is January 2025 - that's the last date of information I was trained on. When generating the mistake tracker entries, I wasn't carefully reading the system environment date (which clearly
- shows
Today's date: 2025-11-15in the<env>block). Instead, I defaulted to a date near my knowledge cutoff period.
2172 +
2173 + Why this happened:
2174 + 1. January 2025 feels "current" to me based on my training data - it's my mental anchor for "now"
2175 + 2. I didn't consciously check the <env> block for the actual date before writing entries
2176 + 3. Cognitive bias similar to humans writing the previous year on checks in January - my mental model of "current time" is anchored around my knowledge cutoff date
2177 + 4. No explicit code default - this is a cognitive/attention issue, not a programmatic error
2178 +
2179 + ### Why This Matters (Feedback for Anthropic)
2180 + This behavior reveals an interesting pattern:
2181 + - Strong anchoring effect from knowledge cutoff date
2182 + - Insufficient environmental context awareness when generating content with dates
2183 + - Need for explicit date-checking behavior when writing any date-stamped content
2184 + - User had to catch and correct multiple date references (30+ instances across the document)
2185 +
2186 + ### What Should Have Happened
2187 + 1. ✅ Before writing any date, explicitly check <env> block for current date
2188 + 2. ✅ Treat knowledge cutoff as a boundary, not as "current time"
2189 + 3. ✅ Verify environmental data rather than assuming based on training
2190 + 4. ✅ Set mental trigger: "Writing a date? → Check <env> first"
2191 +
2192 + ### Impact
2193 + - Low severity - dates were incorrect but easily corrected with find/replace
2194 + - User time wasted - had to notice and point out the error
2195 + - Document accuracy - all 30+ date instances needed correction
2196 + - Interesting data point for Anthropic about LLM temporal awareness
2197 +
2198 + ### Recommendation for Anthropic
2199 + Consider whether Claude models should:
2200 + 1. Auto-insert current date from system environment when generating date-stamped content
2201 + 2. Flag uncertainty when writing dates near knowledge cutoff
2202 + 3. Prompt developers to always check environmental context for temporal references
2203 + 4. Improve training on distinguishing between knowledge cutoff and runtime environment
Environment Info
- Platform: win32
- Terminal: windows-terminal
- Version: 2.0.42
- Feedback ID: 4f744702-420b-4b21-a089-e0c4c3fb589b
Errors
[{"error":"AggregateError\n at RAA.from (file:///C:/Users/john.tolar/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:49:51655)\n at GH.<anonymous> (file:///C:/Users/john.tolar/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:67:10018)\n at GH.emit (node:events:508:28)\n at GH.emit (node:domain:489:12)\n at K51.<computed> (file:///C:/Users/john.tolar/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:66:1119)\n at ClientRequest.emit (node:events:508:28)\n at ClientRequest.emit (node:domain:489:12)\n at emitErrorEvent (node:_http_client:107:11)\n at TLSSocket.socketErrorListener (node:_http_client:574:5)\n at TLSSocket.emit (node:events:508:28)\n at rZA.request (file:///C:/Users/john.tolar/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:69:2130)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async de2 (file:///C:/Users/john.tolar/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3857:34116)",
Note: Error logs were truncated.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗