Skip to content

Workspaces

One branch, cut as a git worktree in every repository you picked, all under one folder.

A feature that spans three services should not mean three checkouts, three terminals and three places to lose track of. A workspace is all of them, cut once: one branch, checked out as a git worktree in every repository you picked, all under one folder.

on disk
~/.meshvy/payments-revamp/
  api/     → repo “api” on payments-revamp
  web/     → repo “web” on payments-revamp
  worker/  → repo “worker” on payments-revamp

Creating one

⇧⌘N, then one step: name the workspace, pick the repositories it spans, and choose the base branch to cut from. Meshvy cuts the same branch in each of them. Another branch means another workspace — a workspace is the branch, so there is nothing to switch inside one.

⇧⌘O adds repositories to a workspace that already exists; each new one is cut from its own base at that moment.

They are worktrees, not copies

Every checkout is a real git worktree registered inside your own repository. Nothing is cloned, nothing is moved, and your existing checkout stays exactly where it is — you can keep working in it while agents work in the worktree.

That also means they are not ordinary folders. Deleting one with rm leaves your real repository pointing at a checkout that no longer exists. Hand them back through Meshvy, or with git worktree remove.

The workspace node

The workspace is a node on the canvas, and the parent of everything else on it. It names the branch, hosts the orchestrator’s Claude Code session in its own body — the working directory is that folder — and shows a chip per repository, marked when that one has uncommitted work.

A repository has no node of its own: its chip is where it lives on the board, because the board is for what runs in a repository. Click a chip for that repository’s changes; right-click it to open an agent, a shell or a browser there.

Archiving and deleting

⌥⌘A, or the box in the toolbar, takes a workspace off the board and out of the switcher without touching a thing on disk. The worktrees stay registered in their repositories and the branch stays where it is. Restore it from Archived in the workspace menu or at the foot of the sidebar, or with Undo on the banner it leaves.