Native sessions, worktrees or a manager?

If you can follow the work, answer the questions and review the changes comfortably in your existing sessions, keep that setup. Consider a worktree tool when managing separate checkouts is the recurring chore. Consider a session manager when finding the right session or decision is the recurring chore. These are overlapping choices: claude-squad, for example, manages sessions using tmux and Git worktrees. Git worktrees, tmux, Worktrunk, claude-squad.

One task, the same finish line

Imagine fixing a CSV export bug. One agent changes the application, another reviews the resulting diff, and a third updates the export guide in a separate documentation repository. The open product question is whether an empty export should produce a file containing only headings or show a message instead. You make that decision. The finish line is the same for every setup: the agreed behaviour works, the relevant checks pass, the review findings are resolved and the guide matches the result.

When plain sessions are enough

For the export fix, you might already know where the change is, which diff the reviewer has and where the product question will arrive. In that situation, our recommendation is to keep your existing workflow. If the missing piece is simply an alert, Claude Code’s own documentation explains notification hooks for when it needs input. A separate manager is not a prerequisite for that alert. Claude Code hooks guide.

If you prefer to leave the sessions running while you move between terminals, tmux documents detach and reattach. If you need different branches checked out concurrently, Git worktrees document that capability. Use the export task to decide whether those two tools cover your review and decision workflow. tmux documentation, Git worktree documentation.

Claude Code can also create the worktree for you: claude --worktree feature-auth starts a session in its own checkout on a new branch, and a second name in another terminal starts a second one. Worktrees separate file edits only. Claude Code worktrees

When a manager is worth trying

Try one when you repeatedly lose time locating the session that needs an answer, identifying the candidate being reviewed or returning to the documentation work. Worktrunk offers worktree lifecycle and activity views; claude-squad offers terminal session management; Workspace offers a map and a Needs-you list across projects. Worktrunk, claude-squad.

For a personal trial, keep the export task, candidate diff, review requirement and product decision the same. Note whether you can find the waiting agent, see who owns the next answer and return to the right work. Keep setup effort and manual coordination in that record too.

Where Hormesis Workspace fits

Workspace puts the projects and agent hand-offs on one map. It can present a decision as a card with pictures or a before/after view, return your answer to the agent and retain the decision history. For our export example, that gives a place to present the two proposed empty-state behaviours.

Its state words make a useful distinction for this task: Needs you means a permission prompt or a question addressed to you; Waiting can mean a question for a lead or an outstanding hand-off. Idle means the agent is at its prompt with nothing pending. Finished work appears in the Work list; “Finished” is not an agent-card state.

A worker’s ordinary question goes to its lead first when it has one; some questions go directly to the human. Decisions appear in-app. Items routed for immediate attention can produce a macOS notification when no Workspace window is focused, or the screen is locked, with notifications enabled. Routine progress, finished turns and idle states do not generate those notifications. These are public 1.0.2 behaviours.

Worktrees still need to be arranged: Workspace does not supply isolation by default. Review also needs to be set up; its separate reviewer can record PASS or FAIL, but the presence of a manager does not mean every result has been reviewed. If your present sessions and worktrees already handle the export task well, that is a reasonable place to stay.