fix(tui): thread DaemonApi into init wizard OAuth flow (#1032)#1369
Merged
Aaronontheweb merged 2 commits intoJun 9, 2026
Merged
Conversation
…dev#1032) ProviderStepViewModel was constructing OAuthFlowCoordinator with a null DaemonApi, so the browser OAuth (PKCE) flow in `netclaw init` hit "Daemon API not available" instead of showing the authorization URL. The DaemonApi was already available in InitWizardViewModel — it just was not passed through.
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
netclaw initshowed "Daemon API not available" when selecting a browser OAuth (PKCE) provider auth method (e.g. OpenAI "ChatGPT Subscription (browser)"), whilenetclaw providerworked correctly.InitWizardViewModelreceivedDaemonApi?but did not pass it toProviderStepViewModel, which hardcodednullwhen constructingOAuthFlowCoordinator.daemonApiparameter through so both flows use the same coordinator wiring.Test plan
dotnet buildpassesnetclaw init→ OpenAI → "ChatGPT Subscription (browser)" now shows the full OAuth URL, callback spinner, and redirect-URL paste fallback (screenshot verified)