Skip to content

Workspaces

A workspace is a saved tab: one pane arrangement, plus one connection per pane. Open it and every terminal in it comes back in a single tab — the four boxes you always open together, in the layout you always put them in, in one click.

Workspaces are in both editions and need no account. In SSH Ache Teams they can also be shared with your team.

Arrange the panes

Open the workspace menu in the tab bar (or press ⌘K and type Arrange) and pick an arrangement:

PresetShape
Singleone full-width terminal
Two columnsside by side
Two rowsstacked
Main + stackbig left, two right
Main + two belowbig top, two below
2 × 2 gridfour terminals

Applying an arrangement adds empty panes rather than cloning what you're on. Each empty pane shows a searchable picker — choose a saved connection or a local shell, so your machine can sit in the grid next to your servers. Every pane header has a reopen () button for a fresh shell on the same host.

⌘D still splits the current pane the old way, cloning the connection you're in.

Drag a tab into the layout

Drag a tab's pill onto any pane to fold that session into the arrangement. Hovering shows exactly which half it will land in; drop it and SSH Ache offers to save the result as a workspace.

TIP

A moved pane gets a fresh session, so the tab you dragged closes its old one. Anything long-running in it stops — reconnect in place with .

Save it

With at least one pane connected, choose Save as workspace (workspace menu, or ⌘K). Give it a name, optionally a folder — it defaults to Workspaces — and any tags you want to find it by. Saving again from the same tab updates the existing workspace instead of making a second one.

Open it

Saved workspaces sit on the dashboard next to your connections, as their own kind of card — there's deliberately no separate workspaces page. Hit Open all → on the card, or find it in the command palette. Favourite them, tag them and file them in folders exactly like connections.

If a connection in the workspace has since been deleted, that pane opens empty and flagged, and a notice tells you how many are missing — pick a replacement and re-save.

Export & import

Export a workspace to move it to another machine. The file carries the arrangement and its connections, so it's usable on the other end:

  • No password — plain JSON with the arrangement and connections, no secrets.
  • With a password — the whole bundle including secrets, encrypted with AES-256-GCM.

Import auto-detects whether a file is a single connection or a workspace. Connections come back with new ids and the workspace still resolves them, so it survives the round trip.

Team workspaces

SSH Ache Teams only.

Build a workspace on shared connections and the save dialog offers two choices:

  • Team workspace — any connection in it that isn't shared yet is uploaded end-to-end encrypted first, so every member can actually open the same set. It then files itself under Team · <your team>.
  • Just for me — nothing is uploaded. It stays on this device, under Others.

The arrangement itself is stored as an ordinary team record, sealed client-side like any connection — the server holds ciphertext and never learns which hosts the workspace points at. See the security model.

Deleting a shared workspace

Deleting one locally is not a team delete — it comes back on the next sync. Remove it for everyone from the team view.

Next steps

Community edition: open source (Apache-2.0), individual use. Teams app: source-available, free for noncommercial use. Zero-knowledge by design.