MiniMax Code Open-Sources CLI, Adds ZCode Migration Plugin Amid Rival's Data Scandal
MiniMax open-sourced its Code CLI under MIT license and released a plugin that migrates only ZCode sessions, hours after ZCode was exposed for uploading entire workspaces including Git history to the cloud, raising questions about competitive timing and data portability in AI coding tools.
On September 18, a GitHub issue revealed that ZCode (by Zhipu AI) was uploading users' complete workspaces — including .git history — to the cloud. Hours later, MiniMax published the source code of its Code CLI (v0.4.12) on GitHub under the MIT license and announced the release. The same day, an "Agent Session Migration" plugin appeared in the MiniMax Code desktop plugin marketplace; it currently supports only ZCode as a migration source.
Timeline
14:50 — ZCode workspace-upload issue made public.
19:25 — MiniMax Code CLI source snapshot imported to GitHub.
20:43 — MiniMax official account announced the open-source release.
The author notes that preparing a full open-source release (source cleanup, license, docs, tooling) usually takes advance work, so the tight sequence suggests the open-source decision predates the ZCode incident, even though the public announcements clustered together.
MiniMax Code CLI v0.4.12
The public repository contains a complete TypeScript project: terminal interactive UI, a headless CLI, an ACP (Agent Communication Protocol) implementation, and distribution tooling. Developers can run the CLI in a terminal to read projects, edit code, and execute tests. Authentication options include a MiniMax account or any model service compatible with OpenAI or Anthropic protocols.
Because the CLI is now open source, enterprises and developers can audit how it invokes tools, manages permissions, and what data might leave the local machine.
Session Migration Plugin (ZCode-Only)
The plugin, version 0.1.4 by developer "Insider", lists three actions: preview migratable ZCode sessions, migrate a selected ZCode session into MiniMax Code, and verify the migrated session. The plugin description states it moves local Agent sessions from other tools into MiniMax Code while preserving conversation history and allowing the task to continue.
The migration logic is not present in the public CLI repository; its exact file access, whether data stays on-device, and whether cloud calls occur during import remain undocumented.
Why Session Migration Matters
Switching AI coding tools often focuses on model capability, speed, and price. The hidden cost is the accumulated context in long-running Agent sessions: requirement background, discarded approaches, tool execution logs, and the rationale for current project structure. Without migration, users must re-explain this context and the new Agent may repeat earlier mistakes.
Migration eliminates that re-onboarding overhead. The platform that can read more rival history formats gains an advantage in poaching heavy users.
Trust and Transparency Concerns
The ZCode controversy underscored that data boundaries in AI coding tools cannot hide behind vague toggles. MiniMax's open-source CLI is a positive step, but the desktop client and the migration plugin — both closed-source — need equivalent inspectability. Users should be told exactly which local files the plugin reads, whether conversion happens entirely on-device, and whether any network requests are made during import.
Reference: Zhipu ZCode scandal: full codebase and Git history allegedly uploaded to cloud — https://mp.weixin.qq.com/s/HDxrfPPF-Mmc2rZgS6AI0w
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.