Codex capability diagnosis

Find why your Codex tool isn't working.

Paste the first error or describe what succeeds and what fails. Your browser removes common secrets before the evidence is analyzed.

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 Session exposure A compact output computed by the current deterministic ruleset. EXPOSED

Example evidence

MCP initialization succeeded and tools/list returned the expected tool names, but the tools do not appear in a genuinely new Codex Desktop session. The same capability works in Codex CLI, but it is missing from Codex Desktop.

Result Session exposure · EXPOSED

The earliest supported failure is session exposure: the provider is connected or registering capabilities, but the active Codex session is not making the expected capability available.

Why this boundary

The supplied evidence explicitly separates a working connection/provider listing from a missing Codex-session capability.

Next safe check Compare the provider listing with the target session's visible tools

You already reported the capability missing in a new session of this surface. Do not repeat that check; isolate where the same tool name stops appearing.

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.