-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat(elicitation): Add URL elicitation support. SEP-1036 #994
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
base: main
Are you sure you want to change the base?
Conversation
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.
Pull request overview
This PR implements URL elicitation support (SEP-1036), enabling servers to request user interaction through URLs (e.g., OAuth flows) in addition to the existing form-based elicitation. The implementation includes a new component for displaying URL elicitation requests with security warnings, updates to client capabilities, and comprehensive test coverage.
Key Changes
- Added URL elicitation mode alongside the existing form mode, with distinct handling for each request type
- Implemented security warnings for non-HTTPS protocols and internationalized domain names
- Extended client capabilities to advertise support for both form and URL elicitation modes
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 10 comments.
Show a summary per file
| File | Description |
|---|---|
| client/src/components/ElicitationUrlRequest.tsx | New component for URL elicitation with security warnings, multiple action buttons, and clipboard integration |
| client/src/components/ElicitationTab.tsx | Updated to handle multiple elicitation modes with type guards and render appropriate components |
| client/src/components/ElicitationFormRequest.tsx | Renamed from ElicitationRequest and updated to work with typed form requests |
| client/src/components/tests/ElicitationUrlRequest.test.tsx | Comprehensive test suite covering URL validation, warnings, user interactions, and edge cases |
| client/src/components/tests/ElicitationFormRequest.test.tsx | Updated test imports and types to reflect component rename |
| client/src/lib/hooks/useConnection.ts | Updated client capabilities to include form and url elicitation support, added ElicitationCompleteNotificationSchema |
| client/src/lib/hooks/tests/useConnection.test.tsx | Updated test expectations for new elicitation capabilities structure |
| client/src/App.tsx | Updated to pass all elicitation request parameters including mode, url, and elicitationId |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Summary
Implemented support of URL Elicitation SEP-1036. This bring next changes:
notifications/elicitation/completeto notification tab! This PR does not change behaviour in case URLElicitationRequiredError. The error will only shown in error popup.
Video:
Screen.Recording.2026-01-01.at.20.37.42.mov
Type of Change
Changes Made
Code changes:
ElicitationUrlRequestRelated Issues
Issue: #929
Testing
Tested with python elicitation server
Test Results and/or Instructions
Screenshots are encouraged to share your testing results for this change.
Checklist
npm run prettier-fix)Breaking Changes
Additional Context
I'm not typescript developer, feel free to close or update PR if needed. This changes was done to test url elicitation for rust sdk.