Work on parallel tasks
Once you are comfortable with a first coding task, split work when its parts can progress independently. Decide separately how to isolate files and how to delegate conversations.
| Need | Use |
|---|---|
| Keep edits to the same repository separate | Git worktrees: separate checkouts, usually on different branches. |
| Coordinate independent tasks in visible, nested conversations | Sub-sessions: separate conversations under a main session. |
| Delegate part of the investigation and inspect the agent's work | Subagents: delegated agents with read-only conversation views. |
A separate conversation does not isolate repository files. Combine delegated work with worktrees when parallel tasks need independent checkouts.
Isolate edits with worktrees
A Git worktree is a separate checkout of a repository, usually on a different branch. Worktrees share Git history but have separate working files, so you do not need to switch branches in your original checkout.
Use a worktree when you want to:
- Run parallel coding tasks without editing the same files.
- Start a new task without stashing or overwriting an unfinished change.
- Review or test another branch in a separate directory.
Ask Vibe to use a worktree before it starts editing:
Use a new Git worktree for this task. Fix the failing authentication tests,
leaving my current checkout unchanged.Two conversations in the same checkout still share files; two worktrees keep their file changes separate. Review the branch and any resulting PR. Keep the worktree until its changes have been committed and delivered or you have explicitly decided to discard them.
Worktrees isolate working files, not everything a task uses. Dependencies, environment variables, external services, and server ports may still need separate setup. Two development servers cannot both use the same port just because they run in different worktrees.
Coordinate work in sub-sessions
The original conversation is the main session. It can create sub-sessions for independent parts of a task and coordinate their results. For example:
Update the feature documentation. Create a sub-session for the French
translation and another to review the examples. Keep coordinating the
work here and incorporate their findings. Use separate worktrees for
any tasks that edit the same repository independently.The main conversation shows a Started a session entry. The new conversation appears nested under the main session in the project's left sidebar. Select it to inspect its progress, then return to the main session for the overall task.
Each sub-session has its own environment and panel contents. Check the selected conversation before using its files, terminal, browser, or process output; see Select the right conversation.
Follow updates to the main session
Sub-sessions can send messages to the main session with findings, results, or questions. The main conversation shows a Received a message from … entry with the sender's name and message content. The sender link identifies the sub-session that produced the update.
Review those updates and the resulting changes. The main session incorporates results, but a completed conversation does not by itself prove the overall task is ready.
Inspect delegated agents
The main agent can also spawn subagents for parts of a task, such as auditing a section of the codebase while it keeps working. Their conversation views are read-only.
Open a subagent's conversation from Subagents in the session's top-right panel, or click a Started subagent name entry in the main conversation. The view shows the instructions the subagent received, its steps, and their results. The header shows its name and status:
| Status | Meaning |
|---|---|
Running | The subagent is working. |
Waiting for input | It is paused; read the conversation to understand what it needs. |
Idle | It finished its current task; the main agent can send more work. |
Failed | It failed; hover over the status to see the reason. |
You cannot send messages through a read-only subagent view. Give new instructions or ask to stop its work through the main agent. These views differ from sub-sessions, which appear as separate nested conversations in the project sidebar.
For the CLI's custom-subagent configuration, see Agents. Desktop shares the CLI's core agent engine rather than running the CLI application; tools and prompts can differ.
Bring the results together
Return to the main conversation, inspect each task's changes and test results, and continue with Review changes and pull requests. Use Organize your conversations to switch between nested conversations or archive them when they are no longer active.