Launch sets: opening a whole context at once

Most work is not one project. A feature touches the API and the web client. A client day means four repositories. A launch set is a saved name for that group, so you stop reassembling it by hand every morning.

Creating a set

There are two routes, and the first is usually faster.

1. Select the projects in the projects view, then choose Create launch set from the selection toolbar. The set is prefilled with exactly what you had selected.
2. Go to Launch sets and choose New launch set, then tick the projects you want.

What launching does

Launching opens a preview showing what the set will produce before anything is copied: which set, how many projects, which tool, and the generated commands. You pick a target, editor, terminal, or file manager, and optionally a specific tool, then copy the lot with one action.

The tool is resolved exactly as it is for a manual selection, so your global default applies unless a project overrides it. Nothing about a set bypasses your configuration.

wt -d "D:\work\api"
wt -d "D:\work\web"
wt -d "D:\work\admin"
wt -d "D:\work\docs"

Sets worth having

• By service: everything one feature touches, so nothing is forgotten mid-change.
• By client: all the work belonging to one account, for days blocked out per client.
• By ritual: the two or three things you always open first thing.
• By state: everything waiting on review, so you can sweep them in one pass.

Sets are sorted by when you last launched them, so the ones you actually use rise to the top and the aspirational ones sink. The last used time is shown on each card.

When a member is gone

Deleting a project does not break the sets it belonged to. The set reports how many members it can no longer find rather than silently shrinking, so you can decide whether to edit it or leave it.