GPTsAppCodex tool diagnosis Free tools. No account.
Menu

Evidence, not issue-count theater

What GPTsApp Doctor knows—and what it does not

The live diagnosis rules can use official source context, but upstream reports never become confirmed incidents or confidence upgrades automatically.

7source-verified method sources
2upstream issue candidates
5human-reviewed incidents
2published incident verdicts

Inspectable ruleset

One upstream precondition, then an ordered capability chain

The public view exposes rule claims and requested evidence, but not regex source, weights, or thresholds that would encourage score-shaped input.

Open machine-readable ruleset
Rules
16
Checkpoints
15
Plain-language signals
53
Version
2026-09-05.21
  1. Precondition Upstream request boundary REACHABLE
  2. 01 Availability ELIGIBLE
  3. 02 Installation INSTALLED
  4. 03 Discovery DISCOVERED
  5. 04 Parsing PARSED
  6. 05 Configuration CONFIG_RESOLVED
  7. 06 Local dependency DEPENDENCY_READY
  8. 07 Connection CONNECTED
  9. 08 Authentication AUTHENTICATED
  10. 09 Registration REGISTERED
  11. 10 Session exposure EXPOSED
  12. 11 Task activation ACTIVATED
  13. 12 Authorization AUTHORIZED
  14. 13 Execution EXECUTED
  15. 14 Persistence PERSISTED

The upstream request boundary is not a live status monitor. It requires a platform-targeted failure plus an independent corroborating observation and never confirms a provider-wide outage from user text alone.

Review state

Collection is not confirmation

  1. CandidateMetadata matched a bounded capability-failure query. It has no root-cause or checkpoint claim.
  2. Source verifiedThe source exists and supports a narrowly written method claim. It still does not prove a user's root cause.
  3. Human reviewedAn environment, ordered checkpoint boundary, source claim, fix, verification, and limitations were checked.
  4. PublishedThe record passed the field-level publication gate and is indexable. Published counts are shown above and change only through operator review.

Behavior level

A document cannot prove runtime compatibility

Open machine-readable manifest
  1. DECLARED
    A first-party source states intended behavior or a supported interface.
  2. PARSED
    A bounded definition or response passed structural parsing.
  3. CONNECTED
    A process or endpoint completed a connection or protocol handshake.
  4. DISCOVERED
    The host discovered or listed the capability.
  5. EXPOSED
    The capability appeared in the active model session.
  6. ACTIVATED
    A representative task selected or triggered the capability.
  7. EXECUTED
    A bounded representative action completed or failed at execution.
  8. VERIFIED
    A fix was followed by a recorded recheck in the same scoped environment.

Live source register

Bounded official context used by the diagnosis

Corpus 2026-09-02.w2-published-2
B · DECLARED current

Official Codex MCP documentation

OpenAI documents that Codex MCP configuration lives in config.toml, can be user- or trusted-project-scoped, is shared by the supported Codex clients, and can be inspected through MCP settings, /mcp, or codex mcp list. OAuth servers can be authenticated with codex mcp login.

Review state
source_verified
Retrieved
Valid until

This documents intended configuration and inspection paths; it does not prove that a submitted server connected or exposed tools.

B · DECLARED current

Official Codex skill-building documentation

OpenAI documents the repository, user, admin, and system locations from which Codex loads skills, and advises restarting Codex when a changed skill does not appear.

Review state
source_verified
Retrieved
Valid until

A discovered or parsed skill is not automatically proven to activate for a representative task.

B · DECLARED current

Official Codex configuration basics

OpenAI documents user-level and project-level Codex configuration layers and how to open config.toml from supported surfaces.

Review state
source_verified
Retrieved
Valid until

The existence of a configuration file does not prove the failing surface read the intended layer.

B · DECLARED current

Official Codex configuration reference

OpenAI provides the current searchable reference for config.toml and requirements.toml fields.

Review state
source_verified
Retrieved
Valid until

The reference can validate a field name or value shape but cannot establish which process or surface loaded it.

B · DECLARED current

Official Codex command rules documentation

OpenAI documents rules for controlling commands outside the Codex sandbox and marks the rules feature as experimental.

Review state
source_verified
Retrieved
Valid until

A rule or approval boundary is not the same as authentication or capability discovery.

B · DECLARED current

Official Codex Windows sandbox guidance

OpenAI documents Windows sandbox permission warnings and advises restarting Codex or rerunning sandbox setup after correcting the listed permissions.

Review state
source_verified
Retrieved
Valid until

This guidance applies to the documented Windows sandbox condition, not every permission or execution failure.

B · DECLARED current

Official Codex developer command reference

OpenAI lists codex mcp and codex plugin as stable management commands and marks codex mcp-server as deprecated in favor of the Codex app server.

Review state
source_verified
Retrieved
Valid until

The command maturity table does not prove that an installed capability is available in a particular active session.

Publication stop condition

Until a candidate has an ordered first failing checkpoint, scoped environment, source-supported claim, bounded fix, verification, and human review, it remains excluded from public Incident and Compatibility pages.

Diagnose your evidence