Earliest supported layer
Rules distinguish availability, discovery, parsing, configuration, dependency, connection, authentication, registration, exposure, activation, authorization, execution, and persistence.
Codex capability diagnosis
A Codex capability broke after an update?
Include previous/current host and provider versions, surface, OS, last known working state, and the first changed checkpoint.
Local redaction. Save only by choice.
Diagnosis workspace
Not checkedEvidence 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 Persistence A compact output computed by the current deterministic ruleset. PERSISTED
Example evidence
This capability worked before the Codex update. After updating and opening a new session it is no longer visible, while the provider still starts. Previous host version: 1.2.3; current: 1.3.0.
Result
Persistence · PERSISTED
The supported boundary is persistence/regression: the capability is reported working in an earlier session/version or temporarily, then absent or failing after restart, reopen, or update.
Why this boundary
The evidence is comparative rather than a first-install failure. It identifies a change boundary but does not, by itself, prove which product introduced a regression.
Next safe check
Repeat the same successful check after one documented restart or new session
Determine whether the capability state survives the exact restart/session boundary instead of treating a one-time success as durable.
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.
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.