Summary

Workspaces created by the CLI can appear in superset workspaces list and MCP workspaces_list, but not appear in the Superset desktop v2 workspace UI.

This looks like a mismatch between the tRPC/cloud list path and the desktop Electric collection path.

Observed behavior

After creating a workspace with the CLI:

superset workspaces create --host <host-id> --project <project-id> --name <name> --branch <branch>

The new workspace is visible through:

superset workspaces list --json

It is also visible through MCP v2 workspaces_list.

However, it does not appear in the desktop UI's v2 workspace list.

Source-level diagnosis

The CLI/MCP list path and desktop UI path are different:

• superset workspaces list and MCP workspaces_list call the cloud/tRPC v2Workspace list path and read from the cloud DB.
• The desktop /v2-workspaces page reads from collections.v2Workspaces, which is backed by Electric sync.

Relevant UI path:

• apps/desktop/src/renderer/routes/_authenticated/_dashboard/v2-workspaces/hooks/useAccessibleV2Workspaces/useAccessibleV2Workspaces.ts
• It reads collections.v2Workspaces, joins v2Hosts, v2UsersHosts, and v2Projects, then filters by active org and current user.

Observed Electric behavior while debugging:

• Electric shape for v2_hosts returned rows.
• Electric shape for v2_users_hosts returned rows.
• Electric shape for v2_projects returned an empty snapshot.
• Electric shape for v2_workspaces returned an empty snapshot.
• Adding cache-buster did not change the result.

So the workspace exists in the cloud list API, but the desktop UI's Electric-backed collections do not receive the corresponding v2_projects / v2_workspaces rows.

Expected behavior

A workspace created by the CLI should become visible in the desktop v2 workspace list, because the CLI-created row is a canonical v2 workspace row and is returned by the cloud/tRPC list path.

If the row is intentionally not sidebar-pinned, that is fine, but it should still appear in /v2-workspaces.

Related issue / PRs

• Getting "Workspace was created but hasn't synced to this device yet" whenever I create new worktree on v2 #3901 reports Workspace was created but hasn't synced to this device yet during v2 worktree creation.
• fix: solve #3901 — bump v2 workspace sync-timeout from 10s to 60s #3902 increases the pending-page sync timeout, but this report is about an Electric shape returning no v2_projects / v2_workspaces rows at all, not just a short timeout.
• feat(desktop): v2 workspace discovery page #3317 introduced the v2 workspace discovery page.
• Add optimistic Electric collection updates #3722 added optimistic Electric collection updates.

Impact

This makes the desktop UI disagree with CLI/MCP list output. It is especially confusing when using the CLI as a workaround for MCP Relay host-mutation failures, because the workspace is created successfully but appears absent in the UI.

Notes

Specific org/host/workspace ids and tokens are intentionally omitted from this public report.