Codex app-server provider probe fails on account.planType = "prolite"

What version of Codex CLI is running?

0.121

What subscription do you have?

ProLite

Which model were you using?

gpt-5.4

What platform is your computer?

windows

What terminal emulator and version are you using (if applicable)?

powershell v7

What issue are you seeing?

## Summary

Codex provider initialization fails because the app-server provider probe rejects a valid account payload when account.planType is returned as prolite.

## Environment

• OS: Windows
• Shell: PowerShell
• Date observed: April 21, 2026
• Codex CLI version: 0.121.0

## Error

Codex app-server provider probe failed: Invalid account/read payload: Expected "free" | "go" | "plus" | "pro" | "team" | "self_serve_business_usage_based" | "business" |
"enterprise_cbp_usage_based" | "enterprise" | "edu" | "unknown", got "prolite" at ["account"]["planType"].

## What I observed

• Provider status shows Unavailable
• Models list is empty (0 models available)
• CODEX_HOME is set to C:\Users\User\.codex
• Codex binary path is valid
• Logout/login does not fix it
• Clearing local Codex auth/cache state does not fix it

## Relevant evidence

After fresh login, the local auth state still reflects the account plan as:

chatgpt_plan_type: "prolite"

This suggests the backend/auth layer is returning prolite, but the provider probe schema still rejects that value.

## Expected behavior

If prolite is now a valid plan type, the provider probe should accept it and continue normally.

## Actual behavior

The provider probe fails schema validation on account.planType, which prevents provider initialization and leaves the model list empty.

## Likely cause

A compatibility mismatch between:

• the account payload returned by the auth/backend layer
• the enum accepted by the Codex app-server provider probe

## Reproduction

1. Log into Codex using ChatGPT account auth
2. Open the Providers screen
3. Observe provider status failure
4. See the error referencing account.planType = "prolite"

## Notes

This does not appear to be caused by:

• wrong CODEX_HOME
• wrong Codex binary path
• stale auth state
• duplicate Codex installations

It looks like a client/provider validation issue.

What steps can reproduce the bug?

accessing codex cli Codex app-server provider probe failed: Invalid account/read payload: Expected "free" | "go" | "plus" | "pro" | "team" | "self_serve_business_usage_based" | "business" |
"enterprise_cbp_usage_based" | "enterprise" | "edu" | "unknown", got "prolite" at ["account"]["planType"].

What is the expected behavior?

_No response_

Additional information

_No response_