Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Vercel connector cannot recover from revoked or stale OAuth grant after account switch [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20286•Fetched 2026-04-30 06:30:41
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
pdurlejpdurlej
Participants
github-actions[bot]github-actions[bot]pdurlejpdurlej
Timeline (top)
labeled ×5commented ×1

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.

Error Message

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.

Root Cause

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.

Fix Action

Workaround

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

Code Example

401: "Server returned 401: 'Unauthorized. Manual reauthentication required.'"
RAW_BUFFERClick to expand / collapse

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.

extent analysis

TL;DR

The Vercel connector in Codex can be fixed by finding a way to trigger a fresh OAuth flow after switching Vercel accounts or revoking an existing grant.

Guidance

  • Investigate the Codex plugin management system to see if there's an option to reset or clear the existing OAuth grant for the Vercel connector.
  • Check the Vercel connector's documentation to see if there are any specific steps or APIs that can be used to trigger a new OAuth flow.
  • Try clearing the local browser storage for the Codex profile and then reinstalling the Vercel plugin to see if this triggers a new OAuth flow.
  • If the issue persists, consider reaching out to the Codex support team to see if they have any additional troubleshooting steps or workarounds.

Example

No code snippet is provided as the issue is related to the OAuth flow and plugin management.

Notes

The issue seems to be specific to the Codex/Vercel connector OAuth lifecycle, and local Vercel CLI authentication works independently. The provided workaround using the Vercel CLI locally does not repair the Codex Vercel connector.

Recommendation

Apply workaround: Use the Vercel CLI locally for project and deployment operations until a fix is found for the Codex Vercel connector, as reinstalling or re-enabling the plugin does not reliably trigger a fresh OAuth flow.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#logging issue#authentication issue#prompt issue#agent setup#task chaining

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING