claude-code - 💡(How to fix) Fix [Bug] --resume flag doesn't emit OSC smart title [1 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/campar/.local/share/claude/versions/2.1.97 (expected in multi-process scenarios)\n at gF$ (/$bunfs/root/src/entrypoints/cli.js:2772:2153)\n at ba8 (/$bunfs/root/src/entrypoints/cli.js:2772:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-08T22:41:57.456Z"}]

TL;DR

Investigate the lock acquisition failure for the /home/campar/.local/share/claude/versions/2.1.97 path to resolve the issue with the --resume option.

Guidance

• Check the permissions and ownership of the /home/campar/.local/share/claude/versions/2.1.97 directory to ensure the current user has write access.
• Verify if there are any other processes holding a lock on the same directory, which could be causing the acquisition failure.
• Consider deleting the lock file (if present) and retrying the operation to see if it resolves the issue.
• Review the code at cli.js:2772:2153 to understand the lock acquisition logic and potential failure points.

Notes

The provided error message suggests a non-fatal error, but it may still be causing issues with the --resume option. The lock acquisition failure could be related to file system permissions, concurrent processes, or other environmental factors.

Recommendation

Apply a workaround by checking and adjusting the directory permissions and investigating concurrent processes, as the root cause of the issue is likely related to the lock acquisition failure.