Fix Cursor MCP auth retry after credential refresh - #20
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cursor reloads a changed user-scoped MCP connection asynchronously. When an agent replaced a Doable credential and retried immediately, the old live transport could still return 401, causing the newly supplied key to be rejected incorrectly and requested again.
This updates the recovery workflow to wait for Cursor's MCP refresh and retry the exact preflight once more before asking for another key. It also adds the stale-transport regression to the acceptance checklist and bumps the plugin to 0.2.6.
Validation:
npm test