[BUG] OpenAI - ChatGPT Plus/Pro setup not working

[chdlc]

Problem (one or two sentences)

When I switch to the new provider OpenAI - ChatGPT Plus/Pro and any of its models, saving changes takes me to the Roo Code welcome screen to create an account. If I choose to use Roo Code with no account using that same provider, the "Finish" button does nothing.

Context (who is affected and when)

Likely any user with a valid ChatGPT subscription. Doesn't work by changing to OpenAI - ChatGPT Plus/Pro provider in settings or in the welcome screen.

Reproduction steps

1. Change to OpenAI - ChatGPT Plus/Pro and choose any listed model.
2. Save changes
3. Takes you to welcome screen

---

1. Choose use with no account option in welcome screen
2. Select OpenAI - ChatGPT Plus/Pro provider and any listed model
3. Click FInish button
4. Nothing happens; stays in that screen

Expected result

Saves changes to use the selected OpenAI - ChatGPT Plus/Pro

Actual result

Takes user to welcome screen/If in welcome screen, Finish button does nothing

Variations tried (optional)

Tried in VS Code and Antigravity

App Version

3.41.1

API Provider (optional)

OpenAI

Model Used (optional)

All variants

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I'd like to help with this issue, but I need some clarification to ensure I implement the right solution. Could you please provide more details on the following:

1. Version confirmation: You mentioned version 3.41.1, but openai-codex (ChatGPT Plus/Pro) provider was added in a more recent version. Could you confirm you're using the latest version (4.x+)?

2. Settings screen scenario: When you switch to "OpenAI - ChatGPT Plus/Pro" in the settings and click Save:

   • Do you see the "Sign in to OpenAI Codex" button before saving?
   • Does clicking Save immediately redirect you, or does it happen after a brief delay?
   • After being redirected to the welcome screen, if you check the provider dropdown in the welcome screen, is "OpenAI - ChatGPT Plus/Pro" still selected?

3. Welcome screen scenario: When the Finish button "does nothing":

   • Do you see any error message displayed in red text near the API options?
   • Have you clicked the "Sign in to OpenAI Codex" button first? (This provider uses OAuth authentication rather than API keys)
   • Does the button visually respond to clicking (e.g., ripple effect) but nothing happens afterward?

4. Authentication state: Have you attempted to authenticate with OpenAI Codex via the "Sign in to OpenAI Codex" button? This provider requires OAuth authentication through ChatGPT rather than traditional API keys.

The underlying issue might be related to how the OAuth authentication state flows between the settings and welcome views. Understanding these details will help me pinpoint whether this is a validation issue, state management issue, or OAuth flow issue.

Please tag @roomote in your response with the answers, and I'll be happy to investigate further and propose a fix.

[chdlc]

@roomote Answers below:

1. AFAIK that's the latest version:

• Yes, I signed in before saving.
• Save button quickly redirects me to welcome screen.
• Yes, the provider is still selected.

• No error, nothing at all.
• Yes, I even tried signing in from the welcome screen, but that didn't work.
• Yes, the button responds to click, nothing happens afterwards.

4. Yup.

[roomote]

Thanks for the detailed responses! Based on what you described:

• Signed in via OAuth before saving
• Save button redirects to welcome screen
• Provider still selected after redirect
• Finish button responds to click but nothing happens (no error)

This sounds like a validation or state management issue where the OAuth token state is not being properly recognized after the redirect. I will investigate the welcome screen finish logic and the openai-codex provider validation to understand why the button click is silently failing.

I will open a PR once I have a potential fix.

[roomote]

I've identified the root cause and opened a draft PR with a fix: #10820

Summary: After OAuth completes, postStateToWebview() overwrites the local webview config with the backend state. However, at that point, the backend does not have apiProvider: "openai-codex" set yet because you had not clicked Finish to save it. This causes the welcome screen to stay visible.

The fix adds a useEffect hook that detects when OAuth completes for the openai-codex provider and automatically saves the configuration, following the existing pattern used for Roo provider authentication.

Feedback welcome!

[mrubens]

Can you try 3.41.2? I think we fixed this. Sorry about the bug.

[chdlc]

Can you try 3.41.2? I think we fixed this. Sorry about the bug.

It works! No worries at all, VSCode latest version is still 3.41.1, I missed the latest release in GH though. Only thing is that the documentation is broken.

Dumb question, does it count for the Codex quota?

[mrubens]

Ugh, not sure why VS Code marketplace isn't updating! The publish script succeeded. I'll try a new release now.

@chdlc yes it does count against codex quota.

[chdlc]

Ugh, not sure why VS Code marketplace isn't updating! The publish script succeeded. I'll try a new release now.

@chdlc yes it does count against codex quota.

Thanks for confirming!