claude-code - 💡(How to fix) Fix [Bug] Claude Code generates lower quality responses compared to web Claude with insufficient reasoning and outdated information [1 participants]

[{"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:540:12098)\n at emitWarning (ws:43:42)\n at #onOrOnce (ws:170:18)\n at MM8 (/$bunfs/root/src/entrypoints/cli.js:7610:4460)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T12:56:09.890Z"},{"error":"AxiosError: Request failed with status code 403\n at Mi (/$bunfs/root/src/entrypoints/cli.js:115:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12710)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:122:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T14:55:18.226Z"},{"error":"AxiosError: Request failed with status code 403\n at Mi (/$bunfs/root/src/entrypoints/cli.js:115:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:120:12710)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:122:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T14:55:24.101Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3449)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-05-05T15:01:17.562Z"}]

TL;DR

Investigate and address the repeated AxiosError with status code 403, which may indicate authentication or permission issues with the requests being made.

Guidance

• Review the request headers and authentication mechanisms used in the application to ensure they are correctly set up and valid.
• Check the server-side logs to understand why the requests are being rejected with a 403 status code, which typically indicates forbidden access.
• Verify that the version of Axios being used is up-to-date, as older versions might have known issues or bugs that could be contributing to the problem.
• Consider implementing retry logic for requests that fail due to temporary issues, but be cautious with retries for 403 errors as they are often indicative of a more permanent issue.

Example

No specific code example can be provided without more context on how requests are being made, but ensuring that requests include appropriate headers (e.g., Authorization) and that the server expects these requests can help resolve the 403 errors.

Notes

The provided error messages suggest issues with WebSocket events and Axios requests. However, without more specific information about the application's architecture and how these requests are being made, it's challenging to provide a precise fix. The bun warnings and errors also suggest potential issues with the development environment or build process.

Recommendation

Apply workaround: Focus on resolving the AxiosError with status code 403 by checking authentication and permissions. This is likely to address the most visible and impactful issue described in the error logs.