claude-code - 💡(How to fix) Fix [Bug] Anthropic API: claude-opus-4-7 context window silently degraded from 1M to 400k tokens [1 comments, 2 participants]

[{"error":"Error: Request was aborted.\n at _16 (/$bunfs/root/src/entrypoints/cli.js:5379:1669)\n at next (native:1:11)\n at V$K (/$bunfs/root/src/entrypoints/cli.js:8838:5693)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T07:01:24.645Z"},{"error":"Error: Compaction interrupted · This may be due to network issues — please try again.\n at GC7 (/$bunfs/root/src/entrypoints/cli.js:4807:7050)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T07:01:24.646Z"},{"error":"Error: Request was aborted.\n at _16 (/$bunfs/root/src/entrypoints/cli.js:5379:1669)\n at next (native:1:11)\n at V$K (/$bunfs/root/src/entrypoints/cli.js:8838:5693)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T07:03:43.657Z"},{"error":"Error: Compaction interrupted · This may be due to network issues — please try again.\n at GC7 (/$bunfs/root/src/entrypoints/cli.js:4807:7050)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T07:03:43.658Z"},{"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-27T07:04:04.627Z"}]

TL;DR

The Opus 4.7 model is reported as 1M context but is capped at 400k tokens, suggesting a potential discrepancy between the model's advertised capacity and its actual behavior.

Guidance

• The error messages indicate issues with request abortion and compaction interruption, which may be related to network problems or server-side limitations.
• Verify the model's actual capacity by checking the documentation or contacting the model's developers to confirm the expected behavior.
• Investigate potential network issues or server-side limitations that could be causing the request abortions and compaction interruptions.
• Consider retrying the request or checking for any updates to the model or its dependencies.

Notes

The provided information does not include explicit details about the model's implementation or the underlying infrastructure, making it challenging to provide a definitive solution.

Recommendation

Apply workaround: Retry the request or check for updates to the model or its dependencies, as the error messages suggest potential network or server-side issues.