claude-code - 💡(How to fix) Fix [Bug] Model performance degradation compared to previous version [1 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/rachitkay/.local/share/claude/versions/2.1.114 (expected in multi-process scenarios)\n at sd_ (/$bunfs/root/src/entrypoints/cli.js:2751:2177)\n at WH8 (/$bunfs/root/src/entrypoints/cli.js:2751:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T10:36:51.245Z"},{"error":"MaxFileReadTokenExceededError: File content (43991 tokens) exceeds maximum allowed tokens (25000). Use offset and limit parameters to read specific portions of the file, or search for specific content instead of reading the whole file.\n at nj7 (/$bunfs/root/src/entrypoints/cli.js:4723:12550)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T18:44:22.790Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/rachitkay/Desktop/ultrahuman/code/web-dashboard.\n at call (/$bunfs/root/src/entrypoints/cli.js:4732:7630)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T18:48:36.819Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/rachitkay/Desktop/ultrahuman/code/web-dashboard.\n at call (/$bunfs/root/src/entrypoints/cli.js:4732:7630)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T18:48:40.607Z"},{"error":"Error: Failed to download binary from https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.116/darwin-arm64/claude: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()\n at jF1 (/$bunfs/root/src/entrypoints/cli.js:2749:7713)\n at async Fn9 (/$bunfs/root/src/entrypoints/cli.js:2749:7803)\n at async ln9 (/$bunfs/root/src/entrypoints/cli.js:2749:14817)\n at async ZF1 (unknown)\n at async nn9 (unknown)\n at unknown\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T23:14:29.041Z"},{"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:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12521)\n at emitError (node:events:43:23)\n at emitErrorNT (internal:streams/destroy:88:12)\n at emitErrorCloseNT (internal:streams/destroy:69:14)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at async fF1 (/$bunfs/root/src/entrypoints/cli.js:2749:6030)\n at async jF1 (/$bunfs/root/src/entrypoints/cli.js:2749:7341)\n at async Fn9 (/$bunfs/root/src/entrypoints/cli.js:2749:7803)\n at async ln9 (/$bunfs/root/src/entrypoints/cli.js:2749:14817)\n at async ZF1 (unknown)\n at async nn9 (unknown)\n at unknown\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T23:14:29.041Z"},{"error":"Error: Failed to download binary from https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/2.1.116/darwin-arm64/claude: The socket connection was closed unexpectedly. For more information, pass verbose: true in the second argument to fetch()\n at jF1 (/$bunfs/root/src/entrypoints/cli.js:2749:7713)\n at async Fn9 (unknown)\n at async ln9 (unknown)\n at async ZF1 (/$bunfs/root/src/entrypoints/cli.js:2749:17530)\n at async nn9 (/$bunfs/root/src/entrypoints/cli.js:2751:322)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:8272:14323)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T23:54:04.031Z"},{"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:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12521)\n at emitError (node:events:43:23)\n at emitErrorNT (internal:streams/destroy:88:12)\n at emitErrorCloseNT (internal:streams/destroy:69:14)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at async fF1 (unknown)\n at async jF1 (unknown)\n at async Fn9 (unknown)\n at async ln9 (unknown)\n at async ZF1 (/$bunfs/root/src/entrypoints/cli.js:2749:17530)\n at async nn9 (/$bunfs/root/src/entrypoints/cli.js:2751:322)\n at async <anonymous> (/$bunfs/root/src/entrypoints/cli.js:8272:14323)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-20T23:54:04.031Z"},{"error":"Error: Failed to download binary from https://storage…

TL;DR

The most likely fix is to investigate and resolve the socket connection issues and file access problems reported in the errors.

Guidance

1. Check network connectivity: Verify that the system has a stable internet connection to download binaries from the specified URLs.
2. Inspect file system permissions: Ensure that the application has the necessary permissions to access and write to the files and directories mentioned in the errors, such as /Users/rachitkay/.local/share/claude/versions/2.1.114.
3. Review error handling: Consider implementing more robust error handling to gracefully manage situations like socket connection closures and file access issues.
4. Verify version compatibility: Although not directly implied, ensuring that the version of the software (2.1.114) is compatible with the system and dependencies might help resolve some issues.
5. Pass verbose: true in fetch: As suggested by some error messages, passing verbose: true in the second argument to fetch() might provide more detailed information about the errors, aiding in debugging.

Example

No specific code example can be provided without more context, but ensuring proper error handling for network requests and file operations is crucial. For instance, using try-catch blocks for fetch operations and checking file existence before attempting to access it can help mitigate some of the reported errors.

Notes

• The provided error messages suggest a mix of network connectivity issues, file access problems, and possibly version compatibility concerns.
• The content was truncated, which might mean there are additional errors or details not considered in this analysis.
• Without more specific information about the application, its dependencies, or the exact commands being run, it's challenging to provide a more targeted solution.

Recommendation

Apply workaround: Given the nature of the errors, applying workarounds such as checking network connectivity, ensuring file system permissions are correct, and enhancing error handling in the application code might be the most straightforward path to resolving the issue. Upgrading to a potentially fixed version is not clearly implied as a solution based on the provided information.