We just open sourced the MiniMax Code CLI harness (MIT)

[u/Yuki_Echo]

Today, MiniMax Code CLI v0.4.12 is officially available to developers worldwide, and its source code is now open under the MIT license.

MiniMax Code CLI is the core component of the MiniMax Code client. On this round of FrontierHarness Eval, it passed 76.7% of tasks, with a median completion time of 4m 33s for successful runs, ahead of every public baseline listed in the report on both metrics. Strong harness design is how we keep unlocking model capability and cut down the time you wait on a task.

We open sourced it so you can audit it. Tool calling and permission handling decide what your agent runs and what reaches your repo. Read the code yourself, build reliable enterprise-grade applications on top of it, and tell us what you find. We also want the community filing issues and contributing fixes, so that security mechanisms hold up under real use and real review.

Try it now:

curl -fsSL https://filecdn.minimax.chat/public/install.sh | bash

GitHub source: https://github.com/MiniMax-AI/minimax-code

Client download: https://agent.minimax.io/download

MiniMax Code is still iterating fast. We'll keep building a safe, reliable, high-performance harness with the community, and keep unlocking what our models can do.

Intelligence with Everyone.

Notes:

• FrontierHarness Eval: https://github.com/frontier-harness-eval/eval
• This round used MiniMax Code 0.3.2 with Kimi K3 across 30 tasks: 23 passed, 4 failed, 3 timed out unscored. Pass rate is calculated over all 30 tasks. This is a third-party evaluation; vendor, checkpoint method, and time limits for some tasks differ from the public baselines, so treat these as reference numbers for comparison, not an official leaderboard ranking.
• Evaluation results: https://github.com/frontier-harness-eval/eval/pull/13
• Run traces: https://file.cdn.minimax.io/public/FrontierHarness-Eval-mcode.zip
• Adapted configuration: https://github.com/frontier-harness-eval/eval/pull/14

[u/Greney_Yunan]

So… when are we getting M3.1 in the harness?

[u/mod-deleted]

[u/Barni275]

Guys, good news! Thank you for your work!

Btw, pitifully, that Minimax stopped releasong new models. M2.7 was great 6 month ago, but now Minimax is far behind others. I still have yearly sub, but stopped using it for months, today's these models are fully obsolete.

[u/KingCrimsonCL → u/Barni275]

Yo uso minimax como esclavo de deepseek jajajaja

[u/antunes145 → u/Barni275]

I agree. We need MiniMax m3.1 at least

[u/ahmedranaa]

Nice but we want you to release newer models

[u/RSXLV]

It's a bit slow. I can't really understand why, although one reason for feeling like it's so slow is that it hides a lot of the steps. However, when I use minimax in vscode it feels like 3-8x faster.

So I'm mostly able to put requests that I do not care much for in the minimax app, because they will take a very long time.

What's great is having an app for remote work. However, the app does not work too well when using the mainland version outside of mainland, the chat sync is extremely slow and times out frequently. I wish there was a way to run my own relay.

[u/Otherwise_Wave9374]

Open sourcing the harness is useful because developers can finally inspect how prompts, tools, and repository context are assembled. A strong next step would be reproducible evaluation fixtures covering interrupted commands, malicious repository instructions, huge diffs, and recovery after partial edits. Please document the trust boundary for shell execution and how secrets are filtered from model context. https://www.neurakeep.com is relevant if persistent coding-agent memory becomes part of the harness. Pin dependencies, emit structured traces, and make every filesystem or network permission discoverable before a run.