Documentary diagnostic · checked 7 October 2026 UTC
Installed/enabled, but the capability is missing: inspect the boundary
Preserve the failure. Inspect source and installed/enabled state. Check only the skill or MCP tool you need in the current session. Then collect actual authorized output—or stop guessing.
Use the four-step diagnostic and its two-line command block →
What the inspection separates
- Source/ref and state:
codex plugin marketplace list --jsonandcodex plugin list --jsonexpose configured sources and installed/enabled entries. Available is not installed. OptionalmarketplaceSourceand absent evidence remain UNKNOWN.installedPathis documented for add, not list. Installed version labels are not loaded-byte fingerprints. Developer commands · codex plugin / marketplace. - Selection/session capability:
/skillsselection inserts context for the next request; explicit$mentioning is documented./mcpshows tools callable in this session;/mcp verboseadds server diagnostics without a documented universal output schema. A configured-server entry or fluent prose does not substitute. Developer commands · /skills / /mcp; Build skills · invocation. - Actual output: a present skill/tool does not prove useful work, intended provider identity or successful authorization. If it fails, separately retain the actual authorized invocation/output/error. Still absent after applicable prerequisites? Preserve a versioned redacted failure for the responsible maintainer/admin rather than cycling reinstall guesses. Plugins · permissions and data sharing.
Qualifications that change the next action
A new CLI session after installation is documented, not a guaranteed repair or universal update/toggle rule. /clear starts a new chat in the same CLI session. The initial model-facing skill-list budget note is not an installation ledger or a documented picker limit. allow_implicit_invocation: false blocks implicit matching, not explicit invocation. These are possible distinctions, not diagnoses. Local standalone-skill controls are not plugin-state workarounds. Plugins · Overview; Developer commands · /clear; Build skills · initial-list note / Optional metadata / local skills.
Local-marketplace project settings and workspace-import enabled state have different owners. Resolve only evidenced mismatches through supported controls; do not bypass trust/policy. Packaging's desktop/ChatGPT cache paragraph is not a universal CLI path recipe. Source/root/state still do not prove loaded bytes. Packaging · Enable or disable a plugin for a repo / How local marketplaces work.
Primary sources and comparison basis
- Developer commands: codex plugin; codex plugin marketplace; Use skills with /skills; List MCP tools with /mcp; Clear the terminal and start a new chat with /clear.
- Plugins: Overview; How permissions and data sharing work.
- Build skills: initial-list note; How ChatGPT and Codex use skills; Optional metadata; Enable or disable local Codex skills.
- Package your plugin: Enable or disable a plugin for a repo; Marketplace metadata; How local marketplaces work.
Four undated primary pages independently retrieved after official-domain search; snippets were not authority. Concrete handles, field limits and state/skill qualifiers were newly inspected relative to the saved guide. Install/new-session and separate selection/quality/access gates were reconfirmed. Changed with evidence: none. No comparable full archived text establishes a rule change. No new conflict was established within this scope; earlier conflicts were not refreshed or resolved.
Not a repair result
No CLI command, installation/toggle/restart, selection/tool invocation, cache inspection, actual output, diagnosis, repair or retest ran. Loaded provenance remains UNKNOWN; all ten actual-host cases remain NOT RUN. No provider/account/workspace/portal, participant or media operation occurred. Reuse the unchanged blank host record or next-evidence worksheet only with actual lawful evidence. No renderer failure is known.
Only this narrow diagnostic earns 7 October. Public ZIP stays 6 October; host/dependency 5 October; annotations 4 October; checkout 3 October; endpoint/recorder 2 October; checker 1 October. Original 0.1.0 source/downloads, seven earlier reports, separate 33/49 offline engineering records and all older dates remain unchanged/unrerun. Developer-first is owner preference; disconnected analytics is unknown use, not zero demand. Research/editorial preparation is separate from Runtime validation, delivery and publication.