Repository navigation
chore: sync MiniMax upstream through c02a275f - #57
Merged
Merged
Conversation
The post-merge Docs review doubled the review's runner time and model tokens without gating anything. Return the workflow to the single review that reads the PR's checks and sends the Feishu card itself, and delete the scripts that only the split reviews used. Native checks also archived the distribution on every run although only manual packaging and releases upload it; archive only when uploading.
* Resume the launcher download across reruns * Use a verified cached launcher download without asking again A complete cached binary from an earlier run went back to the server, which answers 416 and makes curl print an error on a terminal. Verify it first, and remove the whole cache after a successful run.
…#742) * Drop the offline node payload bind on a published upgrade * Escape the payload path in the override test
* Lead the README with install and a first API call * Drop the llms.txt row from the README documentation table
* Separate the node wire protocol from node storage * Show the node as the sender of retention requests
…-AI#746) * Name the model provider boundary and tidy the API references * Match the landing harness test to the Claude Code column * Keep the checkpoint qualification and match the Session diagram to the status table
* Redraw the architecture page as two small diagrams * Keep small diagrams at their natural width and tighten two state diagrams
…#751) * Split Core internals out of the Sandbox Provider protocol * Keep released out of the compute phase diagram
* Give operators one page per task * Fix review findings on the operator pages
* Keep contributor docs to the human workflow * Fix link phrasing and the release flow after review
* Point each reader path at the right pages * Fix openings and link phrasing after review * Refresh translation hashes
* Organize the docs into Docs, API and Extend tabs * List Console server under Operate
* Rebuild the landing hero around the interactive example * Drop the second window bar and keep landing figures readable on phones
* Declare each Harness in one file One harnessconfig.Declaration per Harness is read by Core admission and the Runtime. The generator derives registrations from internal/harnessconfig/*/declaration.go; catalog.json and services/core/internal/engine are deleted. Runtime discovery only narrows the declaration. * Drop the no-op onboarding step and name the declaration file in AGENTS.md * Point docs at the declaration files * Reject widened discovery and drop engine-profile wording * Test heartbeat narrowing and keep onboarding docs exact
* Pass official execution options through to each Harness Core carries the official web search, programmatic tool calling, reasoning, service tier, verbosity and output format values to the Runtime. Each Harness declaration lists the values it supports and Core admission validates against them. Reasoning effort now has one home, reasoning.effort, and migration 000102 moves the Harness-native keys there. * Keep each Harness declaration in one file * Exercise Harness configuration through Claude Code in Web tests * Admit declared execution options in every acceptance test Codex now admits live and cached search, programmatic tool calling and every official reasoning and service-tier value, so the tests that expected the old gates assert admission instead. The Codex declaration accepts the native fast tier and rejects code_mode with Subagent observation. Settings of disabled search configure nothing and stay admitted on every Harness, a declaration must include medium text verbosity, and the protocol version moves to 0.17.0.
* Run Claude Code with its native tools and prompt * Hide unselected MCP tools from Claude * Keep Claude's unattended overrides minimal and documented * Keep Claude's unattended overrides above project settings * Trust the workspace's native Claude settings with the provider key * Remove Claude's Monitor tool and verify declared Skills at init
* Run MiniMax Code with its native tools * Keep native Skill selection on MiniMax Code workspaces * Fix MiniMax Code review findings
The workspace's .minimax, .claude and .agents Skills load as they do in a local run. User roots resolve inside the Session's private HOME.
AGENTS.md states that Core assembles and passes configuration through, that one declaration file joins a Harness, and which native defaults an adapter may override. The Harness protocol, capability page and README link or summarize it.
* Let Codex return structured output Declare structured output for Codex and send the frozen schema as the native outputSchema on every root turn/start. The native strict handling, provider errors and final message text pass through unchanged. * Update tests that used Codex structured output as unsupported
* Let Harnesses own function and MCP URL limits * Admit MCP query URLs in the official-client check
* Let Harnesses own image input rules * Use image inputs every Harness rejects in rejection tests * Match native image rules for Codex and Claude Code
…x-AI#772) * Let Claude combine structured output and tool search natively * Drop admission tests and the field the old Claude rejections needed * Leave ToolSearch and StructuredOutput inventory to native Claude Code
* Generate UUIDs without a secure context crypto.randomUUID exists only in secure contexts. A console served over plain HTTP on a non-loopback address, as the installation guide shows, went blank when Settings → Workspace storage → Select new configuration called it. randomUuid in the client builds a v4 UUID from crypto.getRandomValues and replaces every crypto.randomUUID call and the Executor key ID copy of the same code. Session creation idempotency keys use it too, instead of a non-UUID fallback string. * Use randomUuid in the example application
Core admits a Claude Code stdio MCP cwd against the Environment's declared workspace directory, which is /workspace for hosted Environments. The daemon compared it with the bound root (/environment/workspace in microsandbox), so every hosted stdio server failed runtime preparation. The adapter now checks the same declared directory; the bound root and its /workspace alias are one directory, and native still starts the server there.
* Release idle checkpoints under capacity pressure When waiting placement demand is blocked by a node's full retained slots, Core ends the retention of the node's oldest idle suspended allocation whose Session can cold-restart without loss, then runs the ordinary expiry cleanup. Other checkpoints keep their retention. * Address review of the capacity-pressure release Drop the unreachable compute-state guard, test that a wake request blocks the release, link to the rule from configuration.md instead of restating it, and reword the cold-replacement sentence so it no longer contradicts the new rule.
…Max-AI#795) With active and retained slots both full, pressure could neither suspend an idle allocation (retained full) nor release a checkpoint (active full), so a waiting Session waited for the idle timeout. Pressure now suspends an idle allocation on a full node when its checkpoint can then be released, and the release frees the retained slot on the next pass.
* Remove the upgrade contract * Address review: forward migrations, reinstall guidance, leftovers
* Remove dead Runtime protocol paths * Address review: drop leftover steering code and wording * Wait for the steering frame write before completing the Turn
* Remove dead Core and Web paths * Address review: keep the committed-template reset, drop leftovers
* Derive the sandbox Runtime from the installation * Drop the node-level diagnostic from the Web e2e fixtures * Address review: drop manual node registration and leftovers * Name a node's readiness class from its rollout diagnostic
A failed sandbox node operation logged only its wire error code, so a node whose service account could not open the workspace storage root logged error_code=unconfirmed for every create and nothing else. The node now keeps the local error in its journal, as generation readiness failures already do; only the code crosses the transport.
…AI#803) The offline archive carried the macOS and Windows native installers too (555 MiB of 1.46 GiB). Core already redirects a platform without a local archive to its release asset, so carry only Linux amd64. A catalog without a release base has no URL to redirect to and keeps every archive.
…AI#804) * Download only the selected Harness for self-hosted machines A self-hosted machine downloaded one 300 MB archive per platform holding Node and every Harness, again for every Session. The release now splits each platform into a small base archive (oac-daemon, bundle.json) and one archive per component. The bootstrap fetches the base and starts oac-daemon install, which downloads Node and the selected Harnesses after onboarding, resumes after resets, and keeps verified archives in native-download keyed by version for later Sessions. Core serves the archives as a generic catalog and knows nothing of Harnesses. * Download before claiming and bound stalled native requests
* Reuse finished Environment preparation across Sessions Core computes a key from the Project, initial files and setup operations and calls RestorePreparation/SavePreparation on the Provider. On a hit only finalize runs. The microsandbox helper owns storage, a 24 hour TTL and an 8 GiB bound. The daemon rebinds an identical restored capability installation. * Keep Runtime state out of the preparation archive * Drop a preparation entry that fails to extract and bound its save * Accept preparation fields in strict node frames
…I#809) * Wake placement as soon as capacity or preparation is ready * Hint only existing node lanes on capacity-blocked placement * Hint node lanes only for full nodes and skip direct lanes Placement now hints the lanes only when it failed for capacity, so a generation rollout or reset does not double every lane's scans. A direct lane frees no node slot, and the freed-slot wake is a plain channel send.
* Keep a free slot on full nodes * Give the free-slot inactivity its own limits row * Keep a free slot only where a Session can use it The freed active slot admits no Session when the node's retained slots are full, so the free-slot rule now also needs a free retained slot. SetCompute loads the suspension demand once for both checks.
…iniMax-AI#811) A placement counts as active before its sandbox exists, so a node looked full right after a Session was placed on it. The node lane then ran a free-slot suspension and created the placed Session's sandbox only after it.
…x-AI#812) The Runtime daemon ran its Harness preflights one after another before it connected, and Core found the connected Runtime only on its next 250 ms initialization scan. Both sit on every hosted cold start. The daemon now runs the preflights concurrently and replays their output in declaration order. The gateway signals the first agent-kind declaration of a connection, and the initialization loop scans on that signal; the poll stays as recovery.
…MiniMax-AI#813) A node runs one operation at a time, so a free-slot suspension started while a just-created Session initializes delays its preparation operations behind the suspend. The free-slot rule now also waits while any Session placed on the node has no sandbox or has not finished its Environment initialization.
PostgreSQL jsonb rejects \u0000, so any Harness output with a NUL byte, such as `grep -a` or `/proc/*/cmdline` command output, failed the whole journal batch and the Turn with event_persistence_failed. The journal now stores U+FFFD in place of U+0000 in every string of an observation and of the execution outcome, as decoding already does for invalid UTF-8, and a failed journal write is logged with its Session, Turn and first ordinal.
A request whose client disconnected fails its storage call with the ended request context. The API reported it as a 500 internal_error and logged a persistence failure. The unmapped-error writer now returns nothing once the request context has ended; the request log already records the request as aborted. The Agents and Files mappers reuse the shared writer.
A Turn admitted while its compute was suspended waited for the scheduler's 250 ms tick and 1 s Environment scan throttle after the compute reached running: 0.01–1.24 s, mean 0.66 s over nine resumes on mx2. Saving the running phase now wakes the scheduler the way a freed slot wakes placement.
* Stream Harness reasoning as reasoning Items When the Agent sets reasoning.summary, each Harness reports its native reasoning as `reasoning` Items: the native summary when the Harness produces one, otherwise its native reasoning text. The Runtime sends one `reasoning` frame per native reasoning item (id, status, delta), and Core projects it into a `reasoning` Item with a single summary_text part and the official event sequence (item.added, reasoning_summary_part.added, reasoning_summary_text.delta, reasoning_summary_text.done, reasoning_summary_part.done, item.done). An unfinished Item ends incomplete with the Turn. With reasoning.summary null, the default, no reasoning Items or events appear for root or child Turns. Codex maps null to model_reasoning_summary "none", Claude Code declares only the auto summary, and MiniMax Code no longer emits thinking frames. * Keep native reasoning parts and the part status Each native reasoning part becomes its own summary_text part, reasoning_summary_part.done always carries its nullable status, native reasoning without text is not reported, MiniMax Code child Turns report none, and one validator defines a reasoning frame.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
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.
Synchronize the SandBase fork with MiniMax-AI/OpenAgentCore main at c02a275 using a normal merge. Preserve the fork's creative Runtime tools, E2B packaging, CI selection and deployment workflows. The deployment guide now explicitly describes the upstream installation boundary.
The upstream folds the schema into a new baseline and changes the ledger to oac_schema_version. This source synchronization must not be deployed directly against the existing agents_api_schema_version database. Reinstallation/data transfer requires a separate plan; this PR does not deploy or mutate any database.
Validation: independent review found no source-sync blocking issue; documentation checks (6), CI tests (48), E2B packaging on Python 3.14, and diff checks pass. Full integration CI is required before merge. The subsequent compute-profile branch will merge this synchronized main before its beta integration.