Skip to content

fix(amazon-bedrock): correct MiniMax M2.5 and GLM-5 context/output limits#1272

Merged
rekram1-node merged 1 commit intoanomalyco:devfrom
NachoFLizaur:fix/bedrock-minimax-m2.5-glm-5-limits
Mar 25, 2026
Merged

fix(amazon-bedrock): correct MiniMax M2.5 and GLM-5 context/output limits#1272
rekram1-node merged 1 commit intoanomalyco:devfrom
NachoFLizaur:fix/bedrock-minimax-m2.5-glm-5-limits

Conversation

@NachoFLizaur
Copy link
Contributor

Fixes #1271

What does this PR do?

Corrects the context window, output limits, release dates, and family name for the Bedrock MiniMax M2.5 and GLM-5 entries in providers/amazon-bedrock/models/

  • MiniMax M2.5: context should be 196,608 (not 1M), output should be 98,304 (not 131,072)
  • GLM-5: context should be 202,752 (not 200,000), output should be 101,376 (not 131,072)

How did you verify?

Values come from the raw Bedrock list foundational models API metadata: converse.maxTokensMaximum for context limits and consoleIDEMetadata.converse.maxTokensMaximum for output limits.

The models card for Minimax M2.5 incorrectly list it as having 1M token window and 8K output tokens.

This can also be validated by sending maxTokens: 9999999 through the Converse API (the error response returns the exact enforced limit).

@rekram1-node rekram1-node merged commit 5b73677 into anomalyco:dev Mar 25, 2026
1 check passed
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.

Bug: Bedrock MiniMax M2.5 and GLM-5 have incorrect context/output limits

2 participants