[Bug] "Unchanged since last read" error when reading file previously accessed in reverted conversation state

Open 💬 11 comments Opened Apr 1, 2026 by ihor-drachuk

Bug Description
"Unchanged since last read" error after reverting conversation history AND trying to read file which was read in "future" discussion.

Environment Info

  • Platform: win32
  • Terminal: null
  • Version: 2.1.89
  • Feedback ID: fe38e241-eb59-4b76-aaef-86cf0a1fb91b

Errors

[{"error":"ENOENT: no such file or directory, unlink 'C:\\Users\\User\\AppData\\Local\\Temp\\claude\\C--workspace-win\\b425b35f-5a58-498f-b7d2-4d231e35850c\\tasks\\a8eb08cb46fb39d67.output'","timestamp":"2026-04-01T21:41:17.463Z"},{"error":"ENOENT: no such file or directory, unlink 'C:\\Users\\User\\AppData\\Local\\Temp\\claude\\C--workspace-win\\b425b35f-5a58-498f-b7d2-4d231e35850c\\tasks\\ab6d120a7b02e3171.output'","timestamp":"2026-04-01T21:47:29.515Z"},{"error":"MaxFileReadTokenExceededError: File content (10420 tokens) exceeds maximum allowed tokens (10000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n    at S7_ (B:/~BUN/root/src/entrypoints/cli.js:4351:13364)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-01T21:55:34.978Z"}]

View original on GitHub ↗

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