Verdict: MiniMax Code is interesting to us because it did not just show up as another coding chatbot. We tested it against the kind of work Tech My Money actually gives agents. That means recovering context from a messy workspace, reading our operating docs, following WordPress editorial rules, and respecting source-first reporting. It also means holding a lot of instructions without immediately losing the plot.
That is the real review. Our view comes from onboarding MiniMax Code into our own workflow. We wanted to see how MiniMax M3 fits the way we already work with Codex, Claude Code, Cursor-style tools, and local agent skills. The short version is simple: M3’s long context and low price make MiniMax Code useful for training an agent on a house style. It still needs human review, but it is not a toy.
That also puts MiniMax Code in the same practical agent conversation as xAI’s Grok Build coding-agent push, but with a stronger focus on long-context workflow economics.
What we gave MiniMax Code
MiniMax Code is MiniMax’s desktop agent app for macOS and Windows. Instead of judging it only from the product page, we treated it like a new agent joining Tech My Money. We pointed it at the rules that matter here: our WordPress draft workflow, Newsmag and Yoast checks, and source and Via discipline. It also had to handle image-selection rules and production safety notes. We also tested whether it understood the habit of verifying live state before saying something is done.
Those details matter more than a splashy demo. A coding agent can look impressive when it builds a landing page from scratch. The harder test is whether it can read a real operating manual and remember why discovery sites are not default Source/Via. It also has to avoid exposing secrets and keep drafts unpublished. Most of all, it has to understand that Tech My Money is a live production WordPress site rather than a sandbox.
That is where MiniMax Code started to make sense. It is not just about whether the app can edit files. It is about whether the model underneath can absorb a stack of skills and use them consistently. In our case, we trained the agent around `mjwordpress`, `mjanti`, media judgment, Matomo access notes, and the final read-back loop. That loop is what we use before any draft is called ready.
M3 is the model reason it works
MiniMax M3 is the model behind the pitch. MiniMax describes it as a coding and agentic model with MiniMax Sparse Attention and native multimodality. It supports up to a 1 million-token context window, with a guaranteed minimum of 512,000 tokens. The company says M3 is built for long-range coding, long agent tasks, and multimodal understanding.
For our workflow, that context window is not a bragging-rights spec. It is the difference between an agent that can read a few files and one that can understand a real operation. Tech My Money tasks often include source links, WordPress read-backs, image inventories, site-health checks, old notes, skill files, and corrections from Michael. A smaller context can still work, but it starts juggling. M3’s pitch is that it can keep more of that work in view at once.
That showed up most clearly in onboarding. When an agent can hold the rules, the draft state, the user’s correction, and the verification checklist together, it becomes more useful. The model does not need to be magical. It needs to be steady enough to keep following the operating system we gave it.
The price changes how you use it
The economics are the other reason MiniMax Code deserves attention. MiniMax’s pay-as-you-go pricing page lists MiniMax-M3 standard pricing at $0.30 per million input tokens and $1.20 per million output tokens. That applies to requests up to 512,000 input tokens under its permanent 50% discount. Above 512,000 input tokens, the standard tier is listed at $0.60 input and $2.40 output per million tokens. MiniMax attaches availability notes to that tier, and priority service costs more.
That pricing changes the way we think about agent work. With expensive models, you naturally ration context. You paste less. You summarize more. You avoid giving the model the full operating manual unless the task really needs it. With M3, the cost makes it easier to hand the agent the actual rules and see whether it can follow them.
That matters for Tech My Money because our best agents are not just fast writers. They are systems operators. They need to understand why a draft stays unpublished, why image rights matter, and why Source/Via cannot drift. They also need to know why a WordPress write should wait for site guard, and why live verification beats a confident save message. Cheap long context makes that kind of training more practical.
Where MiniMax Code helped us
The strongest use case we saw is structured, repeatable agent work. MiniMax Code fits tasks where the user has a house style, a pile of skills, and a workflow to follow every time. That includes editorial cleanup, source checking, draft repair, codebase exploration, internal scripts, report generation, and agent onboarding.
It also makes sense for multi-file work where the agent needs to read before it acts. A lot of coding tools fail because they jump straight to editing. MiniMax Code is more valuable when it is given the bigger context. That means the docs, the prior mistakes, the file map, the acceptance checklist, and the command outputs that prove whether the work stuck.
The model also helps with the kind of correction Michael gave here. If the user says, “This review should be ours, not theirs,” the agent has to understand that the issue is not a typo. It is an editorial ownership problem. A good coding agent needs that nuance if it is going to work inside a real publication instead of just producing content-shaped text.
Where we still keep it on a leash
MiniMax Code is promising, but our posture is still controlled adoption. A coding agent that can read files, write changes, run commands, and connect to accounts needs strict boundaries. It should not get production secrets, billing access, or broad write permissions by default. First, the workflow has to prove it can ask before risky actions and preserve user changes.
Long context can also create a new problem: the agent may have enough room to overthink. A low token price is useful only if the model uses that room productively. For Tech My Money, the winning behavior is simple: read the right context, make the narrow change, verify it, and stop.
That is why MiniMax Code works best when paired with a strong operating manual. The model gives you room. The skills give it direction. Without the skills, it is just another agent app with a big context window. With the skills, it starts to look like a real assistant for repeatable production work.
Should you use it?
If you already use agents and keep hitting usage limits, MiniMax Code is worth a serious trial. Do not start with your most sensitive repo. Start with a real but safe workload. A documentation pass, an internal tool, a draft cleanup, a source-checking task, or a reversible prototype is enough. Give it your rules and see whether it follows them after the task gets messy.
For our workflow, the model’s biggest value is not raw benchmark bragging. It is that M3 makes long-context, rules-heavy agent sessions cheaper to run. That lets us train the agent on the way Tech My Money actually works, instead of pretending every task starts from zero.
MiniMax Code still has to earn trust task by task. But after testing it inside our own agent setup, I understand why it matters. M3 gives MiniMax Code enough context and pricing headroom to become a useful workflow agent. That is especially true for teams that already have clear skills, checklists, and review habits. The real upside is not replacing judgment. It is making our judgment easier to encode.
Primary materials checked: MiniMax Code, MiniMax M3, and MiniMax API pricing. Review judgment: Tech My Money hands-on onboarding and testing with our own agent skills and workflow.
