I installed MiniMax Code’s terminal agent into an empty home folder and ran it once without logging in. It refused to work, which was expected. The surprise was in the config file it wrote on that first run: one setting, dataContribution, was already switched on.
MiniMax opened the source for its terminal harness, MiniMax-AI/minimax-code, in September 2026, and most comparisons with Claude Code since then have been about tokens and benchmark scores. This one is about the step before that: what lands on your disk, which settings are on by default, and what to change before you sign in.
What I Installed and What Happened
On 18 November 2026 the npm package @minimax-ai/code was at version 0.7.7, newer than the 0.7.2 printed in the public repo’s root package.json. A plain npm install into a scratch folder took about six seconds and pulled 48 packages. My npm held back one install script, for the better-sqlite3 native module, and asked me to approve it. The project’s install guide says that script is needed at runtime and gives the exact flag to allow just those two packages.
npm install -g @minimax-ai/code@latest --registry=https://registry.npmjs.org/ \ --ignore-scripts=false --include=optional \ --allow-scripts=@minimax-ai/code,better-sqlite3
Then I ran the headless mode with a throwaway home folder so nothing touched my real one.
$ HOME=/tmp/mchome mcode --version 0.7.7 $ HOME=/tmp/mchome mcode exec "say hi" mcode exec failed: Sign in to MiniMax to use Agent features. Run `mcode login`, then retry.
That’s the right failure. It didn’t invent an answer or quietly start a guest session.

The Data Folder Holds Your Keys
That one failed run still created ~/.minimax, 6.5 MB on disk. Inside were 13 built-in skills (code review, deep research, website deploy and others), an auth folder with mode 700, a config.yaml with mode 600, a v2/sqlite folder and a shims/rm script. The project’s SECURITY.md is plain about what goes there: login state, provider settings including API keys in config.yaml, and sessions. It tells you to restrict access to every data directory you’ve used and keep them out of Git, including old profiles.
The permissions I saw match that advice, so the risk isn’t the defaults. It’s habits like syncing your home folder to a dotfiles repo or copying a profile to a colleague. If you use the bring-your-own-key route, your provider key sits in that YAML file.
Check This Setting Before You Log In
The config.yaml written on first run had eight lines, and one of them was this.
dataContribution: enabled: true
I couldn’t find the setting explained in the package’s README or changelog, so I can’t tell you exactly what it sends. What I can say is that the public repo’s own source-sync notes list “default-enabled contribution behavior” among the things not imported into the open source tree, and the compiled npm package reads the value with a default of true. In other words, the open repo you can read and the package you install differ on this point.
If you don’t want to contribute data before you’ve read MiniMax’s terms, change it to false before running mcode login. The config parser accepts it as an explicit boolean, and it’s one line.
How the Agent Deletes Files and Asks Permission
Here’s one thing I liked. The first run put an rm shim on the agent’s PATH, and the docs say deletes from a Bash command go to the trash by default on macOS, Windows and Linux. Directory deletion still needs -r, and protected paths stay blocked. You can opt back into real deletes with permission.nativeDelete, and the docs warn that files may then be unrecoverable. If you’ve lost work to a coding agent before, how to stop Claude Code deleting your files covers the same risk on the Anthropic side.
Permissions come in three policies for headless runs: smart, which is the default, full and off. In the TUI you cycle Ask, Auto and Full access with Alt+M, and /permission status shows the current one. SECURITY.md adds that if the automatic classifier is unavailable, the tool should fall back to asking you. It also says permissions and sandboxing don’t replace reviewing untrusted plugins, MCP servers and shell commands. For a checklist on that last point, see how to check a Claude Code mod before installing it. The same habits apply here.
Is the Code Really MIT?
Mostly. LICENSE-STATUS.md says first-party code is MIT, while third_party/sandbox-runtime stays Apache-2.0 and other bundled pieces keep their own licenses. It also says the root MIT license “is not a statement that every file or bundled component is MIT-licensed”. The file records that a September review found the original root license had been copied from Sandbox Runtime with Anthropic’s attribution, and that it was corrected. The desktop app isn’t in the repo at all.
SECURITY.md calls the project a source preview with no committed support period and no response time for security reports. That’s honest, and worth knowing before a team standardizes on it.
Try It on the Bundled Bug First
The repo ships a tiny fixture at examples/clamp, a four-line clamp function that’s wrong on purpose. I ran its tests before giving any agent a chance.
$ node --test --test-reporter=tap not ok 1 - keeps values inside the range ok 2 - clamps below the minimum not ok 3 - clamps above the maximum # tests 3 # pass 1 # fail 2
The bug is a swapped min and max, and the folder’s README asks the agent not to rewrite the tests. Once you’ve logged in, run mcode exec --permission smart --max-steps 20 on a copy of that folder, check the diff and see if the tests now pass without anyone editing them. Then try it on one real ticket of yours. I stopped at the login, so I can’t tell you how it does.
If what you really want is a cheaper model, you don’t need a new harness. MiniMax documents pointing Claude Code at its Anthropic-compatible endpoint, which keeps your existing CLAUDE.md, your prompt-audit cleanup and your Karpathy-style rules. New harnesses are worth installing when you want to read the agent loop yourself, and the learn-claude-code walkthrough is a good companion for that kind of reading. If you’re juggling several agent runtimes already, the Google AX orchestrator guide shows where a declarative orchestrator fits instead.
Whatever you decide, open ~/.minimax/config.yaml before your first login. It’s eight lines, and one of them is a choice MiniMax made for you.
3 comments