Skip to content

Add MiniMax-M3 and MiniMax-M2.7 to benchmark model registry - #402

Open
octo-patch wants to merge 1 commit into
pinchbench:mainfrom
octo-patch:octo/20260728-model-add-recvq7Rt1ZFUKT
Open

Add MiniMax-M3 and MiniMax-M2.7 to benchmark model registry#402
octo-patch wants to merge 1 commit into
pinchbench:mainfrom
octo-patch:octo/20260728-model-add-recvq7Rt1ZFUKT

Conversation

@octo-patch

Copy link
Copy Markdown

Reason: The scheduled OpenRouter benchmark registry lists only the obsolete MiniMax M2.1 and M2.5 models and is missing the current MiniMax-M3 and MiniMax-M2.7 targets.

Adds openrouter/minimax/minimax-m3 and openrouter/minimax/minimax-m2.7 to the default model list in .github/benchmark-models.yml. Both slugs were confirmed against the live OpenRouter model catalog: minimax/minimax-m3 (1,048,576-token context, text/image/video input) and minimax/minimax/m2.7 (204,800-token context, text input). The existing M2.1 and M2.5 entries are retained so historical leaderboard runs stay reproducible.

Checks:

  • Parsed .github/benchmark-models.yml with PyYAML; the file loads cleanly with 35 model entries, including the four MiniMax entries.
  • Reviewed the diff for hardcoded secrets (none found).

@kilo-code-bot

kilo-code-bot Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (1 file)
  • .github/benchmark-models.yml

Reviewed by claude-sonnet-5 · Input: 18.3K · Output: 1.9K · Cached: 113.7K

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.

1 participant