Quest supports execution environments such as Local and Worktree. This article introduces the use cases and configuration for different environments, helping you safely and efficiently isolate and execute tasks.Documentation Index
Fetch the complete documentation index at: https://docs.qoder.com/llms.txt
Use this file to discover all available pages before exploring further.
| Environment | Behavior | Best for |
|---|---|---|
| Local | Work directly in your open workspace; edits land in the project you have open | Quick tasks, fast validation |
| Worktree | A separate Git worktree checkout so changes stay isolated from your main branch until you apply or merge | Medium complexity, many apply iterations, parallel tasks in one repo |
- With a Git repository: all three environments are available.
- Without Git: Local only.
Quest supports parallel tasks across environments where your plan allows.
Worktree
Worktree mode uses a separate Git worktree checkout in the background so the Agent can execute tasks in an isolated environment. Your main workspace remains clean, and multiple worktrees can run in parallel, making it ideal for advancing multiple tracks of work simultaneously.Core Capabilities
- Parallel Multi-Workspace: Start multiple Agents simultaneously on the same repository. Each Agent has an independent file view and modification space without interfering with each other. While a complex refactoring runs in the background, you can continue writing new features in your main workspace.
- Base on Local Branches: When creating a worktree, you can select any local branch as the starting point, iterate and test your changes on an isolated branch, and then merge back to the main branch.
- Automatic Environment Bootstrap: After you select Worktree and send a message, the Agent can detect dependencies and run common setup steps before entering task execution.
- Isolated Modifications: The Agent’s Files panel displays the structure of the current Worktree directory, not the main workspace root. Iterative changes are isolated from the main branch until confirmed, allowing you to Apply multiple times without polluting your main checkout.
When to Use
| Scenario | Description |
|---|---|
| Parallel Tasks | Handle multiple requirements or refactoring efforts simultaneously, advancing each track independently |
| Branch-level Experiments | Create a Worktree based on a feature branch to iterate and test independently |
| Keep Main Branch Clean | For medium-complexity tasks needing multiple Apply cycles and adjustments, use Worktree to contain risks |
How to Use
- In the run-environment area at the top of the chat panel, click the current mode (e.g., “Local”)
- Choose Worktree mode from the dropdown
- In the branch dropdown next to the mode selector, choose which local branch the Agent should base the Worktree on