Skip to main content
Parallel development enables you to work on multiple features, bug fixes, and experiments simultaneously. Each runs in its own isolated workspace, where tasks and their agents work independently.

​
What You’ll Learn

  • Set up parallel development workflows
  • Work on features, bugs, and experiments simultaneously
  • Common patterns for parallel execution

​
Overview

Parallel development combines:
  • Workspace Isolation - Each workspace has its own branch and file state
  • Parallel Tasks - Multiple tasks with their own agents working simultaneously
  • Selective Rebasing - Choose which results to integrate
BenefitDescription
FasterMultiple agents complete work in parallel
No ConflictsIsolated workspaces prevent interference
Safe ExperimentationTry different approaches without risk

​
Setting Up Parallel Work

1

Create First Workspace

Click New Workspace in the Top Bar, name it feature-auth
2

Start First Task

In the input box, describe the feature and send to start a task with its agent
3

Create Second Workspace

Without waiting, click New Workspace again, name it bugfix-123
4

Start Second Task

Describe the bug fix to start another task with its agent
5

Create More as Needed

Repeat for additional parallel tasks

​
Workspace Structure

​
Monitoring Progress

Switch between workspaces to check progress:
ActionShortcut
Next workspaceCtrl+Tab
Previous workspaceCtrl+Shift+Tab
All tasks and their agents continue working regardless of which workspace you’re viewing.

​
Workflow Patterns

Work on a feature while addressing an urgent bug:
WorkspaceTask
feature-dashboardContinue feature work
hotfix-securityFix critical bug
Bug fix completes first → rebase immediately. Feature continues unaffected.

​
Completing Parallel Work

1

Review Each Workspace

Click Task Changes to review changes for each workspace
2

Address Issues

Fix any problems found in reviews
3

Commit Changes

Use Source Control (Ctrl+Shift+G) to commit with descriptive messages
4

Rebase to Master

Click Workspace Actions → Rebase to master for each completed workspace
5

Clean Up

Click Delete Workspace to remove completed workspaces

​
Best Practices

​
Good Candidates for Parallel Work

  • Independent features
  • Bug fixes unrelated to current work
  • Experiments and proof-of-concepts
  • Different approaches to same problem

​
Poor Candidates

  • Tasks with dependencies (A must complete before B)
  • Very small, quick tasks
  • Tasks requiring tight coordination

​
FAQs

Start with 2-3 and increase based on performance. Complex tasks may need more resources per agent.
If tasks need shared code, they may not be good candidates for parallelization. Complete shared work first, then parallelize independent follow-up tasks.
No. Tasks and their agents continue working in the background when you switch to another workspace.

​
See Also

Parallel Execution

Core parallel execution features

Workspace Isolation

How workspaces stay isolated