MiniMax Code is now publicly available as a terminal coding agent whose repository describes it as “An open-source coding agent for your terminal, powered by MiniMax.” That wording on the GitHub repository establishes the project’s own positioning: a command-line agent rather than a standalone model release. At the time captured in the research note, the public repository showed 861 stars, 91 forks, 91 issues, and five pull requests. Those figures describe the repository page at capture, not user adoption, software performance, or commercial demand. An independent Reddit r/LocalLLaMA post also said MiniMax had released the source code for the terminal agent, giving the release event an independent contemporaneous reference.
MiniMax Code centers coding work in the terminal
The documentation describes a workflow that begins with a project in a terminal: MiniMax Code is intended to understand that project, make changes, and run tests. The MiniMax Code README presents that sequence as a product capability, so it should not be read as independently tested evidence of how well the agent completes those tasks. The same README frames the tool as a terminal coding agent that can work with MiniMax, users’ own models, and tools beyond code.
That model choice is a significant part of the stated design. The README says a user may sign in with a MiniMax account or bring an API key and model. It also lists search, plugins, multimodal tools, session management, scripted command-line tasks, MCP, and ACP connectivity among the workflow’s components. The documentation therefore describes a tool layer around project work rather than a claim that a particular MiniMax model alone performs every step. Readers tracking the company’s model work can place this code-facing release alongside EastFrontier’s earlier coverage, MiniMax Unveils M3 Flagship Model With 1 Million Token Context Window, while keeping the repository’s own claims separate from performance evidence.
The release gives developers a public codebase to inspect, but the available materials do not support claims about benchmark position, coding accuracy, cost, enterprise use, downloads, or a competitive lead. The independent Reddit post explicitly held off on benchmark speculation until public technical details and independent tests were available. That restraint is especially relevant because the repository description and README explain functions and installation, not comparative results. The public materials also do not confirm a relationship between MiniMax Code and any specific model release, including M3.1.
Installation paths define the supported MiniMax Code environment
MiniMax’s README sets out several ways to install the command-line tool. It lists shell-installer paths for macOS, Linux, and Windows Subsystem for Linux, plus a Windows PowerShell route. It also provides an npm installation path through @minimax-ai/code@latest. These are documentation-level instructions issued by MiniMax, not an independently verified account of installation success across systems.
The stated Node.js requirements are unusually specific. The README names Node.js 22.19 or later on the 22.x line, Node.js 24.2 or later on the 24.x line, as well as versions 25 and 26. It says the one-command installer does not support Alpine or musl Linux. By publishing these compatibility boundaries, the project makes clear that its installer guidance is not universal across Linux distributions. The documented options also distinguish between the controlled shell installers and the npm route, a practical distinction for users selecting an installation method.
The README’s list of search, plugins, multimodal tools, and session features is paired with its model-choice statement. In practical terms, MiniMax is documenting one terminal interface that may combine coding work with those other tools. It is not documenting a verified result for every available model or provider. That separation matters when comparing a public agent repository with an article such as EastFrontier’s China’s Three Frontier Coding Models in One Week: None Published a Real Benchmark: MiniMax Code’s release adds inspectable software, but no public benchmark score appears in the supplied release materials.
September commits show active work on operational issues
The public source was active during the news window without establishing an exact repository-creation time. GitHub’s commit history groups multiple commits under September 18, 2026, and another under September 19. That confirms public repository activity across those two dates. It does not show that the repository was created on September 18, nor does it supply a precise launch timestamp.
The September 18 entries include fixes described as preserving bash permission policy while scrubbing provider credentials; invalidating retained-context usage after compaction; and testing provider candidates before use while exposing token limits. Another listed change on September 19 addresses installer-owned npm through pnpm shell shims. These labels identify the maintenance subjects reflected in commit messages. They are evidence of ongoing work on the public codebase, not proof that MiniMax Code is secure, private, stable, or superior to another coding agent.
The distinction is important for reading the release accurately. Credential scrubbing in a commit message is narrower than a comprehensive privacy guarantee. A fix involving bash permissions is likewise not a general safety certification. The repository’s visible work does show that provider handling, context accounting, permission policy, and installation behavior were being adjusted in public during September 18–19. It does not justify extrapolating from those revisions to a conclusion about quality, adoption, or model capabilities.
MIT default license applies to first-party code
The README states that “First-party code defaults to MIT,” while also saying that existing file-level and package licenses remain in place. It directs readers to third-party notices and license-status documentation for dependencies and assets. That framing describes a default for MiniMax’s own code, not a single uniform license conclusion for every component in the repository.
For developers evaluating the release, the documentation therefore provides a starting point rather than a substitute for reading the license materials attached to particular files, packages, dependencies, or assets. The source-bounded record supports the MIT-default statement and the preservation of existing licenses; it does not establish a broader legal conclusion. It also leaves open the technical questions that the release pages do not answer, including independent measurements of coding performance and operational behavior across model providers.
MiniMax Code’s public repository, README, and September commit trail together show a released terminal agent with explicit installation guidance, model choice, tool integrations, and continuing source changes. The available evidence is strongest on what MiniMax says the software is and how it is configured. It is deliberately weaker on outcomes: no verified benchmark, user figure, price claim, performance comparison, or specific-model linkage appears in the reviewed materials. That is the appropriate boundary for assessing this open-source release now.