MiniMax: the model is MiniMax-M3.1-Flash (out of preview)

The API now answers MiniMax-M3.1-Flash-Preview as MiniMax-M3.1-Flash, and
accepts the new name directly. Verified 2026-11-03: a live call returns
"ok" with a 1M context window. Claude Code 2.1.317 prints an
unrecognized_model warning for either name; the session still runs.

Claude-Session: https://claude.ai/code/session_01CLUCNYsiEaER1CMqw5WqfY

specs/ci-triage-minimax-run.spec.md

@@ -20,7 +20,7 @@ ci-triage-minimax-run --repo <owner/repo> --run <N> [--job <name|id>] \
 | `--tail` | 2000 | Log lines fetched (gac `--tail`) |
 | `--max-turns` | 25 | Sub-session turn cap |
 | `--timeout` | 300 | Internal timeout (logs-only task; well under the harness Bash 600s cap) |
-| `--m3` | off | Use `MiniMax-M3[1m]` instead of the default `MiniMax-M3.1-Flash-Preview` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
+| `--m3` | off | Use `MiniMax-M3[1m]` instead of the default `MiniMax-M3.1-Flash` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
 | `--effort <level>` | `low` | Thinking depth `low\|medium\|high\|xhigh\|max`, passed to `ask-minimax-run --effort`. Any other value exits 1. |
 | `--dryrun`, `-n` | off | Print resolved config, the gac command, the full prompt, and the sub-session command line; invoke neither gac's log fetch nor the sub-session |
 

specs/explore-minimax-run.spec.md

@@ -20,7 +20,7 @@ explore-minimax-run --root <path> [--root <path> ...] \
 | `--breadth` | `medium` | `medium` (stop when confidently answered) or `very-thorough` (full sweep, alternate naming conventions) |
 | `--max-turns` | 40 | Sub-session turn cap |
 | `--timeout` | 540 | Internal timeout in seconds (keeps callers under the harness Bash 600s cap) |
-| `--m3` | off | Use `MiniMax-M3` instead of the default `MiniMax-M3.1-Flash-Preview` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
+| `--m3` | off | Use `MiniMax-M3` instead of the default `MiniMax-M3.1-Flash` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
 | `--effort <level>` | `medium` | Thinking depth `low\|medium\|high\|xhigh\|max`, passed to `ask-minimax-run --effort`. Any other value exits 1. |
 
 ## Behaviour / requirements

specs/mm-worktree-task.spec.md

@@ -26,7 +26,7 @@ mm-worktree-task <item-uuid> [OPTIONS]
 | `--docs all\|recent\|none` | `recent` | Which item documents to bundle. `recent` = documents updated in the last 14 days; falls back to `all` if the CLI does not expose update dates. The full list of document names is always included in the prompt regardless of which are bundled. |
 | `--tools "<list>"` | — | Extra `--allowedTools` entries merged into the default allowlist (comma-separated). |
 | `--timeout <secs>` | `1800` | Max seconds the sub-session may run (`timeout <secs>` wrapper). |
-| `--m3` | off | Use `MiniMax-M3[1m]` instead of the default `MiniMax-M3.1-Flash-Preview` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
+| `--m3` | off | Use `MiniMax-M3[1m]` instead of the default `MiniMax-M3.1-Flash` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
 | `--effort <level>` | `max` | Thinking depth `low\|medium\|high\|xhigh\|max`, passed to `ask-minimax-run --effort`. Any other value exits 1. |
 | `--gate "<command>"` | — | Supervisor gate: after the sub-session exits, `mm-worktree-task` itself re-runs this command in the worktree against the sub-session's LAST commit and appends a `## Supervisor gate` section to the result file (see Behaviour §8). Never trust the agent's own "tests pass" claim — this re-run is the check. |
 | `--gate-timeout <secs>` | `900` | Max seconds `--gate`'s command may run before it is killed and recorded as a timed-out (failed) gate. |

specs/review-loop-run.spec.md

@@ -35,7 +35,7 @@ review-loop-run --help
 | `--prev` | auto | Explicit previous-round result file (overrides the auto lookup). |
 | `--tools` | kind default | Extra `--allowedTools` entries (comma-separated). |
 | `--timeout` | 1500 | Seconds before the sub-session is killed. |
-| `--m3` | off | Use `MiniMax-M3` instead of the default `MiniMax-M3.1-Flash-Preview` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
+| `--m3` | off | Use `MiniMax-M3` instead of the default `MiniMax-M3.1-Flash` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
 | `--effort <level>` | `max` | Thinking depth `low\|medium\|high\|xhigh\|max`, passed to `ask-minimax-run --effort`. Any other value exits 1. |
 | `--project` | current repo root | Repo to `cd` into before launching. |
 | `--dryrun`, `-n` | off | Print the assembled prompt and the exact launch command; write nothing; launch nothing. |

specs/review-minimax-run.spec.md

@@ -21,7 +21,7 @@ review-minimax-run --worktree <path> [--base <ref>] [--out <findings-file>] \
 | `--max-diff-lines` | 6000 | Diff budget; larger diffs exit 1 with the count |
 | `--max-turns` | 40 | Sub-session turn cap |
 | `--timeout` | 540 | Internal timeout (keeps callers under the harness Bash 600s cap). Why: a longer run invoked synchronously from a skill is killed by the harness with no findings file. |
-| `--m3` | off | Use `MiniMax-M3[1m]` instead of the default `MiniMax-M3.1-Flash-Preview` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
+| `--m3` | off | Use `MiniMax-M3[1m]` instead of the default `MiniMax-M3.1-Flash` (1M window natively, always thinks). No effort is sent unless `--effort` is given. |
 | `--effort <level>` | `max` | Thinking depth `low\|medium\|high\|xhigh\|max`, passed to `ask-minimax-run --effort`. Any other value exits 1. |
 | `--dryrun`, `-n` | off | Print resolved config, materialised-input plan, full prompt, and the exact sub-session command line; create/invoke nothing beyond the scratch dir |