Back to Signal Feed
CodeTracked since May 19, 2026

Rework workspace creation to use optimistic rows in TanStack DB

The PR replaces the separate in-flight workspace-creation sidecar with an optimistic `v2Workspaces` insert flow, so create requests are now represented in the main collection immediately, with completion/error transitions tied to sync state instead of duplicated renderer-side bookkeeping.

TanStack DBv2WorkspacessubmitfailedWorkspaceCreates

What Happened

  • The PR replaces the separate in-flight workspace-creation sidecar with an optimistic `v2Workspaces` insert flow, so create requests are now represented in the main collection immediately, with completion/error transitions tied to sync state instead of duplicated renderer-side bookkeeping.
  • The PR replaces the separate in-flight workspace-creation sidecar with an optimistic `v2Workspaces` insert flow, so create requests are now represented in the main collection immediately, with completion/error transitions tied to sync state instead of duplicated renderer-side bookkeeping.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduces a synchronous fire-and-forget `submit` flow for workspace creation that writes pane layout first, inserts an optimistic `v2Workspaces` row immediately, and relies on synced/unsynced state to drive the UI. It removes the `workspace-creates` Zustand store and manager, adds a minimal `failedWorkspaceCreates` collection for persisted failed inputs, and aligns retry/dismiss behavior to an explicit failure store.

Why Track This

Why It Matters

People using workspace creation in the desktop product should experience faster, more understandable behavior because new workspaces now surface as in-flight rows right away and failed creates stay visible for retry instead of disappearing behind hidden state, which should reduce stalled or confusing create flows. The technical result is that render-side state is now derived from the same collection used for sync and confirmation, while retry paths are centralized through a lightweight persisted failure record. Continue monitoring multi-create recovery after app restart and any 401/reconnect behavior that can delay sync confirmation under real-world network churn.

Impact

People using workspace creation in the desktop product should experience faster, more understandable behavior because new workspaces now surface as in-flight rows right away and failed creates stay visible for retry instead of disappearing behind hidden state, which should reduce stalled or confusing create flows. The technical result is that render-side state is now derived from the same collection used for sync and confirmation, while retry paths are centralized through a lightweight persisted failure record. Continue monitoring multi-create recovery after app restart and any 401/reconnect behavior that can delay sync confirmation under real-world network churn.

What To Watch Next

  • Watch whether TanStack DB becomes a repeated pattern.
  • Track follow-up changes around AI Workflow Automation.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: multi_create_recovery_after_restart, failure_store_desync_with_workspace_collection.
Open Topic TimelineOpen Technical EventOpen Original Sourcemulti_create_recovery_after_restart / failure_store_desync_with_workspace_collection / slow_sync_warning_accuracy / token_refresh_retry_loop_regressions

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

superset-sh/superset PR #4707: feat: optimistic workspace creation + Electric write-sync correctness

Workspace creation now enters the main collection as an unsynced row right away, with retryable failures persisted separately and no longer tracked through the old Zustand manager path.