Workspaces

A workspace is one project: one folder, one repository. Several are open at once, and every open workspace stays live — its shells keep running and its files stay watched whether or not you are looking at it. Switching changes what you see, never what is running.

The segments

The band holds one segment per open workspace, in the order they were added. The focused workspace wears its tinted glyph and its name; every other one is its glyph alone, naming itself in a tooltip. Five segments show — the focused one always among them — and the rest roll into a ··· N card that opens the workspace dropdown.

Click a segment to focus that workspace. ⌥⌘1–9 does the same by number.
Double-click the focused segment's glyph to open the tint picker — the eight tints, nothing else. The tint washes the whole window: the band, the pane tiles, the instruments' branch, the glow.
Right-click a segment for its menu. Close is the last item; it kills nothing — every session born there goes to the shelf, still running.

One rule

Sessions are window-wide; files are workspace-scoped. The Files, Git and Notes tool panes, the document panes and search always show exactly one workspace — the focused one. The band's chips show every session, whichever workspace you are in, unless you flip the session scope to the focused workspace only.

Opening a folder from the welcome page (⌘O) adds a workspace; it never replaces one.

Branches and worktrees

The instruments at the foot of the window state git's facts for the focused workspace: the branch, the worktree, the changes, the sync state, and the shelf while it has rows. Each fact lifts a sheet above itself:

the branch fact lists branches to switch to, or names a new one;
the worktree fact lists the repository's worktrees and creates one — a separate folder per branch, same repo — so you can run agents on several branches at once. The file side follows one worktree; each session keeps its own working directory. A linked worktree's row wears a ✕ under the pointer: click it, confirm, and Fold runs a plain git worktree remove. Never forced — a folder with modified or untracked files is refused in git's own words and stays put. The branch outlives its folder, and the main checkout has no ✕: it is the repository, not a worktree of it.

Fold shells out to the git on your machine for all of it.

Workspaces

The segments

Click a segment to focus that workspace. ⌥⌘1–9 does the same by number.
Double-click the focused segment's glyph to open the tint picker — the eight tints, nothing else. The tint washes the whole window: the band, the pane tiles, the instruments' branch, the glow.
Right-click a segment for its menu. Close is the last item; it kills nothing — every session born there goes to the shelf, still running.

One rule

Opening a folder from the welcome page (⌘O) adds a workspace; it never replaces one.

Branches and worktrees

the branch fact lists branches to switch to, or names a new one;
the worktree fact lists the repository's worktrees and creates one — a separate folder per branch, same repo — so you can run agents on several branches at once. The file side follows one worktree; each session keeps its own working directory. A linked worktree's row wears a ✕ under the pointer: click it, confirm, and Fold runs a plain git worktree remove. Never forced — a folder with modified or untracked files is refused in git's own words and stays put. The branch outlives its folder, and the main checkout has no ✕: it is the repository, not a worktree of it.

Fold shells out to the git on your machine for all of it.

#Workspaces

#The segments

#One rule

#Branches and worktrees

#Workspaces

#The segments

#One rule

#Branches and worktrees

Workspaces

The segments

One rule

Branches and worktrees

Workspaces

The segments

One rule

Branches and worktrees