claude-code - 💡(How to fix) Fix [Bug] Claude responses contain repeated text sections requiring excessive scrollback [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/alexandre/.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-22T12:39:45.266Z"},{"error":"Error: console.error: [bun] Warning: ws.WebSocket 'unexpected-response' event is not implemented in bun\n at K (/$bunfs/root/src/entrypoints/cli.js:525:12055)\n at emitWarning (ws:43:42)\n at #onOrOnce (ws:170:18)\n at ps$ (/$bunfs/root/src/entrypoints/cli.js:3856:4688)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T14:02:11.274Z"}]

TL;DR

The issue of repeated text in Claude's responses may be related to a locking mechanism or WebSocket implementation, and checking the locking file or updating the WebSocket handling could potentially resolve the issue.

Guidance

• Investigate the locking mechanism for the file /home/alexandre/.local/share/claude/versions/2.1.117 to see if it's causing the repetition, possibly by checking file permissions or lock acquisition logic.
• Look into the WebSocket implementation, specifically the 'unexpected-response' event, to determine if it's contributing to the repeated text issue.
• Consider testing Claude's responses in a different terminal or environment to isolate if the issue is specific to the vte-based terminal or Linux platform.
• Review the error logs for any patterns or correlations between the errors and the repeated text issue.

Example

No specific code snippet can be provided without more context, but checking the cli.js file at lines 2756 and 3856 might offer insights into the locking and WebSocket handling mechanisms.

Notes

The provided errors suggest a potential issue with locking and WebSocket handling, but without more information about Claude's internal workings or the specific conditions under which the repetition occurs, it's challenging to provide a definitive fix.

Recommendation

Apply workaround: Given the uncertainty around the root cause, applying a workaround such as testing in a different environment or terminal, or potentially modifying the locking mechanism, might be the most feasible next step. This approach allows for further diagnosis without waiting for a potential update or fix.