[BUG] Claude Code fails to read updated file content despite repeated user instructions

Resolved 💬 3 comments Opened Dec 11, 2025 by rabshanrahman Closed Dec 14, 2025

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

During a debugging session, Claude Code repeatedly failed to read current log data from a file (scratchpad.txt) that the user explicitly stated contained updated server logs. Claude continued referencing stale log data from hours earlier (04:07 UTC) when the current time was 23:57 UTC. The user corrected Claude at least 5 times, stating the updated logs were in the file. Claude ignored these corrections, made assumptions about the file content, and suggested the user fetch new logs instead of reading the file they had already provided.

What Should Happen?

  • Claude reads the full file or at minimum the most recent content
  • Claude checks timestamps in log data against current time
  • Claude follows user's explicit instruction that the file contains current data
  • Claude stops making assumptions after being corrected

Error Messages/Logs

Steps to Reproduce

  1. User opens file scratchpad.txt containing server logs
  2. User pastes fresh logs into the file
  3. User tells Claude "Review server logs in scratchpad.txt"
  4. Claude reads file but only looks at old content or wrong portion
  5. User says "the updated logs are in scratchpad.txt"
  6. Claude suggests user get fresh logs instead of reading the file
  7. User explicitly states timestamps and that file is updated
  8. Claude continues to reference old data or ignores file entirely

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.55 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗