claude-code - 💡(How to fix) Fix [Bug] Session limit consumption rate is unpredictable and inconsistent [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/tomas/.local/share/claude/versions/2.1.117 (expected in multi-process scenarios)\n at Dn$ (/$bunfs/root/src/entrypoints/cli.js:2756:2177)\n at tq6 (/$bunfs/root/src/entrypoints/cli.js:2756:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T09:37:19.076Z"}]

TL;DR

The session limit issue may be related to the lock acquisition failure error, and clearing sessions before starting a new one might help mitigate the problem.

Guidance

• The error message suggests a lock acquisition failure, which could be causing the session limit to disappear quickly. Investigate if multiple processes are accessing the same resource simultaneously.
• Try to reproduce the issue with a consistent workload to see if the session limit depletion is indeed unpredictable.
• Clearing all sessions before starting a new one, as done with the Team account, might help prevent the issue. Try to make this a standard practice.
• The fact that the issue occurs on both Team and Pro accounts suggests that the problem might not be account-specific.

Example

No code snippet is provided as the issue does not imply a specific code-related fix.

Notes

The issue seems to be related to the specific version (2.1.117) and platform (linux), so the solution might not apply to other versions or platforms.

Recommendation

Apply workaround: Clear all sessions before starting a new one, as this seems to have helped in one of the instances described. This might help mitigate the issue until a more permanent fix is found.