claude-code - 💡(How to fix) Fix [Feature Request] Add configurable cache threshold for auto-clear behavior [1 comments, 2 participants]

[{"error":"AxiosError: Request failed with status code 401\n at zd (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12712)\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:117:2467)\n at async ot1 (/$bunfs/root/src/entrypoints/cli.js:3090:14589)\n at async v97 (/$bunfs/root/src/entrypoints/cli.js:3090:15128)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T08:59:26.176Z"},{"error":"AxiosError: Request failed with status code 401\n at zd (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12712)\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:117:2467)\n at async ot1 (/$bunfs/root/src/entrypoints/cli.js:3090:14589)\n at async v97 (/$bunfs/root/src/entrypoints/cli.js:3090:15128)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-22T08:59:26.177Z"}]

TL;DR

The issue is likely related to authentication, as indicated by the 401 status code in the error messages, and may require re-authentication or adjusting authentication settings.

Guidance

• Verify that the authentication credentials are correct and not expired.
• Check the documentation for the claude code and Axios library to see if there are any specific authentication requirements or troubleshooting steps.
• Consider clearing the cache and retrying the request to see if it resolves the issue.
• Review the error messages to see if there are any other clues about the cause of the authentication failure.

Notes

The provided information does not include specific details about the authentication mechanism or the claude code, so it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Re-authenticate and adjust authentication settings as needed, as the 401 status code suggests an authentication issue.