Earliest supported layer
Rules distinguish availability, discovery, parsing, configuration, dependency, connection, authentication, registration, exposure, activation, authorization, execution, and persistence.
Codex capability diagnosis
Record the working and failing surfaces, account/workspace, capability version, and whether the failing session was created after the change.
Local redaction. Save only by choice.
Diagnosis workspace
Not checkedYour result appears here after you review and submit the sanitized evidence.
The capability is visible and works in Codex CLI, but it is missing from Codex Desktop after opening a genuinely new Desktop session with the same workspace.
The earliest supported failure is surface-specific exposure: the capability is evidenced in one Codex surface but not in the failing surface/session.
A working surface makes a universal install/provider failure less likely. The remaining boundary is how the failing surface reads configuration, refreshes capabilities, or exposes them to its active session.
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
Deterministic rules over your redacted evidence. What the tool cannot support, it declines to claim.
Rules distinguish availability, discovery, parsing, configuration, dependency, connection, authentication, registration, exposure, activation, authorization, execution, and persistence.
A rule must meet a deterministic threshold. Conflicting or incomplete evidence becomes partial or unknown; it is not converted into a confident root cause.
The site does not install capabilities, execute packages, contact private endpoints, edit configuration, or ask for credentials.
A diagnosis is stateless by default. Saved reports use random URLs, expire after seven days, can be deleted immediately, and are excluded from indexing.