Wire the in-session provider connect flow to actually connect - #397
Merged
Conversation
Selecting "connect" for an unauthorized provider from the running TUI used to be a stub that told the operator to restart or reconnect via onboarding. It now runs the existing inline OAuth/API-key connect flow, rebuilds the provider catalog from disk plus the Codex/xAI credential stores, and pushes it into the mounted host so the new provider's models are selectable without a restart. OAuth choices are also matched more precisely: a signed-in Codex/xAI account lands in the catalog as a per-account provider name, so "connect" rows need prefix matching, not exact-id matching, to clear after a successful login.
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
onConnectProviderin the running TUI was a stub that told the operator to restart or reconnect via onboardingcodex/<profile>,xai/<profile>) instead of exact-id matching, so a signed-in account correctly clears the rowTest plan