claude-code - 💡(How to fix) Fix [Bug] Anthropic API Error: Stream idle timeout - partial response with no retry mechanism [1 participants]

[{"error":"Error: File does not exist. Note: your current working directory is /Users/.../...-terminal.\n at call (/$bunfs/root/src/entrypoints/cli.js:4303:7610)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T02:49:20.844Z"},{"error":"AxiosError: Request failed with status code 403\n at hB (/$bunfs/root/src/entrypoints/cli.js:108:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:113:12750)\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:115:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T02:57:50.346Z"},{"error":"AxiosError: Request failed with status code 404\n at hB (/$bunfs/root/src/entrypoints/cli.js:108:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:113:12750)\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:115:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T02:57:57.599Z"},{"error":"AxiosError: Request failed with status code 404\n at hB (/$bunfs/root/src/entrypoints/cli.js:108:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:113:12750)\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:115:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T02:58:42.163Z"}]

TL;DR

Check the file path and API request URLs to ensure they are correct and the resources exist.

Guidance

• Verify the current working directory /Users/.../...-terminal is correct and the required files are present.
• Review the API request URLs to ensure they are correctly formatted and the requested resources exist, as indicated by the 404 status codes.
• Check the authentication and permissions for the API requests, as the 403 status code suggests an authorization issue.
• Consider retrying the requests or checking the network connectivity to rule out any transient issues.

Example

No specific code snippet can be provided without more context, but ensuring correct file paths and API URLs is crucial.

Notes

The issue seems to involve a combination of file system and API request errors, making it essential to verify both aspects.

Recommendation

Apply workaround: Verify and correct file paths and API request URLs to resolve the errors, as the issue seems to be related to incorrect resource access rather than a version-specific problem.