claude-code - 💡(How to fix) Fix [Bug] Advisor mode incorrectly routes to Opus when Opus advisor is enabled [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/sharo/.local/share/claude/versions/2.1.123 (expected in multi-process scenarios)\n at C68 (/$bunfs/root/src/entrypoints/cli.js:2771:2177)\n at MM6 (/$bunfs/root/src/entrypoints/cli.js:2771:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-30T13:12:27.346Z"}]

TL;DR

The issue may be resolved by addressing the lock acquisition failure for the specified path.

Guidance

• Investigate the lock file at /home/sharo/.local/share/claude/versions/2.1.123 to determine the cause of the acquisition failure.
• Check for any ongoing processes that may be holding the lock and preventing other processes from acquiring it.
• Consider implementing a retry mechanism or a more robust locking strategy to handle multi-process scenarios.
• Verify that the error is not related to permissions issues by checking the ownership and access rights of the lock file.

Example

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

Notes

The provided error message suggests a non-fatal error, but it may still be causing issues with the advisor functionality. The lock acquisition failure could be related to the multi-process scenario mentioned in the error message.

Recommendation

Apply workaround: Implement a retry mechanism or a more robust locking strategy to handle multi-process scenarios, as the error message suggests that this is an expected issue in such scenarios.