You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
restarted to 1.99 and all my agents are gone #4763
Quick code triage — this looks like the same UX pattern as #4610 ("after update all my workspaces are gone"). Sharing what I found in case it helps narrow it down. The good news: your data is almost certainly still on disk, not deleted.
The most likely explanation: the app is now rendering the v2 UI, while your v1 workspaces/agents still sit in the v1 SQLite tables. The two surfaces read from completely different storage:
v1 data: local SQLite at ~/.superset/local.db (tables projects, workspaces, worktrees)
When v2 is enabled, the v1 sidebar isn't rendered at all — so the v1 entries look "missing." The toggle is wired up in:
apps/desktop/src/renderer/hooks/useIsV2CloudEnabled.ts — true if you've flipped the experimental switch or your account was created on/after V2_ONLY_USER_CUTOFF (2026-05-15T14:00:00Z, in packages/shared/src/constants.ts:66)
apps/desktop/src/renderer/routes/_authenticated/layout.tsx branches on isV2CloudEnabled
Two things that would confirm/disconfirm this:
Settings → Experimental. If you see a "Try Superset v2" switch and it's on, flipping it off should bring back the v1 sidebar with your workspaces. (Some newer accounts don't see the switch — see below.)
Sanity-check the DB file to prove the data is intact:
ls -lh ~/.superset/local.db
sqlite3 ~/.superset/local.db "SELECT COUNT(*) FROM projects; SELECT COUNT(*) FROM workspaces WHERE deleting_at IS NULL;"
Non-zero counts = data is fine, it's a rendering/mode issue, not deletion.
If you've already accepted the v2 onboarding (or your account is post-cutoff), the path forward is to adopt v1 workspaces in v2 via the V1 import flow — apps/desktop/src/renderer/routes/_authenticated/components/V1ImportModal/ImportWorkspacesPage/ImportWorkspacesPage.tsx. As @jnelken mentioned on #4610, restarting the onboarding flow walks you through importing them; git worktree list will also still show the on-disk worktrees.
Why I didn't open a reproduction PR: the issue body doesn't include the version string clearly (was it 1.9.9?), platform, whether v2 is enabled, or the steps that led to "agents missing" (image attachment in the issue body wasn't accessible to the triage tooling). Without those, any test I wrote would be guessing at which surface is empty. Could you share:
A screenshot of Settings → Experimental (or confirm whether the v2 toggle is on)
Output of the two sqlite3 commands above
The exact version (Settings → About, or Superset.app/Contents/Info.plist)
Once we know whether the v1 rows are still in local.db and which UI is rendering, this either collapses to "import your v1 workspaces" (no code change, docs/UX fix) or splits off into a real regression we can write a test for.
@saddlepaddle for visibility. Looks like an electric bug or a host service bug. Taking a look at this now but please see if next time you can do host service -> restart in the macOS top right tray where the superset icon is
Hi there, we're investigating to lock in an answer for sure but I believe an outage we had with our sync provider had knock-on effects, if any of you end up in a stuck state after command+R please let us know! I'll give a more detailed report as well once I investigate.
Definitely an issue with electric-sql sync outage + updating. Updating had cleared our local cache which then never got refilled because of electric. Terrible bug and I'm very sorry about this.
This PR hardens against future failures of this type, we will always rely on local data first even if not synched. #4785
Same issue. This morning and last night I had an "update to 1.10.something" notification that kept popping up. I updated again this morning and am seeing the same blank screen again.
For those experiencing the same bug, I disabled "Try Superset v2" went back to home, returned to settings, and re-enabled Try Superset v2. Everything is back now.
Activity
marcinhlybin commentedon May 20, 2026
Same issue here. Can't even start new workspace. When going into settings I see skeleton only.
jessedobbelaere commentedon May 20, 2026
Same issue here. I'm on Superset v2 in the experimental mode. Will try to downgrade.
edit: I downloaded the mac .dmg from previous release version from, and that one seems to be working fine 👍
https://github.com/superset-sh/superset/releases/tag/desktop-v1.9.7
Collin128 commentedon May 20, 2026
Mine eventually opened but it took 5 or 6 minutes.
github-actions commentedon May 20, 2026
Quick code triage — this looks like the same UX pattern as #4610 ("after update all my workspaces are gone"). Sharing what I found in case it helps narrow it down. The good news: your data is almost certainly still on disk, not deleted.
The most likely explanation: the app is now rendering the v2 UI, while your v1 workspaces/agents still sit in the v1 SQLite tables. The two surfaces read from completely different storage:
~/.superset/local.db(tablesprojects,workspaces,worktrees)v2_workspaces, etc.)When v2 is enabled, the v1 sidebar isn't rendered at all — so the v1 entries look "missing." The toggle is wired up in:
apps/desktop/src/renderer/hooks/useIsV2CloudEnabled.ts— true if you've flipped the experimental switch or your account was created on/afterV2_ONLY_USER_CUTOFF(2026-05-15T14:00:00Z, inpackages/shared/src/constants.ts:66)apps/desktop/src/renderer/routes/_authenticated/layout.tsxbranches onisV2CloudEnabledTwo things that would confirm/disconfirm this:
If you've already accepted the v2 onboarding (or your account is post-cutoff), the path forward is to adopt v1 workspaces in v2 via the V1 import flow —
apps/desktop/src/renderer/routes/_authenticated/components/V1ImportModal/ImportWorkspacesPage/ImportWorkspacesPage.tsx. As @jnelken mentioned on #4610, restarting the onboarding flow walks you through importing them;git worktree listwill also still show the on-disk worktrees.Why I didn't open a reproduction PR: the issue body doesn't include the version string clearly (was it
1.9.9?), platform, whether v2 is enabled, or the steps that led to "agents missing" (image attachment in the issue body wasn't accessible to the triage tooling). Without those, any test I wrote would be guessing at which surface is empty. Could you share:sqlite3commands aboveSuperset.app/Contents/Info.plist)Once we know whether the v1 rows are still in
local.dband which UI is rendering, this either collapses to "import your v1 workspaces" (no code change, docs/UX fix) or splits off into a real regression we can write a test for.Refs #4610
Kitenite commentedon May 20, 2026
@saddlepaddle for visibility. Looks like an electric bug or a host service bug. Taking a look at this now but please see if next time you can do host service -> restart in the macOS top right tray where the superset icon is
saddlepaddle commentedon May 20, 2026
Hi there, we're investigating to lock in an answer for sure but I believe an outage we had with our sync provider had knock-on effects, if any of you end up in a stuck state after command+R please let us know! I'll give a more detailed report as well once I investigate.
Kitenite commentedon May 20, 2026
Definitely an issue with electric-sql sync outage + updating. Updating had cleared our local cache which then never got refilled because of electric. Terrible bug and I'm very sorry about this.
This PR hardens against future failures of this type, we will always rely on local data first even if not synched.
#4785
Collin128 commentedon May 21, 2026
Same issue. This morning and last night I had an "update to 1.10.something" notification that kept popping up. I updated again this morning and am seeing the same blank screen again.
Collin128 commentedon May 21, 2026
For those experiencing the same bug, I disabled "Try Superset v2" went back to home, returned to settings, and re-enabled Try Superset v2. Everything is back now.