claude-code - 💡(How to fix) Fix [Bug] /clear command doesn't clear UI history in Warp terminal [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/gubiera/.local/share/claude/versions/2.1.116 (expected in multi-process scenarios)\n at jl_ (/$bunfs/root/src/entrypoints/cli.js:2752:2177)\n at B88 (/$bunfs/root/src/entrypoints/cli.js:2752:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-21T15:37:31.173Z"},{"error":"Error\n at call (/$bunfs/root/src/entrypoints/cli.js:4741:7630)\n at processTicksAndRejections (unknown:7:39)","timestamp":"2026-04-21T17:03:52.297Z"}]

TL;DR

The issue with the UI keeping history on Warp after using /clear may be related to a locking mechanism failure, and checking the lock acquisition process or the multi-process scenario handling could provide insights.

Guidance

• Investigate the lock acquisition failure error and its relation to the /clear command, as it might be causing the history to persist.
• Review the multi-process scenarios in the application to ensure proper handling and synchronization, which could be contributing to the locking issue.
• Examine the cli.js file, specifically lines 2752 and 4741, for potential clues on the error's origin and how it affects the UI's history.
• Consider testing the /clear command in a single-process scenario to isolate if the issue is indeed related to multi-process handling.

Example

No specific code snippet can be provided without further context, but reviewing the mentioned lines in cli.js could look like:

// $bunfs/root/src/entrypoints/cli.js:2752
function jl_() {
  // ...
  // Lock acquisition logic here
}

// $bunfs/root/src/entrypoints/cli.js:4741
function call() {
  // ...
  // Potential error source
}

Notes

The provided information suggests a complex issue potentially related to process synchronization and locking mechanisms. Without more context or specific code, it's challenging to provide a definitive fix.

Recommendation

Apply workaround: Given the complexity and the lack of a clear solution from the provided information, it might be necessary to implement a temporary workaround, such as manually clearing the history or adjusting the locking mechanism, until a more permanent fix can be developed.