claude-code - 💡(How to fix) Fix [Bug] File read-tracking state not reset when conversation is rewound [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/user/.local/share/claude/versions/2.1.123 (expected in multi-process scenarios)\n at x86 (/$bunfs/root/src/entrypoints/cli.js:2769:2177)\n at Jw8 (/$bunfs/root/src/entrypoints/cli.js:2769:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-29T12:37:19.849Z"}]

TL;DR

The issue can be mitigated by resetting the harness's read-tracking state when rewinding the conversation to a point before a Read call.

Guidance

• When rewinding the conversation, ensure that the harness's read-tracking state is reset to reflect the new context, allowing Claude to re-read the file if necessary.
• Investigate the cli.js file at line 2769 to understand the lock acquisition failure and its relation to the read-tracking state.
• Consider adding a check to verify if Claude has the file contents in context before attempting to act on it, to prevent errors.
• Review the error handling mechanism to determine if the "NON-FATAL" error can be safely ignored or if it indicates a more significant issue.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The provided error message suggests a potential issue with lock acquisition, but its relation to the main problem is unclear. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Reset the harness's read-tracking state when rewinding the conversation, as this directly addresses the described issue and allows Claude to recover the file content.