You know the pattern: a handful of requests you always open together—login, token refresh, then the protected call you’re debugging—plus a layout you’ve already tuned. Console open. Staging selected. Git sidebar visible. Every time you switch projects, you rebuild that setup by hand.

HarborClient Workspaces capture that whole context. Save your open saved-request tabs and the surrounding UI—panels, sizes, sidebar state, active environment, and theme—then reopen everything with one click.

What are workspaces?

A workspace is a named entry in the Collections sidebar under Workspaces. Each one stores:

• An ordered set of saved collection requests (not unsaved drafts)
• A layout snapshot: which panels are open, their sizes, Collections and Git sidebar expansion, the active environment, and your theme preference

Workspaces live in your local HarborClient registry—same privacy model as the rest of the app. They’re for switching your working context, not for duplicating collections.

If you used Tab Groups before: same idea, clearer name, and the layout is now part of the snapshot. Existing Tab Groups migrate automatically. Portable exports use harborclientExport: "workspace".

Why use workspaces?

• Context switching — Jump between “Auth debugging”, “Billing API”, or “Mobile client” without reopening tabs one by one.
• Layout memory — Restore console, terminal, variables, MCP, and split heights—not just the request list.
• Environment + theme — Opening a workspace can re-select Staging (or whatever you saved) and your preferred appearance.
• Shareable structure — Export and import workspace JSON (request UUIDs plus layout). Full request bodies stay in your collections.

How to create a workspace

From open tabs

1. Open one or more saved requests from your collections. File → New Workspace is enabled only when saved request tabs are open.
2. Arrange the UI the way you want it—panels, footer tools, active environment, and theme.
3. Choose File → New Workspace. HarborClient may ask you to confirm that the workspace will include the current tabs, layout, theme, and environment.
4. Enter a name (for example, “OAuth flow”) and click Create.

From selected requests

1. In the Collections sidebar, multi-select requests (Shift-click or Ctrl/Cmd-click).
2. Open a selected row’s menu (⋯) and choose New Workspace.
3. Name the workspace and create it. HarborClient stores those selected requests and captures your current layout at the same time.

How to open, update, and manage

Open a workspace

In the Collections sidebar, expand Workspaces and click a row. HarborClient opens each saved request in the workspace (without duplicating tabs that are already open) and restores the saved layout, environment, and theme.

By default you’ll see a confirmation dialog the first few times. You can turn that off under Settings → Backup & Restore confirmations if you prefer a one-click open every time.

If a request was deleted or is otherwise missing locally, HarborClient skips it and tells you how many couldn’t be opened. The rest of the workspace still loads.

Save updates

Changed your open tabs or layout? Open the workspace row menu and choose Save. That overwrites the workspace with the currently open saved request tabs and a fresh layout snapshot.

Other useful actions

From the workspace row menu (⋯) or right-click:

• Rename — Change the display name.
• Clone — Duplicate the workspace under a new name.
• Export — Save a portable JSON file.
• Delete — Remove the workspace (it goes to Trash so you can restore it later).
• Color marker — Tag workspaces visually; filter and sort from the Workspaces section header.
• Reorder — Drag rows, or use Move up / Move down when sort mode is Default.

Export and import

Workspaces are portable:

1. Open the row menu and choose Export.
2. Save the JSON file (default name is {name}.json). The file includes harborclientExport: "workspace", the ordered request UUIDs, optional marker, and layout when present.
3. On another machine (or after a fresh install), use File → Import and choose that workspace file.

One important detail: exports reference requests by UUID—they do not embed full request definitions. The matching requests must already exist in your local collections for those tabs to open after import. The layout still restores when it’s included in the file.

Practical workflows

OAuth debugging

Save authorize, callback, and token-refresh requests in one workspace. Open it with Staging active and the console visible so you can watch script output while you step through the flow.

Feature areas

Keep separate workspaces for Users, Orders, and Billing. Give each a different color marker so you can filter the Workspaces list when the day gets busy.

Demo mode

Clone a workspace before a live demo. If you rearrange tabs mid-presentation, reopen the original workspace and you’re back to the known-good setup.

Get started

Open a few saved requests, tune your panels and environment, then choose File → New Workspace. The next time you need that context, one click in the Workspaces section brings it back.

Grab the latest HarborClient from harborclient.com or GitHub Releases, then save your first workspace. Same harbor. Cleaner context switches.