Expose installed Codex plugin MCP servers and skills to non-Codex providers #26021

Problem

Codex threads inherit the user's CODEX_HOME, so installed plugins, their MCP tools, and their skills are available (#2168). OpenCode threads do not see them. Plugin tools are bundled MCP servers, so reuse currently means copying each server into opencode.json and symlinking skills/ by hand.

Ask

Add a supported way to discover enabled Codex plugins and expose their portable MCP servers and skills to the active provider. A read-only plugin inventory in Settings would be a useful first step. Automatic registration for OpenCode is the end state.

Notes

• code-review@openai-bundled starts standalone with node server.mjs, CODEX_HOME, and CODEX_MCP_NODE_PATH. Its tools were verified callable outside Codex.
• unified-computer-use@openai-bundled and codex-app-tools@openai-bundled depend on Codex app IPC or the Codex node_repl binary, so they are not portable.
• Related: OpenCode provider: surface MCP servers, LSP servers, and plugins #11398 (OpenCode provider MCP/LSP/plugin inventory, closed not planned), [Bug]: Plugins/Skills not brought over from the codex app #2168 (Codex app plugins in Codex threads, closed completed).

Why reuse

• One install and one auth. Enabling a connector in Codex makes its tools and skills available to every provider, instead of a second copy in opencode.json and a symlink farm.
• Credentials travel with the plugin. Its MCP server already declares auth and env forwarding, so OAuth clients and tokens do not need re-registering per harness.
• Version tracking stays with Codex. The marketplace, version, and install path are managed; a hand-copied entry pins a stale cache path and breaks on update.
• Behavior matches Codex. Same SKILL.md, scripts, and tool surface, so a workflow does not work in one harness and fail in the other.
• No per-connector integration work in T3.