-
Notifications
You must be signed in to change notification settings - Fork 9
[security] Add MCP elicitation for secure preview token handling #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mattpodwysocki
wants to merge
19
commits into
main
Choose a base branch
from
add-preview-token-elicitation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
19cf40f
Add MCP elicitation for secure preview token handling
mattpodwysocki 2b81c67
Fix: Ensure preview tokens are created as public tokens (pk.*)
mattpodwysocki 0e68743
Fix: Use only public scopes to create public tokens (pk.*)
mattpodwysocki f51feff
Fix: Check client elicitation capability before using elicitInput()
mattpodwysocki ec35e38
Docs: Clarify varying MCP elicitation support across clients
mattpodwysocki b9a2246
Docs: Update elicitation support status for Cursor and VS Code
mattpodwysocki c974bcc
Docs: Add Goose elicitation bug report and documentation
mattpodwysocki ffdc83a
Docs: Link to filed Goose elicitation bug issue
mattpodwysocki 08b2460
Remove redundant Goose bug report file
mattpodwysocki 3c6f8a6
Tests: Add unit tests for elicitation and token storage
mattpodwysocki 90cbd1b
Docs: Confirm Claude Code does not support elicitation yet
mattpodwysocki 1e3e9e7
Add elicitation support to style_comparison_tool
mattpodwysocki 14e54b3
Merge remote-tracking branch 'origin/main' into add-preview-token-eli…
mattpodwysocki 19d3637
Add tk.* guard, HttpPipeline DI, and hosted-endpoint docs for token e…
mattpodwysocki 8f9fcf2
Correct tk.* guard claims and improve the actual create-token failure…
mattpodwysocki 9eaf79f
Add HTTP integration test for elicitation over the real MCP wire prot…
mattpodwysocki ae725b0
Fix race in HTTP integration test harness that caused CI flake
mattpodwysocki 2b3fddc
Fix backwards client list in the no-elicitation-support error message
mattpodwysocki 848963c
Address PR #57 review feedback: useCustomToken fallback and cache-key…
mattpodwysocki File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what happens if the client does not support selection dialog? Is that a possible scenario?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — this was actually a real bug: if the client can't show the selection dialog,
useCustomToken: truewas forcing the same elicitation flow anyway, which then fails the capability check and returns an error — even when a perfectly good cached token already existed. Fixed in 848963c:useCustomTokennow only bypasses the cache when the client actually supports elicitation; otherwise it silently falls back to the cached token (or the existing no-elicitation error if nothing is cached).