[Feature]: Route requests through GPT-5.6 Pro

[fede-oss]

Area

Proxy and routing

What are you trying to accomplish?

Allow OpenCodex to route requests through GPT-5.6 Pro when the user has an eligible authenticated ChatGPT account.

What prevents this today?

GPT-5.6 Pro is not available in the normal OpenCodex/Codex model picker, so it cannot be selected or used as a routing target.

What should OpenCodex do?

• Add an opt-in GPT-5.6 Pro route for eligible authenticated accounts.
• Make it available as an explicit model target, even if it cannot appear in the native model picker.
• Preserve clear errors for unavailable access, account eligibility, quota limits, or session expiry.
• Never silently fall back to another model or account when GPT-5.6 Pro is selected.
• Respect all ChatGPT/OpenAI access controls and service limits.

Possible implementation

Because GPT-5.6 Pro may not be exposed through the standard model-picker/API route, OpenCodex could offer an optional browser-mediated adapter that sends the request through an authenticated ChatGPT web session.

A useful design reference is steipete/oracle, which supports an experimental browser mode for authenticated ChatGPT sessions, while retaining API and manual-copy alternatives. OpenCodex would not need to copy that implementation, but a similar isolated, explicit opt-in integration could provide a path for Pro-only models.

Suggested behavior:

• User explicitly enables and authenticates a dedicated browser-backed provider.
• Requests to gpt-5.6-pro are routed only through that provider.
• The provider exposes session health and actionable reauthentication errors.
• Browser automation remains clearly labeled experimental.
• API routing remains preferred whenever a supported API route is available.

Example usage or interface

ocx provider add chatgpt-browser
ocx login chatgpt-browser
ocx sync

codex -m gpt-5.6-pro "Review this change and suggest improvements."

Alternatives or workarounds

• Use GPT-5.6 variants already available through standard OpenCodex routes.
• Use a supported OpenAI API model when API access is available.
• Use a manual prompt-and-context export for one-off GPT-5.6 Pro consultations.

Additional context

This request is for supported, user-authorized routing of an eligible account. It is not a request to bypass plan restrictions, quotas, model availability, or access controls.

Checks

• I searched existing issues and documentation.
• I removed secrets and personal data.

[github-actions]

_{Automated translation bookkeeping — detected language: unknown.}

[Wibias]

Interesting Idea. I am going to do some research on it, implementation and legal wise and come back to you.

[lidge-jun]

Not planned. The only implementation path this asks for - a browser-mediated adapter driving an authenticated chatgpt.com session - is scripted use of a provider's web UI outside its published API, and shifts agent traffic onto a consumer allowance that was not sold for it. See #757 for the full reasoning. Models reachable through a documented API are the only routes this project will add.

[Wibias]

https://x.com/steipete/status/2083020455049380028

[fede-oss]

Understood, no worries