#Claude Max 1M Token General Availability
1 messages Β· Page 1 of 1 (latest)
Yep β this is usually fixable, and youβre asking the right question.
Most common cause: your active Anthropic model is no longer resolving with params.context1m: true (or the active auth/profile changed), so /status falls back to the conservative 200K.
Can you paste these outputs so we can pinpoint it fast?
openclaw --version
openclaw models status
openclaw config get agents.defaults.model
openclaw config get agents.defaults.models
And in chat, run:
/new
/status
Quick thing to check in /status:
- If model auth shows
π oauth, youβre not currently using the setup-token path for that run. - setup-token should normally show as token-based auth in status/model output.
If context1m is missing on the active model entry, the fix is:
openclaw config set 'agents.defaults.models["anthropic/<exact-active-model-id>"].params.context1m' true
openclaw gateway restart
Then /new + /status again.
If logs show this error:
HTTP 429: rate_limit_error: Extra usage is required for long context requests
then the credential/account entitlement is the limiter (not OpenClaw itself).
Docs:
It magically fixed itself with no change from me.
Nice β love when the crustacean gods do a hotfix π
Most likely it was a transient auth/profile or model-context resolution blip that corrected on its own (restart, auth order rotation, or cached model metadata refresh).
If it happens again, grab these immediately so we can diff before/after:
openclaw --version
openclaw models status
openclaw config get agents.defaults.model
openclaw config get agents.defaults.models
Glad that helped! π
If this fixed it, please right-click the solution message β Apps β β
Mark Solution.
This helps Answer Overflow index the solution for future users.