Anthony Tafoya
f7a135ec61
## What changed - Use V2 discovery inventories for plugin MCP contributions when supplied, including empty or failed inventories; retain legacy discovery when no V2 snapshot is supplied. - Merge plugins by canonical identity, using cloud metadata and enablement for remote plugins and attaching executor installations only when versions match. Preserve configured executor-local plugins and executor enablement when cloud data is unavailable. - Keep installation order stable across refreshes and run merged MCP declarations on the first retained executor installation while preserving attribution for the others. - Carry local and remote identities through selected-plugin snapshots, skill attribution, and active-plugin telemetry. Track disabled plugin IDs alongside disabled roots. - Preserve a complete cloud catalog when a partial refresh arrives, and cap tool-description plugin attribution at 1,024 bytes while retaining all plugin associations. ## Testing Add coverage for catalog parsing and reconciliation, enablement and discovery-mode selection, installation refresh ordering, executor-specific MCP normalization, selected-plugin snapshots, and bounded UTF-8 attribution text. GitOrigin-RevId: a8ad352de6a2b8dc4bfd1ff6a5c62ee8ed1d1664
Codex MCP runtime
This crate manages Codex's MCP connections, tool calls, and their captured authority.
Sandbox request metadata
An MCP server advertises the experimental codex/sandbox-state capability to
receive sandbox metadata on tool calls. The deprecated capability name
codex/sandbox-state-meta opts into the same contract during migration.
Codex supplies these entries in the request's _meta object:
| Key | Value |
|---|---|
codex/sandbox-state |
Opaque policy to pass to codex sandbox --sandbox-state-json. |
codex/sandbox-state-meta |
An identical copy of that policy under the deprecated name. |
codex/sandbox-launcher |
When available, an object with an absolute codexExecutable path to a verified full Codex CLI on the MCP server's host. |
Use the launcher path to invoke sandbox --sandbox-state-json with the entire
state value serialized as one argument, followed by -- and the command to run.
The state contains neither launcher discovery data nor deprecation messages.
Preserve unknown policy fields by forwarding the original value rather than
deserializing and reconstructing it. The two state names are aliases, not separate
policies; new consumers should prefer codex/sandbox-state.
Launcher metadata is currently available only for local stdio servers. An HTTP endpoint, including loopback, or a remote executor does not establish a shared filesystem with the harness. Codex omits the launcher when its path is unknown, not representable as UTF-8, or fails the cached capability probe. Absence does not authorize a PATH search or unsandboxed fallback. Servers that require a launcher must fail closed or require an explicit operator opt-out.
The state and launcher describe the issuing call. Retain both when starting a
long-lived subprocess or caching policy-bound results; reject changed authority
before reusing them. Tool arguments supplied by the model are not authority.
See sandbox_metadata.rs for the wire types and
binding.rs for execution-environment selection.