Live bug in 0.1.0
src/providers.js ships the z.ai preset as:
models: { opus: 'glm-5.2', sonnet: 'glm-5.2', haiku: 'glm-5.2' }
GLM-5.2 is a 1M-context model, but because ANTHROPIC_BASE_URL points away from api.anthropic.com, Claude Code cannot verify 1M support and falls back to a hardcoded 200,000. Users get ~20% of the context they're paying for, and auto-compaction fires at roughly 167–187K — which presents as "the model keeps forgetting things", with no error anywhere.
The fix is the [1m] suffix, not the window variable
Per model-config:
To enable extended context for a pinned model, append [1m] to the model ID in ANTHROPIC_DEFAULT_OPUS_MODEL or ANTHROPIC_DEFAULT_SONNET_MODEL
The suffix is read per variable, not per model
That second line is the trap: it must be appended to every model variable. One unsuffixed variable silently runs that tier at 200K.
Setting CLAUDE_CODE_AUTO_COMPACT_WINDOW=1000000 does not substitute for this — see #2, where the value is capped at the assumed window and collapses back to 200K.
Note this is a live upstream gap, not just ours
z.ai's international docs ship glm-5.2 with no suffix, while bigmodel.cn and Volcengine both document glm-5.2[1m] — same model, same vendor. Anyone following z.ai international's own instructions has this bug.
Proposal
Add an explicit extendedContext flag to the provider/model schema so the suffix is applied deliberately rather than by string-munging.
Acceptance criteria
Verified per-provider values
| Provider |
Model ID |
Window |
| MiniMax |
MiniMax-M3[1m] |
1000000 |
| Kimi |
kimi-k3[1m] |
1048576 (2^20) |
| Zhipu / bigmodel.cn |
glm-5.2[1m] |
1000000 |
| Volcengine ARK |
glm-5.2[1m] |
1000000 |
| z.ai international |
ships bare glm-5.2 |
← the gap |
Qwen/DashScope and DeepSeek document no [1m] — do not add speculatively.
Live bug in 0.1.0
src/providers.jsships the z.ai preset as:GLM-5.2 is a 1M-context model, but because
ANTHROPIC_BASE_URLpoints away fromapi.anthropic.com, Claude Code cannot verify 1M support and falls back to a hardcoded 200,000. Users get ~20% of the context they're paying for, and auto-compaction fires at roughly 167–187K — which presents as "the model keeps forgetting things", with no error anywhere.The fix is the
[1m]suffix, not the window variablePer model-config:
That second line is the trap: it must be appended to every model variable. One unsuffixed variable silently runs that tier at 200K.
Setting
CLAUDE_CODE_AUTO_COMPACT_WINDOW=1000000does not substitute for this — see #2, where the value is capped at the assumed window and collapses back to 200K.Note this is a live upstream gap, not just ours
z.ai's international docs ship
glm-5.2with no suffix, while bigmodel.cn and Volcengine both documentglm-5.2[1m]— same model, same vendor. Anyone following z.ai international's own instructions has this bug.Proposal
Add an explicit
extendedContextflag to the provider/model schema so the suffix is applied deliberately rather than by string-munging.Acceptance criteria
glm-5.2[1m]on all model tier variablesANTHROPIC_DEFAULT_*_MODELcarries the suffix when extended context is onglm-5.2are migrated or warned about/statusshould report 1MVerified per-provider values
MiniMax-M3[1m]kimi-k3[1m]glm-5.2[1m]glm-5.2[1m]glm-5.2Qwen/DashScope and DeepSeek document no
[1m]— do not add speculatively.