Parallel Execution is Verdent’s ability to run multiple AI agents simultaneously, each with its own isolated context, transforming how you handle complex development work.

​
What You’ll Learn

  • How parallel execution accelerates complex workflows
  • Launching and managing multiple agents
  • How agents coordinate without conflicts
  • Workspace controls for running agents
  • Best use cases for parallel execution

​
What is Parallel Execution?

Parallel Execution allows you to run multiple AI agents simultaneously, each working independently with its own isolated context. Instead of waiting for one agent to finish before starting another, you can launch multiple agents at once, each working without interference. Agents can share a workspace or work in separate workspaces for isolated feature development.

​
How It Works

ComponentDescription
Isolated ContextEach agent maintains its own conversation context
Workspace FlexibilityAgents can share a workspace or work in separate workspaces
No InterferenceAgents work independently without conflicts
Selective RebasingWorkspace changes can be compared and selectively rebased

​
Key Benefits

Reduced Turnaround Time

What takes one agent hours, multiple agents complete in minutes

Practical Multi-Step Development

Makes it feasible to use agents for larger, complex pieces of work

Safe Experimentation

Try different approaches in parallel, compare results, rebase what works

Continuous Workflow

Start new tasks while others are still processing

​
Performance Through Parallelization

Parallel agents accelerate complex project cycles by running multiple agents simultaneously rather than sequentially. The actual speedup depends on task independence and available resources.

​
Sequential vs Parallel

Sequential (Traditional): One agent completes Task A, then starts Task B, then Task C. Parallel (Verdent): Agents work on Tasks A, B, and C simultaneously.
Actual improvement depends on task parallelizability. Tasks with dependencies still require sequential execution, but independent work can proceed simultaneously.

​
Launching Multiple Agents

​
Creating Parallel Workspaces

1

Create First Workspace

Click New Workspace in the top bar or use Cmd+Shift+N (macOS) / Ctrl+Shift+N (Windows)
2

Submit First Prompt

Submit your prompt in workspace A, this creates a new task and the agent starts working
3

Create Second Workspace

Click New Workspace again or use the same keyboard shortcut
4

Submit Second Prompt

Submit a prompt in workspace B, this creates another task and the second agent starts in parallel
5

Continue as Needed

Repeat for additional parallel tasks

​
Switching Between Active Agents

ActionShortcut
Next WorkspaceCtrl+Tab
Previous WorkspaceCtrl+Shift+Tab
Select WorkspaceClick All Workspaces in the top bar

​
Example Workflow

Task 1: Planning the architecture in workspace `feature-auth`
Task 2: Implementing user interface in workspace `ui-components`
Task 3: Writing tests in workspace `test-suite`
All three tasks run simultaneously without waiting for each other.

​
How Agents Avoid Conflicts

Agents avoid conflicts in two ways:
  1. Isolated Context - Each agent maintains its own conversation context, regardless of workspace
  2. Workspace Isolation - For parallel feature development, agents can work in separate workspaces using git worktrees

​
Workspace Isolation (for Parallel Feature Development)

When agents work in separate workspaces, file-level isolation is achieved through git worktrees:
LayerHow It Works
DirectoryEach workspace is an isolated directory
BranchEach worktree has its own branch checkout
FilesFile changes in one worktree don’t affect others
StagingEach workspace has its own staging area

​
No Coordination Needed

When using separate workspaces, agents don’t need to coordinate because they physically can’t conflict:
  • Changes are isolated at the filesystem level
  • No shared state between workspaces
  • Each agent sees only its own changes

​
Rebasing Results

When ready, rebase desired changes using Verdent’s workspace controls:
  1. Switch to the workspace you want to apply
  2. Click Workspace Actions → Rebase to main branch in the Workspace Bar
  3. Resolve any conflicts if prompted
  4. Review changes before confirming
Only bring trusted results back to master. The isolation lets you compare approaches before committing to one.

​
Workspace Management

The Workspace Bar provides controls for managing workspaces:
ControlDescription
Delete WorkspaceRemove the workspace (available in Workspace Bar)
Workspace ActionsDropdown with Rebase to main branch, Sync with main branch

​
Deleting a Workspace

Click Delete Workspace in the Workspace Bar to remove a workspace when no longer needed.
Uncommitted changes are lost when deleting a workspace. Review changes and rebase any work you want to keep before deleting.

​
Agent Limits

  • No hard limits on parallel execution
  • Multiple agents can run simultaneously
  • A workspace can have multiple agents (multiple tasks)
  • Agents can also work across separate workspaces for isolated feature development

​
Best Use Cases

​
Ideal for Parallel Execution

  • Work on authentication, payment, and notifications simultaneously
  • Each feature in its own workspace
  • No interference between features
  • Try different approaches to the same problem in parallel
  • Compare results across workspaces
  • Rebase only the approach you prefer
  • Keep feature development running
  • Spin up new workspace for urgent bug fix
  • Both proceed without blocking each other
  • Work across multiple client projects
  • Switch between projects with full context preserved
  • Tasks continue working when you switch away
  • Continue development in one workspace
  • Run code review in another
  • Get review feedback without stopping development

​
Not Ideal For

ScenarioWhy
Tasks with strict sequential dependenciesMust wait for previous task to complete
Work requiring tight coordinationChanges need to be synchronized
Very small, quick tasksWorkspace creation overhead not worth it

​
FAQs

Details on specific limits coming soon. A workspace can have multiple tasks running simultaneously.
No. Each task operates with its own isolated context. This prevents interference but means tasks can’t see each other’s work until you rebase.
When using separate workspaces, each task works in its own git worktree. When you rebase, you’ll resolve any conflicts using standard git rebase conflict resolution.
Yes. Use the Left Panel to see all active tasks within the current workspace. Switch between workspaces with Ctrl+Tab.

​
See Also

Workspace Isolation

How git worktrees enable parallel execution

Multitasking

Multiple tasks within the same workspace

Parallel Development Workflow

Step-by-step parallel development guide

Project Switching

Managing multiple projects