claude-code - 💡(How to fix) Fix [Bug] Multiple concurrent sessions spawned on same worktree without tracking [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/nick/.local/share/claude/versions/2.1.128 (expected in multi-process scenarios)\n at Nq6 (/$bunfs/root/src/entrypoints/cli.js:2764:2177)\n at uGH (/$bunfs/root/src/entrypoints/cli.js:2764:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T20:14:01.698Z"},{"error":"Error: Working directory "/Users/nick/dotfiles/.claude/worktrees/ese-upgrade" was deleted; shell cwd recovered to "/Users/nick". Re-issue your command (it will run from the recovered directory).\n at call (/$bunfs/root/src/entrypoints/cli.js:5059:1395)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T20:47:44.743Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3449)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-06T00:31:19.770Z"}]

TL;DR

The issue can be mitigated by ensuring that Claude sessions are properly managed and terminated when no longer needed, to prevent concurrent access to the same worktree.

Guidance

• Investigate the Claude code to identify where and why it is spawning unnecessary sessions that are working concurrently on the same worktree.
• Review the error messages to understand the specific issues caused by these concurrent sessions, such as lock acquisition failures and working directory deletions.
• Consider implementing a mechanism to track and manage active sessions, ensuring that only one session is working on a given worktree at a time.
• Look into the cli.js file, specifically lines 2764 and 5059, to understand how the errors are being handled and potentially modify the code to better handle these scenarios.

Notes

The provided information suggests that the issue is related to the management of Claude sessions and their access to worktrees, but without more context or code, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Implement a session management mechanism to prevent concurrent access to the same worktree, as this appears to be the root cause of the errors and issues described.