[Bug] Opus 1M model fails to initialize despite active subscription
Resolved 💬 3 comments Opened Mar 30, 2026 by misaelabanto Closed Mar 31, 2026
Bug Description
I'm not able to run Opus 1M by default. I've paid 5X plan to fix this and now it continues without working. Why is it the default model then?
Environment Info
- Platform: linux
- Terminal: zed
- Version: 2.1.87
- Feedback ID: 22b1e1b4-6835-4ce7-807a-bd377861c980
Errors
[{"error":"Error: NON-FATAL: Lock acquisition failed for /home/misaelabanto/.local/share/claude/versions/2.1.87 (expected in multi-process scenarios)\n at em$ (/$bunfs/root/src/entrypoints/cli.js:2849:2138)\n at Ei8 (/$bunfs/root/src/entrypoints/cli.js:2849:1218)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-30T22:24:26.637Z"},{"error":"Error: 429 {\"type\":\"error\",\"error\":{\"type\":\"rate_limit_error\",\"message\":\"Extra usage is required for long context requests.\"},\"request_id\":\"req_011CZa3qvYde78qNEXWG3tQZ\"}\n at generate (/$bunfs/root/src/entrypoints/cli.js:11:50937)\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:5435)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-30T22:25:33.538Z"}]This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗