chore: refresh llm configs for minimax m2.7 - #1247
Conversation
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis PR updates the Minimax language model version from m2.5 to m2.7 across configuration files and model mappings. Additionally, Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request updates the project's configuration to consistently use the newer Minimax M2.7 large language model across all relevant services and tools. This ensures that all components relying on Minimax are aligned with the latest model version, improving consistency and leveraging the most current capabilities. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
Mesa DescriptionTL;DRRefreshed the canonical Minimax model to What changed?
Description generated by Mesa. Update settings |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the Minimax model version from m2.5 to m2.7 across various configuration files. The changes are consistent, updating the canonical model entry in models.json and derived configs for CLIProxyAPI, OpenClaw, OpenCode, and Pi. The comment in .env.example is also updated to reflect the new model version. The changes are straightforward and correctly implement the intended model version refresh.
|
You do not have enough credits to review this pull request. Please purchase more credits to continue. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
Updates the repo’s canonical Minimax model version and regenerates downstream tool configs so all consumers stay aligned with models.json.
Changes:
- Bump
minimaxinmodels.jsonfromminimax-m2.5tominimax-m2.7. - Regenerate derived configs for CLIProxyAPI, OpenClaw, OpenCode, and Pi to reference
minimax-m2.7. - Adjust
.env.examplecommentary related toOPENCODE_API_KEY.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| models.json | Updates the canonical Minimax model mapping to minimax-m2.7. |
| config/pi/models.json | Updates Pi’s model catalog entry to minimax-m2.7. |
| config/opencode/opencode.jsonc | Updates OpenCode’s local CLIProxyAPI model display mapping to minimax-m2.7. |
| config/openclaw/openclaw.template.json | Updates OpenClaw model list and default primary model to minimax-m2.7. |
| config/cliproxyapi/config.template.yaml | Updates CLIProxyAPI OpenAI-compat provider model mapping to minimax-m2.7. |
| .env.example | Updates the OPENCODE_API_KEY comment (minor clarity opportunity noted). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| # Gateway token for remote mode clients (from kyber: cat ~/.config/openclaw/gateway-token) | ||
| OPENCLAW_GATEWAY_TOKEN=your-gateway-token-here | ||
| # OpenCode API key for minimax-m2.5 access via cliproxyapi | ||
| # OpenCode API key for OpenCode Go access via cliproxyapi |
There was a problem hiding this comment.
The OPENCODE_API_KEY comment no longer mentions which upstream access this enables. Since the local CLIProxyAPI config maps OPENCODE_API_KEY to the opencode provider for the minimax-m2.7 model, consider mentioning minimax-m2.7 (or opencode.ai + minimax) here to reduce user confusion when setting secrets.
| # OpenCode API key for OpenCode Go access via cliproxyapi | |
| # OpenCode (opencode.ai) API key for CLIProxyAPI opencode provider (minimax-m2.7 model) |
$(cat <<'EOF'
Refresh the repo's canonical Minimax model entry from to and regenerate the configs that are derived from .
This keeps the generated CLIProxyAPI, OpenClaw, OpenCode, and Pi model definitions aligned with the source-of-truth model map instead of leaving those consumers on the previous version.
I also updated so its OpenCode API key comment matches the configured Minimax model.
'EOF'
)
Summary by cubic
Switch the canonical Minimax model from
minimax-m2.5tominimax-m2.7and refresh all derived configs. This keepsCLIProxyAPI,OpenClaw,OpenCode, andPialigned withmodels.json.minimaxinmodels.jsontominimax-m2.7.minimax-m2.7inconfig/cliproxyapi,config/openclaw(including default primary),config/opencode, andconfig/pi..env.exampleOPENCODE_API_KEYcomment to reference OpenCode Go viacliproxyapi.Written for commit 245dd91. Summary will update on new commits.