claude-code - 💡(How to fix) Fix [Bug] Anthropic API Error: Extra usage required for Sonnet 4.6 1M context on Max x20 plan [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/dannywayne/.local/share/claude/versions/2.1.111 (expected in multi-process scenarios)\n at Kd_ (/$bunfs/root/src/entrypoints/cli.js:2748:2177)\n at qe6 (/$bunfs/root/src/entrypoints/cli.js:2748:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T15:59:33.458Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12917)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:114:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T15:59:48.482Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12917)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:114:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T16:02:52.764Z"},{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T16:05:21.670Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12917)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:114:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T16:05:22.628Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12917)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:114:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T16:06:32.876Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12917)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:114:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T16:07:23.959Z"},{"error":"Error: Was there a typo in the url or port?\n at from (/$bunfs/root/src/entrypoints/cli.js:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12917)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:114:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-16T16:07:46.845Z"},{"error":"Error: ECONNREFUSED\n at from (/$bunfs/root/src/entrypoints/cli.js:107:7862)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12917)\n at emitError (node:events:43:23)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:114:1149)\n at emitError (node:events:43:23)\n at <anonymous> (node:_http_client:253:22)\n at…

TL;DR

The issue can be resolved by running the /extra-usage command to enable extra usage for the 1M context or by switching to the standard context using the /model command.

Guidance

• The error message "API Error: Extra usage is required for 1M context" indicates that the current plan (Max x20) requires extra usage to be enabled for the 1M context.
• The user can try running the /extra-usage command to enable extra usage and see if it resolves the issue.
• Alternatively, the user can try switching to the standard context using the /model command to avoid the extra usage requirement.
• The repeated ECONNREFUSED errors suggest a potential connection issue, but the primary issue seems to be related to the extra usage requirement.

Example

No code snippet is provided as the issue seems to be related to a specific command or configuration rather than a code-level problem.

Notes

The provided error logs are truncated, which might limit the ability to identify the full scope of the issue. However, the initial error message provides a clear indication of the problem.

Recommendation

Apply the workaround by running the /extra-usage command to enable extra usage for the 1M context, as this directly addresses the stated error message and required action.