[ENHANCEMENT] Allow Codex/Claude login on Roo CLI

[ArchimedesCrypto]

Problem (one or two sentences)

Currently only able to use API keys for self provider, would be nice to use OpenAI login or Claude login

Context (who is affected and when)

Users using CLI

Desired behavior (conceptual, not technical)

Login using OpenAI subscription to use Codex models

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I have been looking into this issue and wanted to share some observations and ask a few clarifying questions before proposing a plan.

Current state of the CLI auth:

• The CLI supports API-key-based auth for providers: anthropic, openai-native, gemini, openrouter, vercel-ai-gateway, and roo
• Only the roo provider has an OAuth-style browser login flow (via app.roocode.com)
• All other providers require explicit API keys (via --api-key flag or environment variables like OPENAI_API_KEY, ANTHROPIC_API_KEY, etc.)

Questions about the request:

1. OpenAI subscription vs API access: OpenAI consumer subscriptions (ChatGPT Plus/Pro) and API access are separate products with separate billing. An OpenAI subscription does not grant API access -- you need to set up API keys at platform.openai.com. Is the request specifically about using ChatGPT Plus/Pro subscription credits for API calls, or about a smoother way to configure API keys?

2. OAuth for providers: Neither OpenAI nor Anthropic currently offer a public OAuth flow that third-party CLIs can use to obtain API tokens on behalf of users. Are you envisioning something like a browser-based flow where the user logs into their OpenAI/Anthropic account and grants Roo Code access? This would require those providers to support such an integration, which they do not currently offer.

3. Alternative interpretation: Could this be a request to support OpenAI and Claude models through the Roo Code cloud service (the roo provider)? That way users could log in via the existing browser flow and access OpenAI/Claude models through their Roo Code subscription, without needing separate API keys?

Understanding the exact workflow you are looking for would help me propose the right solution. Please tag @roomote in your response and I will proceed from there.

[ArchimedesCrypto]

@roomote CLI OpenAI ChatGPT Plus/Pro authentication is currently possible in the VSCode extension, it should be extended into the CLI, this is supported in other agent frameworks like OpenClaw or OpenCode. Roo Code CLI should be the same. Claude Code prohibits this actually so we can ignore the Anthropic side.

[roomote-v0]

I have seen your comment and will work on extending OpenAI Codex OAuth authentication to the CLI. The VSCode extension already has this flow via openAiCodexOAuthManager, and the CLI needs equivalent support so users can authenticate with their ChatGPT Plus/Pro subscription.

I will open a PR to share progress. The approach will be:

1. Add openai-codex as a supported CLI provider
2. Add roo auth login-openai / logout-openai / status-openai CLI commands that perform the same PKCE OAuth flow
3. Store credentials in the vscode-shim secret storage so the existing OpenAiCodexHandler works transparently
4. Update run.ts to handle the openai-codex provider without requiring an API key

[roomote-v0]

Opened a draft PR with my attempt at adding OpenAI Codex OAuth to the CLI: #11935

This adds roo auth login-openai / logout-openai / status-openai commands and --provider openai-codex support so users can authenticate with their ChatGPT Plus/Pro subscription from the CLI. Feedback welcome!