What You’ll Learn
- How in-workspace multitasking works
- Creating and switching between tasks
- How context is preserved across tasks
- Difference between multitasking and parallel execution
- Best use cases for multitasking
What is In-Workspace Multitasking?
In-workspace Multitasking allows you to quickly create and switch between multiple tasks within the same workspace, making it easy to handle related goals without creating separate workspaces.How It Works
Multiple Conversation Threads
Each task is a separate conversation with its own context
Shared File State
Tasks in the same workspace see the same files
Quick Switching
Jump between tasks instantly without overhead
Related Work
Handle planning, coding, and reviewing together
Creating and Managing Tasks
Creating a New Task
| Platform | Shortcut |
|---|---|
| macOS | Cmd+N |
| Windows | Ctrl+N |
- Click New Task button in the interface
- Submit a prompt in a workspace (creates a task automatically)
What Happens
When you create a new task:- New conversation thread starts
- Task appears in the Left Panel
- Task shares the workspace’s file state
- Previous tasks remain accessible
Switching Between Tasks
Within Same Workspace:- Click task in the Left Panel
- Use New Task shortcut (Cmd+N / Ctrl+N) to create and switch
Context Preservation
How Context Works
| Scope | What’s Preserved |
|---|---|
| Within Workspace | Tasks share file state; each task keeps its own conversation |
| Across Workspaces | Each workspace maintains separate context |
| Across Projects | Full context preserved when switching projects |
Context When Switching Tasks
When you switch between tasks in the same workspace:- Preserved
- Full conversation history for each task
- Where you left off in each conversation
- File state (shared across tasks in workspace)
Multitasking vs Parallel Execution
Understanding when to use multitasking vs parallel execution is key to effective workflow management.Comparison Table
| Aspect | In-Workspace Multitasking | Parallel Execution |
|---|---|---|
| Location | Multiple tasks in ONE workspace | Multiple agents across DIFFERENT workspaces |
| Isolation | Tasks share file state | Complete filesystem isolation |
| Use Case | Related tasks (plan, code, review) | Independent parallel work |
| Conflicts | Tasks can see each other’s changes | No possible conflicts |
| Context | Shared files, separate conversations | Separate context per workspace |
Key Distinction
Tasks = Parallelize “non-coding work”- Solution discussion and comparison
- Requirement clarification and problem breakdown
- Technical research and risk assessment
- Code reading and understanding
- Multiple implementations running in parallel
- Each workspace is fully isolated (own branch, commit history, file state)
- Changes don’t interfere; conflicts are visible and manageable
Decision Guide
- Use Multitasking When
- Use Parallel Execution When
- Tasks are related and should share file state
- You want to quickly switch between planning, coding, and reviewing
- Work doesn’t need isolation
- You’re exploring different aspects of the same feature
Best Practices
Task Organization Tips
- Name tasks descriptively: “Plan auth” vs “Review auth” vs “Implement auth”
- Keep related tasks together: Same workspace for same feature
- Use workspaces for independence: Different features in different workspaces
- Commit before switching workspaces: Preserve work before moving
FAQs
How many tasks can I have in one workspace?
How many tasks can I have in one workspace?
There is no limit. You can create multiple tasks within a single workspace, each maintaining its own conversation context.
Do tasks in the same workspace share files?
Do tasks in the same workspace share files?
What happens to task history when I close Verdent?
What happens to task history when I close Verdent?
Task history persists. You can resume tasks where you left off when you reopen Verdent.
Can I move a task to a different workspace?
Can I move a task to a different workspace?
No. Tasks are tied to their workspace and cannot be moved between workspaces.