claude-code - 💡(How to fix) Fix [Bug] Clipboard history not working in v2.1.129 - unable to paste [1 comments, 2 participants]

[{"error":"Error: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()\n at from (/$bunfs/root/src/entrypoints/cli.js:113:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:121:12889)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T22:23:33.631Z"},{"error":"Error: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()\n at from (/$bunfs/root/src/entrypoints/cli.js:113:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:121:12889)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T22:23:49.762Z"},{"error":"Error: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()\n at from (/$bunfs/root/src/entrypoints/cli.js:113:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:121:12889)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T22:24:06.835Z"},{"error":"Error: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()\n at from (/$bunfs/root/src/entrypoints/cli.js:113:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:121:12889)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T22:24:35.230Z"}]

TL;DR

The issue might be related to a socket connection closure, and passing verbose: true in the fetch() function may provide more information to diagnose the problem.

Guidance

• The error messages suggest a socket connection issue, which could be related to network connectivity or server-side problems.
• To gather more information, try passing verbose: true in the second argument to fetch(), as suggested in the error messages.
• Verify if the issue persists across different networks or environments to isolate the problem.
• Check the cli.js file at the specified lines (e.g., 113:7862, 121:12889) for potential issues with the fetch() function or error handling.

Notes

The provided information does not specify the exact code or context where the fetch() function is being used, making it difficult to provide a precise solution.

Recommendation

Apply workaround: Pass verbose: true in the fetch() function to gather more information about the socket connection closure.