Workspace Isolation
How Verdent separates parallel code changes with git worktrees
Workspace Isolation separates parallel code changes at the filesystem level with git worktrees. A workspace has its own directory, branch checkout, files, and staging state.
Manual workspace creation is not exposed in the current Verdent Desktop interface. The New Workspace button, its keyboard shortcut, and Duplicate to New Workspace are hidden. Duplicating a response creates the new task in the current workspace.
What You'll Learn
- How workspace isolation prevents conflicts
- How git worktrees enable isolation
- Difference between Base Workspace and Workspaces
- How existing and Verdent-managed workspaces appear in the interface
- Best practices for workspace management
What is Workspace Isolation?
When Verdent runs work in separate workspaces, changes from one worktree do not modify the files or staging state of another worktree. This makes parallel implementation and review safer.
How It Works
| Layer | How It Works |
|---|---|
| Directory | Each workspace is an isolated directory |
| Branch | Each workspace has its own branch checkout |
| Files | File changes in one workspace don't affect others |
| Staging | Each workspace has its own staging area |
Benefits
Zero Interference
File changes stay in separate worktree directories
Safe Experimentation
Try risky changes without affecting stable code
Clear Comparison
Use git diff to compare approaches across workspaces
Selective Rebasing
Only rebase results you trust
Base Workspace vs Workspaces
Base Workspace
The Base workspace is your original repository checkout, serving as the default starting point.
| Characteristic | Description |
|---|---|
| Location | Your original git clone or init location |
| Primary Branch | Typically on main or development branch |
| Reference Point | Source for comparing experimental work |
When to Use Base:
- Quick changes that don't need isolation
- Reference point for comparing experimental work
- When you want changes to go directly to the main branch
- Simple tasks where parallel execution isn't needed
Workspace
A Workspace is an isolated working environment created using git worktrees, with its own independent branch checkout and file state.
Verdent can use a workspace when a supported workflow needs isolated code changes. Existing workspaces remain associated with their project and can contain multiple tasks.
Work with existing workspaces
Workspaces that already belong to a project remain grouped with that project in the Projects panel. Select a workspace to view its tasks and file state.
- Tasks inside the same workspace share its files but keep separate conversation context.
- Switching to another workspace changes the active worktree and branch context.
- Duplicating a response keeps the duplicated task in the current workspace.
- Delete a workspace only after committing, rebasing, or otherwise preserving work you need.
Rebasing Workspace Changes
When you're ready to integrate workspace changes back to the main branch:
Using Verdent UI
Complete Work
Complete work in the workspace
Review Changes
Click Task Changes in the middle panel to review all modifications
Rebase to main branch
Click Workspace Actions → Rebase to main branch in the Workspace Bar
Resolve Conflicts
Resolve any conflicts if prompted
Verify
Review changes before confirming
Keeping Workspaces Updated
Use Workspace Actions → Sync with main branch to pull the latest changes from the main branch into your workspace. This helps prevent large conflicts when rebasing.
Best Practices
Workspace Maintenance
| Practice | Why |
|---|---|
| Delete rebased workspaces | Free up disk space |
| Remove abandoned experiments | Keep workspace list manageable |
| Keep workspace count reasonable | System resources are finite |
Git Hygiene
| Practice | Why |
|---|---|
| Commit frequently | Commit work in progress before switching |
| Small commits | Smaller commits are easier to cherry-pick |
| Sync with base regularly | Don't let workspaces diverge too far from the main branch |
| Reduce conflict complexity | Regular integration prevents large conflicts |
FAQs
How much disk space does each workspace use?
Each workspace duplicates working files but shares the .git directory. Space usage roughly equals your project size per workspace. Large projects with many parallel workspaces will use significant disk space.
Can I delete a workspace?
Yes. Delete the workspace through Verdent. This removes the directory but preserves any committed work on the branch.
How do I create a new workspace?
Manual creation is not available in the current Desktop interface. The New Workspace entry and shortcut are hidden. Verdent can still use workspaces internally for supported isolated workflows.
What happens to uncommitted changes if I delete a workspace?
Uncommitted changes are lost when a workspace is deleted. Always commit or stash changes before removing a workspace.
Can I convert a workspace to the base workspace?
No direct conversion, but you can rebase all changes from the workspace to the main branch, then delete the workspace. The branch history is preserved.
Do worktrees work with all git hosting services?
Yes. Git worktrees are a standard git feature. They work with GitHub, GitLab, Bitbucket, and any other git hosting service.