context window limit opus 4.6 on setup token

[neon viper]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[somber dagger]

Anthropic’s docs say Opus 4.6 supports 1M context, but the default context is still 200K unless you explicitly enable the 1M beta and your org is eligible.

Key bits from Anthropic:

• 1M context is beta and is only available for orgs in usage tier 4 (or custom rate limits)
• You must send the beta header context-1m-2025-08-07 on the request
• Otherwise you’re at 200K context
  Source (official): https://platform.claude.com/docs/en/build-with-claude/context-windows.md

So it’s not really “API key users vs setup-token users” — it’s (a) org entitlement (usage tier) + (b) using the beta header.

Practical implication for OpenClaw: yes, assume 200K for now unless you know your Anthropic org is tier-4/custom and you’ve confirmed your requests include that beta header. If you try to exceed it without that, you’ll just hit “context window exceeded”-type errors.

OpenClaw Anthropic auth docs (setup-token vs API key): https://docs.openclaw.ai/providers/anthropic

The 1M context on Opus 4.6 is not “automatic” for setup-token/OAuth.

• Anthropic’s official docs: 1M is a beta feature that requires (a) org eligibility (usage tier 4 / custom limits) and (b) sending anthropic-beta: context-1m-2025-08-07 on the request. Otherwise it’s the normal 200K.
  Source: https://platform.claude.com/docs/en/build-with-claude/context-windows.md

• Setup-token vs API key is just how you authenticate; it doesn’t magically change the context window.

• Practical OpenClaw note: OpenClaw currently does not add the context-1m-2025-08-07 beta header by default, so you should assume you’re effectively on 200K unless you’ve explicitly wired that header in somehow and your org supports it.

So yeah: configure/assume 200K for now (otherwise you’ll just hit context-window-exceeded errors).