fix(connectors): migrate webui connectorsStore off dropped /api/connections#1631
Draft
github-actions[bot] wants to merge 1 commit into
Draft
fix(connectors): migrate webui connectorsStore off dropped /api/connections#1631github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
…ctions The Agent UI mailbox selector for the Email Triage agent never rendered: the webui connectorsStore still fetched the legacy /api/connections endpoints, which the backend no longer mounts (connections moved to the T-8b /api/connectors framework). The fetch failed, leaving the store with zero connected providers, so the selector's connectedMailProviders.length > 0 render gate never opened. Migrate the store's refresh() onto listConnectors() / listConnectorGrants() (/api/connectors), mapping connected OAuth ConnectorRow entries to the ConnectorInfo shape the store and ChatView consume. Retire the dead /connections* helpers in services/api.ts (all provably unused after the migration) so nothing else regresses onto the unmounted prefix. Closes #1630
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
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.
In the Agent UI, the Email Triage agent's mailbox selector never rendered even with a Google and a Microsoft account fully mail-connected. The webui
connectorsStorestill fetched the legacy/api/connections*endpoints, which the backend stopped mounting when connections moved to the T-8b/api/connectorsframework — so the fetch failed, the store saw zero connected providers, and the selector'sconnectedMailProviders.length > 0gate never opened. After this change the store reads connected providers from/api/connectors, so the selector renders, auto-selects a sole provider, and lets the user switch when both are connected.This unblocks the mailbox-provider selector (#1596/#1600) and multi-inbox triage (#1614) when driven through the Agent UI.
Closes #1630
Test plan
python util/lint.py --allpasses (Black/isort clean; this change touches no Python)cd src/gaia/apps/webui && npm install && npm run test— the newconnectorsStorerefresh()tests passnpm run build— TypeScript compiles (legacy/connections*helpers removed; no dangling references)Follow-up (out of scope here): the issue notes that "triage my inbox" engaged Gmail only when both mailboxes were connected. That is most likely downstream of this bug (a dead selector can never set the session
mail_provider). Once this lands, confirmmail_provider = nullfans out to all connected mailboxes per #1614 — if it still defaults to Gmail, there's a second backend-side gap to file separately.