Codex Plugins and ChatGPT OAuth Login

Problem pattern

Typical state:

1. You routed Codex through gpt88.cc with CC-Switch
2. API-key mode uses https://api.gpt88.cc; OAuth mode does not configure an API Base URL
3. The API key is a gpt88.cc sk-... key
4. Model calls work
5. But plugin / app capability is missing or unavailable

This usually does not mean your gpt88.cc API key is broken. It means you are still in API-key model mode while trying to use a product feature that requires ChatGPT OAuth identity.

Why API key mode cannot unlock plugins

API key mode only proves that a request may call a model and consume quota. It does not carry your ChatGPT account session, workspace identity, or plugin authorization state.

Prepare three things first

To restore plugin capability, do not only change the Base URL. You need a working Codex CLI install, a ChatGPT OAuth login, and the correct CC-Switch route if you use CC-Switch.

Install Codex CLI

node -v
npm -v
npm install -g @openai/codex
codex --version

Enable ChatGPT OAuth

codex logout
codex --login

# choose:
# Sign in with ChatGPT

# do not paste a gpt88.cc API key during this flow

During login, choose Sign in with ChatGPT. Do not paste the gpt88.cc API key in this flow.

Enable the CC-Switch OAuth route

1. Open CC-Switch
2. Go to Codex / Routes / route settings
3. Disable the current API-key route if it is active
4. Create a new profile such as chatgpt-oauth
5. Choose ChatGPT OAuth as the auth type
6. Keep the official default base URL
7. Enable the route
8. Save and apply
9. Complete ChatGPT login in the browser
10. Restart Codex and verify plugin visibility

The OAuth profile should use the official default login flow. Do not point the OAuth profile itself athttps://api.gpt88.cc.

Switch to ChatGPT OAuth

The goal is simple: exit API-key login mode and re-enter Codex with ChatGPT OAuth. If the interface keeps asking for an API key, you are still on the wrong path.

Clear environment overrides

Even after switching the visible login flow, environment variables may continue forcing API-key mode. Clear them before restarting Codex.

unset OPENAI_API_KEY
unset OPENAI_BASE_URL
unset ANTHROPIC_API_KEY
unset ANTHROPIC_BASE_URL

Verify plugin recovery

1. Restart Codex.
2. Confirm the session shows a ChatGPT login state rather than only API-key routing.
3. Open the plugin or app area again.
4. If it is still missing, verify that the OAuth route is the active one and that no API-key env vars remain.

Keep two separate profiles

Recommended two-profile setup:

profile: gpt88-api
  purpose: model access through gpt88.cc
  strength: flexible routing, multi-model access, transparent cost view
  limit: no ChatGPT OAuth plugin identity

profile: chatgpt-oauth
  purpose: Codex plugins / apps / ChatGPT account features
  strength: plugin capability and ChatGPT workspace identity
  limit: usage and permissions follow the official ChatGPT / Codex account system

In practice, keeping one profile for model access and one profile for ChatGPT OAuth avoids a lot of confusion and makes switching intent explicit.

For related setup work, continue with Codex CLI and CC-Switch.