Skip to content

fix(provider): add MiniMax-M3 and missing M2.7 variants to minimax provider #10431

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alexhancock merged 1 commit into from
Jul 15, 2026
+13 −0
Merged

fix(provider): add MiniMax-M3 and missing M2.7 variants to minimax provider #10431

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions crates/goose-providers/src/declarative/definitions/minimax.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,20 @@
"description": "MiniMax AI models with long context support via Anthropic-compatible API",
"api_key_env": "MINIMAX_API_KEY",
"base_url": "https://api.minimax.io/anthropic",
"dynamic_models": true,

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Don't refresh away MiniMax highspeed models

When MINIMAX_API_KEY is configured, this flips MiniMax inventory refresh on (register_declarative_provider passes config.dynamic_models.unwrap_or(false) as supports_refresh). A successful refresh stores only the IDs returned by GET /anthropic/v1/models and inventory_models_from_snapshot then uses that snapshot instead of these static entries; MiniMax's documented List Models response (https://platform.minimax.io/docs/api-reference/models/anthropic/list-models) contains MiniMax-M3, MiniMax-M2.7, and MiniMax-M2.5 but not either *-highspeed ID, while the supported-models page says the highspeed IDs are valid. After such a refresh, ACP defaults validation checks only entry.models, so selecting MiniMax-M2.7-highspeed is rejected even though this patch adds it; keep dynamic refresh off or merge the static highspeed IDs into refreshed inventories.

Useful? React with 👍 / 👎.

@sheikhlimon sheikhlimon Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Structural concern's fair, but the live /anthropic/v1/models response does include both highspeed IDs – so no immediate regression. Filed the merge gap as a follow-up. Keeping dynamic_models: true for the auto-discovery benefit.

"models": [
{
"name": "MiniMax-M3",
"context_limit": 1000000
},
{
"name": "MiniMax-M2.7",
"context_limit": 200000
},
{
"name": "MiniMax-M2.7-highspeed",
"context_limit": 200000
},
{
"name": "MiniMax-M2.5",
"context_limit": 204800
Expand Down
Loading