MiniMax Code 2.0 is more than a framework migration. It is a full rewrite of how we own and operate the agent runtime.
OpenCode helped us validate the product quickly. But it is also a complete coding agent product, with its own server, session model, storage, event system, and tool runtime.
Embedding it inside MiniMax Code meant running two runtimes, two session models, and two state machines. Product state lived in one layer, while execution history and tool state lived in another.
Long-running tasks exposed the cost of that split. When a tool runs without output, which layer decides whether it is still alive? After an interruption, which layer restores the task?
Who guarantees that tool calls, tool results, and compacted history remain consistent? Watchdogs and heartbeats can observe events, but they cannot fully understand the internal state of the agent loop.
This is why we rebuilt MiniMax Code around Pi Agent.
Pi gives us a clean, composable agent loop with precise lifecycle boundaries. Models, history, tools, and product policies can be explicitly assembled for every turn.
Pi runs the loop. MiniMax Code owns the session, history, tool state, permissions, and runtime events.
In other words: Pi gives us an Agent Loop, not a second Runtime.
That is the real architectural shift behind MiniMax Code 2.0—and the foundation for more reliable long-running agents.
#MiniMaxCode #PiAgent #AIAgents #AgenticAI #AIEngineering