Save the sessions you start every morning

All articles

Most mornings start the same way. Open the Director, start a session in the main repository, another in the website, one in the documentation, give each its name and its color, pick the right agent for each. Five minutes of setup before any work happens, and it is the same five minutes every day.

A workspace is that setup, saved. You name it once and bring the whole set back in one step.

Saving the crew you have open

Get the sessions the way you like them, then choose File, Save Workspace. The dialog asks for a name, an optional description, and gives you a checkbox list of the sessions you have open. Take all of them or only the ones that belong together. Saving under a name you already used warns you before it overwrites.

For each session it keeps the recipe for starting it again:

  • Where. The repository path.
  • What it is called and how it looks. The display name, your custom color and its place in the order.
  • How it runs. Which coding agent it ran, and the launch arguments it was started with.

It keeps the recipe, not the conversation. A loaded session starts fresh in the right place.

Bringing it back

File, Load Workspace lists your saved workspaces with a preview of the sessions in each. Choose one and press Load. The Director closes the sessions you have open, then starts each saved one while a progress window keeps count.

That close is the part to respect. Loading replaces what is in the Director, so if you will want the current set again, save it as a workspace of its own first.

It checks before it closes anything

A workspace saved months ago can name a worktree you have since removed. If the Director found that out halfway through loading, you would be left with half a workspace and none of the sessions you had.

So every saved session is checked first: that its repository folder is still there, and that it names an agent this Director can run. If any of them fails, nothing is closed. You get a message naming the workspace, saying your sessions are untouched, and listing each problem.

What it does not bring back

A workspace saves a set of sessions, not who leads whom. Roles and missions are not part of what it stores, so a loaded workspace comes back as ordinary sessions in the right repositories with the right names. If you run a team with a lead and workers, declare the roles and attach the mission again after loading.

A few to keep

  • One per kind of day. A product day and a website day rarely need the same repositories.
  • Clear before you switch. File, Clear Workspace closes every session in the Director and saves nothing.
  • Delete the ones you stopped using. The load list has a Delete button for each.

Your saved workspaces are kept by your Gateway rather than on the machine. The full detail is on the Workspaces page of the docs.

Talk to usBook a 20-minute call