Workspaces

Bind several projects into one named product — shared mentions, a cross-project task view, and a Team Map filter.

A product is rarely one repo. A web app, an API, and a mobile client are three projects in the sidebar and one thing in your head. Workspaces make that binding real, so a set of repos becomes an operational unit instead of a pile of ad-hoc links.

Creating one

Two routes:

  • Settings → Workspaces → Create workspace
  • Right-click a group in the projects sidebar → Create workspace…

The sheet shows the projects that actually resolve — with their avatars, colours, and emoji — before you save, so a workspace never comes out empty because a group did not expand the way you expected.

Membership can work two ways:

  • Follow a sidebar group — the workspace changes as the group changes
  • Snapshot — today's members are frozen in place

On a free plan a workspace is limited to a single project; the sheet says so in place rather than failing at save time.

Mentioning another project

Agent Input's @ picker gains a Projects tab.

  • @Backend inserts that sibling project's context into your prompt, without leaving the terminal you are in.
  • @Acme — the workspace itself — expands at send time into one block per member project, with a per-project size cap and an honest truncation line when a repo does not fit.
  • Mentioning a single sibling project retargets file search to that project's root, so @ file mentions reach across the repo boundary too.

The Terminals tab puts workspace members first, because a terminal in a sibling repo is usually what you meant.

Agents can address the whole product

Over links you have already granted, an agent can list the workspace roster, send to a peer in another project, broadcast to all of them, and collect replies from several terminals at once. The permission model does not change — see Read Permissions.

Tasks across the workspace

The Tasks board gains a Workspace view listing every task across member projects, and the assign dialog offers sibling projects' terminals grouped as project · workspace — so handing a task to the API agent from the frontend board is one dialog, not a project switch.

Where a workspace shows up

  • Mission Control cards carry a workspace badge, and a workspace growing or shrinking says so.
  • Team Map gains a workspace chip plus a Show outside toggle for everything beyond it.
  • Adding a folder you already have is caught before you add it — the Add Project dialog warns when the folder is already a project, names which one, and offers to open it instead of creating a second entry sharing a working directory.

Related