v2.4.0

Add a repo to a session

Started on frontend and backend, and now the work needs docs too? On a group session, ⋯ → Add a repo… (or ⇧A, the rail's right-click menu, or work add-repo <alias> in a terminal) checks another of your repos out into the session's folder, on the session's branch. Its Claude is told and can use it straight away — nothing restarts — and the Diff tab keeps the session's turns. The session header lists its repos.

Session folders (opt in, experimental)

Set "sessionFolders": true in ~/.work/config.json and every new session is a folder of repos — a single repo's too — so you can add a repo to any of them. The folder is named after its branch with a short id (worktrees/fix-login-a3f9c2/<repo>/), so the same branch name in two projects never shares a folder, and the folder's CLAUDE.md imports each repo's own instead of a generated summary. Sessions you already have keep their folders and instructions, whatever the switch says.

A session keeps its own repo list

New sessions record which repos they hold, and archive, Restore, Fork, clean-up and Move act on exactly those. Sessions from before go on following their group's settings, as they always did. One change you may notice: removing a repo that a live group session uses now asks first (Do it anyway).

Smaller things

• The branch field in New worktree starts empty. The suggested name is shown greyed out — type your own without deleting anything first. Left empty with a prompt, the suggestion is used.
• Warnings reach you. What went wrong while setting up a worktree, restoring a session or adding a repo (a pull that failed, a repo no longer in your config) now shows in the toast, not only in the debug log. Routine lines — a worktree that's already there — no longer read as warnings.
• work list <group> and tab completion know about sessions in the new folders.