PR Summary

Low Risk
Low risk UI/state-management changes that mainly affect connector action disabling/spinners and knowledge-base list rendering; primary risk is minor UX regressions around pending-state cleanup or sorting.

Overview
Fixes connector action race conditions by tracking sync and pause/update per connector (using Set state + onSettled cleanup) so triggering a sync/pause no longer disables controls for other connectors; the connector card now shows a name-adjacent spinner when that specific connector is syncing.

Adds a Connectors column to the knowledge base list that renders registered connector icons with tooltips and enables sorting by connector count.

^{Written by Cursor Bugbot for commit 959b7a8. Configure here.}

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 27, 2026 7:48pm

Greptile Summary

This PR fixes two race conditions in the connectors section of the knowledge base feature and adds a new Connectors column to the knowledge base list view.\n\n- Race condition fix (sync): Replaces the single syncingConnectorId string and global isSyncing flag with a per-connector syncingIds Set, so that triggering a sync on connector A no longer disables the sync button on connector B.\n- Race condition fix (pause/resume): Replaces the global isUpdating flag from useUpdateConnector().isPending with a per-connector updatingIds Set backed by the new handleTogglePause callback, so pausing connector A no longer disables the pause button on connector B.\n- Cleanup consolidation: Both syncingIds and updatingIds entries are now removed in a unified onSettled callback, consistent with the idiomatic React Query pattern for covering both success and error paths.\n- Connectors column: knowledge.tsx adds a Connectors column after Tokens that renders connector icons with tooltips. It filters out unknown registry types gracefully with an em-dash fallback. The server-side connectorTypes array is already deduplicated in service.ts, so the key values in the icon map are safe from duplicate React key warnings.

Confidence Score: 5/5

Safe to merge — all changes are isolated UI state fixes with no data-integrity risk.

No P0 or P1 issues found. The per-connector Set state is implemented correctly with functional updates, server-side deduplication guarantees unique React keys, and the onSettled pattern is now consistent across both sync and update paths. Prior concern about inconsistent cleanup strategy was resolved in the head SHA.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant U as User
    participant CC as ConnectorCard (A)
    participant CC2 as ConnectorCard (B)
    participant CS as ConnectorsSection
    participant TQ as TriggerSync Mutation

    Note over CS: syncingIds = Set{}, updatingIds = Set{}

    U->>CC: Click Sync (connector A)
    CC->>CS: onSync(connectorA.id)
    CS->>CS: addToSet(setSyncingIds, connectorA.id)
    Note over CS: syncingIds = Set{"connectorA"}
    CS->>TQ: triggerSync({knowledgeBaseId, connectorA.id})
    CC-->>U: Sync button disabled for A only

    U->>CC2: Click Sync (connector B) — now allowed!
    CC2->>CS: onSync(connectorB.id)
    CS->>CS: addToSet(setSyncingIds, connectorB.id)
    Note over CS: syncingIds = Set{"connectorA","connectorB"}
    CS->>TQ: triggerSync({knowledgeBaseId, connectorB.id})

    TQ-->>CS: onSettled (connector A)
    CS->>CS: removeFromSet(setSyncingIds, connectorA.id)
    Note over CS: syncingIds = Set{"connectorB"}

    TQ-->>CS: onSettled (connector B)
    CS->>CS: removeFromSet(setSyncingIds, connectorB.id)
    Note over CS: syncingIds = Set{}

_{Reviews (2): Last reviewed commit: "refactor(knowledge): use onSettled for s..." | Re-trigger Greptile}

@greptile

@cursor review