[shyam-stha]

What broke
Connected app accounts were buried inside app cards, making it difficult to distinguish accounts, select team access, or remove duplicate connections. Desktop startup could also begin compiling before bundled runtime preparation finished.

Why
The Add-ons screen had no consolidated account view, and the Tauri development command did not wait for runtime staging.

What changed

• Add a connected-accounts table above the app catalog with account identity, connection date, status, team access, naming, reconnect and disconnect actions.
• Load connection pages automatically, show early results immediately, and preserve rows with timeout/retry handling. Retain compatibility with servers that require per-app account queries.
• Keep connection names in the local Bees profile and pass those labels with exact account IDs to agents; ask for clarification when several accounts could match.
• Group duplicate connections only when provider identity is known, and confirm each disconnect. Connect first and name afterward.
• Make development commands wait for bundled runtime preparation before Cargo starts.

Tested

• npm run check passed using Node 24, including 235 client tests and desktop/hosted UI builds.
• cargo check --manifest-path src-tauri/Cargo.toml passed.
• Live provider-account operations and visual verification remain pending. Connection names are local to this computer, and identity lookup currently covers Gmail and GitHub. Older servers cannot provide all account metadata or disconnect actions.

Companion server PR: https://github.com/Bees-bot/bees-server/pull/74