feat(agents-api): qualify MiniMax Code Docker workspace runtime - #703
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MiniMax Code can now run a Docker-managed workspace through the existing Core/Runtime contract, including public Files/Artifacts, cancellation, reconnect and exact-history continuation. Core remains independent of Parsar and uses the existing engine profile, preparation and resource interfaces.
The published native CLI retains its model loop and history in a private control directory. An adapter-owned MCP bridge runs six original workspace tools in the upstream Linux sandbox, keeping workspace files away from privileged configuration and credentials. The image and companion build pin their source provenance; the deployment and onboarding guides describe the boundary. This private transport does not enable public MCP or functions.
Validation: server
make check, focused Go race tests, OpenAPI generation (no drift), published-CLI regression, fixed official SDK 3.13.0/raw HTTP with real Kimi and MiniMax, standalone Core/Docker deployment, Files/Artifacts, cancellation/reconnect, crash recovery and credential/history isolation. Final image native temp/spill tests ran with both network policies; real MiniMax Artifacts and both Core/Runtime crash-recovery suites passed. Seecontracts/agents-api/mcode-workspace-v1.mdfor exact image IDs, evidence and reused initial-image coverage. No database query/schema changes.Known limits: optional public MCP/functions/Subagents and complete usage reporting remain unqualified. After an explicit new recovery prompt, Kimi sometimes issued a new tool call for the interrupted command; automatic/idempotent recovery replay checks passed, and MiniMax passed the same continuation test. No output filter or protocol workaround was added. This qualifies the requested workspace profile, not complete official protocol compatibility.
Fresh independent GPT-6 Astra high review of the complete diff found no blocking issues; its focused race and companion checks passed. Full/live acceptance was run by the implementation owner.