Workspaces

2 min read

A workspace is a saved layout: a named set of sessions - which repos, what they are called, their colors, how they launch - that you can bring back in one step. If you run the same crew every morning, save it once and stop rebuilding it.

Saving one

File -> Save Workspace opens a dialog with a name, an optional description, and a checkbox list of your current sessions - include the whole Director or just the sessions that belong together. Saving under an existing name warns before overwriting.

What is stored per session: its display name, repository path, custom color, sort order, which coding agent it ran, and its launch arguments - the recipe for recreating it, not the conversation itself.

Loading one

File -> Load Workspace lists your saved workspaces with a preview of the sessions inside. Load closes the sessions currently in the Director, then restores each saved session while a progress window keeps score. Delete removes a saved workspace; File -> Clear Workspace just clears the Director.

Warning

Loading replaces the current Director - the Director closes your current sessions first. Save the current Director as its own workspace if you will want it back.

Note

A workspace saves a set of sessions, not a formation. Roles and missions are not part of what it stores, so a loaded workspace comes back as ordinary standalone sessions in the right repositories with the right names - you declare the roles and attach the mission again afterwards.