feat(oauth): support manual pasted callback URL for remote PKCE#129
Open
joeblack2k wants to merge 2 commits intoSoju06:mainfrom
Open
feat(oauth): support manual pasted callback URL for remote PKCE#129joeblack2k wants to merge 2 commits intoSoju06:mainfrom
joeblack2k wants to merge 2 commits intoSoju06:mainfrom
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.
Summary\n- add optional
callback_urlto OAuth complete payload\n- support finishing Browser PKCE flow by pasting callback URL from remote client\n- keep existing local callback server flow intact\n\n## Why\nWhen dashboard is used remotely, browser sign-in often redirects tohttp://127.0.0.1:1455/auth/callback?...on the user machine. That callback cannot reach the server-side listener. This adds a manual paste path like OpenClaw onboarding.\n\n## Changes\n- backend: parse callback URL (code/state) and complete token exchange server-side\n- frontend: input + button in OAuth dialog (browser stage)\n- tests: integration + frontend component tests for manual callback path\n\n## Validation\n-uv run pytest tests/integration/test_oauth_flow.py -q(pass)\n- canary runtime updated and healthy\n