Codex capability diagnosis

Why isn't this Codex plugin showing?

Name the failing surface and paste the smallest loader or availability excerpt. A plugin can be installed yet absent from the active session.

Local redaction. Save only by choice.

What happened?

Paste the first useful error/status or describe the last thing that worked and the first thing that failed.

0 / 32,768

Which capability?

MCP or connector Skill or plugin Browser or Computer Use Auth or permission Not sure

Collect private diagnostics locally

Raw text stays in this browser. Only the sanitized preview is submitted. The diagnosis is not stored unless you explicitly save a private report.

Optional context Improves surface and version boundaries

Codex surface Operating system Recent change Codex/host version Capability/provider name and version

Diagnosis workspace

Not checked

Evidence in.
One useful next step.

Your result appears here after you review and submit the sanitized evidence.

First supported boundary: Waiting for evidence
Next check: Not selected yet
Private report: Not created

Worked example — not your diagnosis Discovery A compact output computed by the current deterministic ruleset. DISCOVERED

Example evidence

The plugin was installed in one project, but Codex Desktop reports plugin not found in the current workspace. No parser or activation message appears.

Result Discovery · DISCOVERED

The earliest supported failure is discovery: Codex is not finding the configured or installed capability in the scope being inspected.

Why this boundary

The evidence reports a missing capability or path before a successful parse, connection, or session exposure is shown.

Next safe check Verify one documented skill location, then start a new Codex session

Separate file placement/discovery from later parsing or task activation without editing multiple skill copies.

Method and limits

A capability chain, not an AI guess

Redacted on this device
Inspectable deterministic ruleset · 15 checkpoints
Saved only when you choose

Deterministic rules over your redacted evidence. What the tool cannot support, it declines to claim.

Inspect the ruleset See published reported cases

Earliest supported layer

Rules distinguish availability, discovery, parsing, configuration, dependency, connection, authentication, registration, exposure, activation, authorization, execution, and persistence.

Evidence before verdict

A rule must meet a deterministic threshold. Conflicting or incomplete evidence becomes partial or unknown; it is not converted into a confident root cause.

No unknown execution

The site does not install capabilities, execute packages, contact private endpoints, edit configuration, or ask for credentials.

Private by explicit choice

A diagnosis is stateless by default. Saved reports use random URLs, expire after seven days, can be deleted immediately, and are excluded from indexing.