Project Switching
Instant switching between multiple projects with state preservation
Project Switching enables you to jump between different projects instantly while Verdent keeps all workspace states alive. Move fluidly between multiple client projects or switch between your main repo and side projects without any setup delay or lost state.
What You'll Learn
- How fast project switching works
- State preservation across project changes
- Managing multiple projects
What is Project Switching?
Project Switching is Verdent's ability to maintain multiple open projects simultaneously and switch between them instantly with full state preservation.
How It Works
| Feature | Description |
|---|---|
| Multiple Projects | Keep many projects open at once |
| Instant Switching | Jump between projects with minimal loading |
| State Preservation | All workspace states remain alive |
| Context Retention | Conversation and task context preserved |
Key Benefits
Fast Loading
Minimal waiting for projects to load
Full Context
Pick up exactly where you left off
Active Agents
Agents continue running when you switch projects
Fluid Workflow
Handle multiple clients throughout the day
Fast Project Switching
What Makes It Instant
Verdent keeps all project states in memory, enabling instant switching:
- No Project Reload: Project context stays loaded
- Workspace States Alive: All workspaces maintain their state
- Tasks Preserved: Active tasks continue where you left off
- Agent Continuation: Running agents keep working in the background
Switching Methods
| Action | Method |
|---|---|
| Current Project | Click Current Project in the top bar |
| Home | Click Home in the top bar, then select your project |
State Preservation
What Gets Preserved
When you switch projects, Verdent maintains:
- All workspace states (Base + Worktrees)
- Session and conversation history
- Running agent sessions
- Project-specific settings (AGENTS.md)
- Branch checkout state
- Uncommitted changes
- Active task reference
- Full conversation history
- Agent execution state
- Where you left off
Example Workflow
flowchart LR
subgraph Morning
A1[Open Client A] --> A2[Start feature] --> A3[Agent begins working]
end
subgraph Midday
B1[Switch to Client B] --> B2[Agent A continues in background]
B1 --> B3[Work on Client B bug fix]
end
subgraph Afternoon
C1[Switch back to Client A] --> C2[Agent A has made progress]
C2 --> C3[Review and continue]
end
Morning --> Midday --> AfternoonMulti-Project Management
Opening Projects
Open Project Dialog
Click Home in the top bar, then click Open Project
Select Directory
Navigate to your project's root directory
Open
Click Open to add the project to Verdent
Managing Open Projects
| Action | How To |
|---|---|
| Switch Project | Click Current Project in the top bar |
| Open New Project | Click Home in the top bar, then Open Project |
Project Limits
There is no limit to how many projects you can have open simultaneously.
- Multiple projects can be open simultaneously
- All states remain alive during the session
Use Cases
Common Scenarios
Multiple Client Projects
Handle work for multiple clients throughout the day:
- Open Client A's project in the morning
- Start agent on feature implementation
- Switch to Client B for an urgent fix (agent A continues)
- Switch back to Client A, check progress
- Continue alternating as needed
All clients' states preserved.
Main Work + Side Project
Balance your main job with personal projects:
- Primary work project stays open all day
- Open side project during breaks
- Switch instantly between them
- Side project preserves state even when not active
Multi-Repository Monorepo
Work across related repositories:
- Open frontend repository
- Open backend repository
- Open shared library repository
- Switch between them as you implement features
Learning + Production
Study codebases while working:
- Keep production project open
- Open open-source project to study patterns
- Switch between to apply learnings
Best Practices
Organization
| Practice | Why |
|---|---|
| Name projects clearly | Easy identification in project list |
| Close unused projects | Free up system resources |
Workflow Tips
- Let agents work: Agents continue running in the background when you switch projects
- Commit before long switches: Save your state before extended time away
- Use workspaces for major features: Combine project switching with workspace isolation
- Check agent status on return: Review what agents accomplished while away
Resource Management
| Consideration | Recommendation |
|---|---|
| Many projects open | Close projects you won't return to soon |
| Memory usage | Memory consumption depends on project size and active agents |
| Agent activity | Running agents consume resources |
FAQs
Do agents keep running when I switch projects?
Yes, agents continue running in the background when you switch projects. You can return later to check their progress.
Is there a limit to how many projects I can have open?
No, there is no limit. The system is designed for multi-project workflows with all states preserved.
What happens if I close a project with running agents?
Running agents will be stopped when you close the project. Make sure to wait for agents to complete important work before closing.
Can I open the same project twice?
No. Each project can only be open once. If you need multiple views of the same project, use workspaces within that project.
Can I open nested projects?
No. Verdent does not support opening a project that is inside another open project. Each project must be a separate, non-nested directory.
Do project settings sync between sessions?
Yes. Project-specific settings, conversation history, and task states are all preserved between Verdent sessions.