Skip to content

feat: default MiniMax requests to M3.1 Flash - #818

Open
octo-patch wants to merge 2 commits into
rohitg00:mainfrom
octo-patch:feature/upgrade-minimax-m3
Open

octo-patch wants to merge 2 commits into
rohitg00:mainfrom
octo-patch:feature/upgrade-minimax-m3

Conversation

@octo-patch

@octo-patch octo-patch commented Jun 4, 2026 •

Copy link
Copy Markdown

Reason: Make MiniMax-M3.1-Flash the default for new MiniMax configurations and fallback requests while preserving explicitly configured models.

Summary

  • Use MiniMax-M3.1-Flash in provider detection, fallback resolution, onboarding, and the environment example.
  • Document MiniMax-M3 as an explicit alternative; saved legacy and custom model identifiers retain their existing precedence and are sent unchanged.
  • Exercise real configuration loading and provider factories through mocked HTTP transport for compression, summaries, saved configuration, custom and regional endpoints, compatible requests, and fallback selection.
  • Merge current main into this existing branch without rewriting its published history.

Validation

  • Passed: npm test -- test/minimax-provider.test.ts test/fallback-model-resolution.test.ts test/fetch-timeout.test.ts --maxWorkers=2 — 48 tests across 3 files.
  • Passed: npm run skills:gen, npm run skills:check (17 skills), and git diff --check.
  • Ran npm run docs:sync; no generated changes remain. Its test-count calculation is incomplete because the full suite cannot be collected with the available dependencies.
  • Local tests use Node 22.23.2 and read-only cached packages compatible with the manifest, including Vitest 4.1.10 and SDK 0.100.1. The repository does not commit a lockfile.
  • Incomplete: npm run build cannot start because tsdown is unavailable. Full-suite collection fails on missing iii-sdk and other uncached dependencies; npm run docs:check consequently cannot compute the test count. Full tests and build are not claimed as passing. New heavy setup is paused by the shared resource gate (approximately 60.5 GiB available versus the required 110 GiB). The queued light install was canceled before it started after compatible focused-test caches were located.
  • All request tests use mocked transport; no paid inference was performed.
  • At head 2b6d240b37ba07855f4980518b4f0f560785efb1, upstream CI and Release gate report action_required. Vercel reports a team-authorization failure. These external gates have not validated the patch.

The request shape keeps thinking and effort unset on the native MiniMax path, allowing the documented Flash defaults. The existing single-turn text provider interface is unchanged.

Reference: https://platform.minimax.io/docs/api-reference/text-anthropic-api.md

Summary by CodeRabbit

  • New Features

    • MiniMax now uses MiniMax-M3.1-Flash as the default model.
    • Existing explicit model selections, including MiniMax-M3, remain supported.
    • Custom and regional MiniMax endpoints continue to be recognized.
  • Documentation

    • Updated setup guidance and provider documentation to reflect the new default and override options.
  • Tests

    • Expanded coverage for MiniMax configuration, requests, endpoints, model selection, and fallback behavior.

- Set MiniMax-M3 as default in src/config.ts and src/providers/index.ts
- Update onboarding label to MiniMax-M3
- Update .env.example sample to MINIMAX_MODEL=MiniMax-M3
- Keep MiniMax-M2.7 and MiniMax-M2.7-highspeed as supported alternatives
- Refresh provider docstring to describe M3 support (up to 128K output)
- Update unit tests to use MiniMax-M3

Signed-off-by: octo-patch <octo-patch@github.com>
@vercel

vercel Bot commented Jun 4, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the rohitg00's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jun 4, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: fcb5fce5-2c7c-49cd-9aeb-c07c31b2031a
📥 Commits

Reviewing files that changed from the base of the PR and between d5b66f1 and 2b6d240.

📒 Files selected for processing: 8
  • .env.example
  • README.md
  • src/cli/onboarding.ts
  • src/config.ts
  • src/providers/index.ts
  • src/providers/minimax.ts
  • test/fallback-model-resolution.test.ts
  • test/minimax-provider.test.ts
🚧 Files skipped from review as they are similar to previous changes: 2
  • src/providers/minimax.ts
  • src/cli/onboarding.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

📝 Walkthrough

The default MiniMax model changes to MiniMax-M3.1-Flash in configuration and onboarding. Explicit model settings remain supported. Documentation and tests are updated to cover the default, overrides, endpoints, and request serialization.

Changes: MiniMax Default Model Update

Layer / File(s) Summary
Set the default model
.env.example, src/cli/onboarding.ts, src/config.ts, src/providers/index.ts
The environment example, onboarding label, configuration fallback, and provider default now use MiniMax-M3.1-Flash.
Document and validate model selection
src/providers/minimax.ts, README.md, test/fallback-model-resolution.test.ts, test/minimax-provider.test.ts
Documentation describes the default and override options. Tests cover fallback resolution and request serialization across model, endpoint, and configuration variants.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Feature

Suggested reviewers: rohitg00

Merge Risk: ⚪ Minimal · up to 2b6d2

The new default uses a documented MiniMax model, while explicit model selections remain available. No issue identified here prevents merging after normal checks.

Pre-merge checks: Passed 4 · Failed 1

Failed Failed checks: 1 warning

Check name Status Explanation Resolution
Docstring Coverage Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 6 files. (2 skipped: 2 … Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed Passed checks: 4 passed
Check name Status Explanation
Title check Passed The title clearly and concisely describes the main change: MiniMax requests now use MiniMax-M3.1-Flash by default.
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 6 files. (2 skipped: 2 unsupported.)

Resolution

Write docstrings for the functions missing them to satisfy the coverage threshold.

  • Fix all pre-merge checks with AI
✨ Finishing Touches: 💡 1
🛠️ Fix failing CI checks: 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/providers/minimax.ts`:
- Line 14: Update the docblock in src/providers/minimax.ts that documents
MAX_TOKENS so the default shown matches runtime/config defaults (4096); change
the text "MAX_TOKENS — max output tokens (default: 800; ...)" to "MAX_TOKENS —
max output tokens (default: 4096; MiniMax-M2.7 needs ≤800, MiniMax-M3 supports
up to 128K)" so it aligns with src/config.ts and .env.example.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2d40a252-9704-43b3-84ed-3cc3bfe2941f

📥 Commits

Reviewing files that changed from the base of the PR and between 334e5ad and d5b66f1.

📒 Files selected for processing (8)
  • .env.example
  • src/cli/onboarding.ts
  • src/config.ts
  • src/providers/index.ts
  • src/providers/minimax.ts
  • test/fallback-model-resolution.test.ts
  • test/fetch-timeout.test.ts
  • test/minimax-provider.test.ts

Comment thread src/providers/minimax.ts Outdated
* MINIMAX_MODEL — model name (default: MiniMax-M2.7)
* MAX_TOKENS — max output tokens (default: 800; MiniMax-M2.7 needs ≤800)
* MINIMAX_MODEL — model name (default: MiniMax-M3; MiniMax-M2.7 / MiniMax-M2.7-highspeed also supported)
* MAX_TOKENS — max output tokens (default: 800; MiniMax-M2.7 needs ≤800, MiniMax-M3 supports up to 128K)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix the MAX_TOKENS default in the provider docblock.

Line 14 says default is 800, but runtime/config defaults are 4096 (see src/config.ts and .env.example). This can mislead operators during setup.

Proposed patch
- *   MAX_TOKENS       — max output tokens (default: 800; MiniMax-M2.7 needs ≤800, MiniMax-M3 supports up to 128K)
+ *   MAX_TOKENS       — max output tokens (default: 4096; MiniMax-M2.7 needs ≤800, MiniMax-M3 supports up to 128K)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
* MAX_TOKENS — max output tokens (default: 800; MiniMax-M2.7 needs ≤800, MiniMax-M3 supports up to 128K)
* MAX_TOKENS — max output tokens (default: 4096; MiniMax-M2.7 needs ≤800, MiniMax-M3 supports up to 128K)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/providers/minimax.ts` at line 14, Update the docblock in
src/providers/minimax.ts that documents MAX_TOKENS so the default shown matches
runtime/config defaults (4096); change the text "MAX_TOKENS — max output tokens
(default: 800; ...)" to "MAX_TOKENS — max output tokens (default: 4096;
MiniMax-M2.7 needs ≤800, MiniMax-M3 supports up to 128K)" so it aligns with
src/config.ts and .env.example.

Signed-off-by: octo-patch <266937838+octo-patch@users.noreply.github.com>
@octo-patch octo-patch changed the title feat: upgrade MiniMax default model to M3 feat: default MiniMax requests to M3.1 Flash Oct 20, 2026

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 Devin Review: 1 flag

Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

Devin Review

This branch has not been deployed

No deployments
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