Codex provider rejects valid account/read response with planType "self_serve_business_prolite"

[kostkaro]

Summary

T3 Code fails to detect a healthy Codex installation with:

Codex app-server provider probe failed:
Invalid payload for method 'account/read' during 'decode-payload'

Environment

• T3 Code: 0.0.35
• Codex CLI: 0.150.1
• macOS 26.4.1 (Apple Silicon)
• ChatGPT authentication

codex doctor passes with 0 failures.

Investigation

Manually querying codex app-server returns:

{
  "id": 2,
  "result": {
    "account": {
      "type": "chatgpt",
      "email": "<redacted>",
      "planType": "self_serve_business_prolite"
    },
    "requiresOpenaiAuth": true
  }
}

This appears to be a valid response from Codex 0.150.1, but T3 rejects it during payload decoding before the provider becomes available.

Expected

The provider should accept planType: "self_serve_business_prolite" and treat it as a ChatGPT Business subscription (or otherwise gracefully handle unknown plan types).

Notes

This looks like a schema/enum mismatch rather than a Codex installation problem. Adding support for the new planType value in the app-server schema should resolve the issue.

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Closing as fixed by #8447. The current Codex account schema accepts self_serve_business_prolite and maps that exact plan type to the Business label.

This is part of an automated closure pass based on our investigation.