Support reliable per-plugin disablement for remote curated plugins

What variant of Codex are you using?

App and CLI

What feature would you like to see?

Codex should provide a supported, reliable way to disable one installed plugin without disabling every plugin.

For example, I should be able to disable openai-templates@openai-curated-remote while leaving plugins such as GitHub or Computer Use enabled:

[plugins."openai-templates@openai-curated-remote"]
enabled = false

Today, individual skills can be disabled with [[skills.config]], but remote-curated parent plugins do not reliably honor enabled = false. The only reliable global switch is features.plugins = false, which removes unrelated plugins as well. That makes a template-only opt-out require maintaining one rule per contributed skill.

Please make per-plugin enablement a first-class, documented setting across plugin sources and Codex surfaces. A disabled plugin should not inject its skills, start its MCP servers, or expose its app/connector; other enabled plugins should remain available. Plugin IDs should be discoverable through the normal plugin list, and the result should apply predictably to fresh App and CLI sessions.

Additional information

Related reports: #28443 documents that remote-curated plugins ignore per-plugin enabled = false; #32513 covers the Default templates bundle specifically; #30967 discusses per-thread capability selection. This request is for a stable user-level per-plugin disable contract, including remote-curated plugins.

Start by tracing plugin configuration and the normal plugin list across the App and CLI entry points, especially handling of remote-curated plugin IDs. Verify that disabling one plugin prevents its skills, MCP servers, and app or connector exposure while other plugins remain available in fresh App and CLI sessions.