Regression: Canceling OAuth prevents plugin installation; disconnecting provider removes the plugin

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.623.141536 • Released Jul 6, 2026

What subscription do you have?

Plus

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

Previously, provider authentication was optional when installing plugins such as Vercel.

When installing a plugin, the provider OAuth/login window would appear. If I canceled or closed the login flow, the plugin would still install and its skills would remain available. If I later wanted provider-specific features, I could open the plugin and connect my account at any time.

Likewise, if I connected my provider account and later disconnected it, the plugin remained installed and I could continue using its skills. Only authenticated provider features became unavailable.

Current behavior:

1. If I cancel OAuth during installation, the plugin does not install or immediately disappears.
2. If I complete OAuth and later disconnect/sign out of the provider account, the plugin disappears and its skills are removed.

This makes provider authentication effectively required for the plugin itself, even though plugin skills should work without provider account access.

What steps can reproduce the bug?

Scenario 1: Cancel OAuth during installation

1. Open Codex.
2. Install the Vercel plugin.
3. When the provider OAuth/login window appears, click Cancel or close the login window.
4. Observe that the plugin does not finish installing or immediately disappears.
5. Attempt to use the plugin's skills.
6. The skills are not available because the plugin is not installed/visible.

Scenario 2: Disconnect provider after successful installation

1. Open Codex.
2. Install the Vercel plugin.
3. Complete the provider login/OAuth flow.
4. Verify the plugin installs and its skills are available.
5. Disconnect or sign out of the provider account.
6. Observe that the plugin disappears and its skills are no longer available.

I do not have a code snippet because this appears to be a Codex plugin/auth lifecycle issue, not a code execution bug.

What is the expected behavior?

Provider authentication should be optional for plugin skills, as it was previously.

Expected behavior:

• Installing a plugin should install the plugin and its skills regardless of whether OAuth is completed.
• Canceling OAuth during installation should not prevent the plugin from installing.
• If OAuth is canceled during installation, the user should still be able to open the installed plugin later and connect the provider account if they want authenticated features.
• Disconnecting the provider account should not uninstall, hide, or remove the plugin.
• Plugin skills, prompts, documentation, templates, workflows, engineering guidance, and other local functionality should remain available without a connected provider account.
• Only provider-specific actions that require account access, such as deployments, project access, logs, or other authenticated operations, should require OAuth.

Additional information

This appears to be a regression where plugin installation/visibility is now coupled to provider authentication.

Previous workflow:

• Install a plugin.
• Skip OAuth during installation.
• Use the plugin's skills immediately.
• Connect the provider account later from within the plugin if authenticated features are needed.
• Disconnect the provider account later without losing the plugin or its skills.

Current workflow:

• Cancel OAuth → plugin does not install or disappears.
• Disconnect provider after installation → plugin disappears.

This makes optional authentication effectively mandatory for using plugin skills.