Vercel connector cannot recover from revoked or stale OAuth grant after account switch #20286

Summary

The Vercel connector in Codex can get stuck after switching Vercel accounts or revoking an existing OAuth grant. Reinstalling or re-enabling the Vercel plugin does not reliably trigger a fresh OAuth flow. Instead, connector calls continue to fail with a manual reauthentication error.

Environment

• Codex Desktop on macOS
• Vercel plugin: vercel@openai-curated
• Affected connector call: mcp__codex_apps__vercel._list_teams
• Local Vercel CLI authentication works independently, so the issue appears specific to the Codex/ChatGPT connector OAuth lifecycle.

Steps To Reproduce

1. Authorize the Vercel connector in Codex with one Vercel account.
2. Switch to a different Vercel account outside Codex.
3. Disable/remove/reinstall or re-enable the Vercel plugin in Codex.
4. Start a new Codex thread.
5. Call the Vercel connector, for example list_teams.
6. Revoke the stale Vercel authorization and try reconnecting the plugin again.

Expected Behavior

Codex should expose a clear Vercel reconnect flow and start a fresh OAuth authorization when the existing grant is stale or revoked.

After reconnecting, connector calls such as list_teams should use the newly selected Vercel account.

Actual Behavior

The connector can remain stuck and return:

401: "Server returned 401: 'Unauthorized. Manual reauthentication required.'"

Reinstalling or re-enabling the plugin does not appear to initiate a new OAuth flow from within Codex.

Notes

The local Vercel CLI can authenticate and access the intended Vercel account successfully, so this does not appear to be a Vercel account problem.

Local cache cleanup of Codex profile browser storage did not resolve the issue, suggesting the stale or revoked connector grant may be tied to the connector authorization lifecycle rather than local plugin cache.

Workaround

Use Vercel CLI locally for project and deployment operations, but this does not repair the Codex Vercel connector.