Overview

Incidents don't fit in a single tab. When you're debugging across two accounts, three namespaces, and a handful of specific keys, you accumulate a layout — certain tabs open in a certain order, specific filters active on specific namespaces, a sidebar expanded to just the right branches. Workspaces capture that whole layout as a named session you can save and restore.

A workspace snapshots: every open tab and its type, which tab is active, the active filter in each namespace, which accounts and namespaces are expanded in the sidebar, and any layout panel state. Nothing about values is saved — values always come fresh from Cloudflare — only the view that got you to them.

How to use it

Once your session looks the way you want, open the workspace menu (or use the command palette) and pick "Save workspace…". Give it a name. The saved workspace appears in the workspaces list; click it any time to restore that exact layout.

  • Save — captures tabs, filters, sidebar state, and layout as a named session.
  • Restore — replaces the current session with the saved layout; unsaved edits in open tabs are preserved where possible.
  • Update — re-save on top of an existing workspace name to refresh the snapshot.
  • Delete — remove workspaces you no longer need.

Tips

  • Use workspaces for long-running projects (promo-launch, user-cleanup) instead of for momentary views — the value is in the return visit.
  • Saved filters are part of the workspace, so a workspace can restore a specific filter in a specific namespace.
  • Combine with multiple accounts — a single workspace can span prod and staging side-by-side.
  • Workspaces live locally in SQLite, so they move with the app, not with your Cloudflare account.