Skip to content

fix(opencode-go): set MiniMax-M3 context window to 1M#2781

Open
kapelame wants to merge 1 commit into
anomalyco:devfrom
kapelame:feat/opencode-go-minimax-m3-1m
Open

fix(opencode-go): set MiniMax-M3 context window to 1M#2781
kapelame wants to merge 1 commit into
anomalyco:devfrom
kapelame:feat/opencode-go-minimax-m3-1m

Conversation

@kapelame

Copy link
Copy Markdown

What

Set the context window for MiniMax M3 (3x usage) to 1,000,000 tokens in the opencode-go provider.

providers/opencode-go/models/minimax-m3.toml
  [limit]
- context = 512_000
+ context = 1_000_000

Why

The previous value (512_000) is the pricing-tier boundary — MiniMax-M3 is billed at a standard rate for ≤512K input and a long-context rate above it — not the model's actual context window. The model supports up to 1M tokens, which is what limit.context is meant to represent.

This aligns opencode-go with the minimax-owned providers (same change in #2762 for minimax / minimax-cn / minimax-coding-plan / minimax-cn-coding-plan). Scope is context only; output left unchanged.

The previous value (512_000) is the pricing-tier boundary, not the
model's actual context window. MiniMax-M3 supports up to 1M tokens.
Aligns opencode-go with the minimax-owned providers (see anomalyco#2762).
@rekram1-node

Copy link
Copy Markdown
Collaborator

AUTOMATED REVIEW: This change has already landed on dev in commit b4f37703. Please close this PR as superseded rather than merging the stale duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants