Skip to main content

Local workspaces and Worktree

Run tasks in local projects, isolate changes with Worktree, and review results.

Work directly in a local project or isolate changes in a Worktree. For other execution locations, see Choose a workspace and execution location.

Local workspace

Select an existing workspace or choose New workspace. A workspace can contain multiple readable and writable project folders, with one primary folder used for opening the project. When you create a workspace or add folders to an existing one, Qoder lists the folders that need your confirmation. Check each path and confirm only if you trust its contents. If a path is wrong, cancel and select the intended folder.

Worktree

Worktree requires a supported local Git repository with at least one commit. Worktree tasks isolate changes in a separate Git checkout. Configure retention and backup behavior under Settings → Worktrees. Ignored files are not included in the Git backup, so do not rely on the backup for generated secrets or local-only data.

Start a Worktree task

You can reuse an existing worktree to continue working, or create a new one. Reuse a worktree when you want to keep working with its code and changes. To isolate a separate set of changes, follow the steps below to create a new worktree and give its directory a recognizable name.
  1. Open the current execution mode at the bottom of the task composer.
  2. Select Worktree and choose the starting Git branch.
  3. To customize the new worktree directory name, enter one under Worktree name (optional), such as api-cleanup. Use up to 32 ASCII letters, digits, hyphens, or underscores. If you leave it blank, Qoder generates a name. If the directory name is already taken, Qoder adds a random suffix.
  4. If Qoder offers to include uncommitted changes, review them before enabling the option.
  5. Send the task. Qoder reads, edits, and verifies the code in the separate worktree.
Review the changes before bringing them back to the local workspace. Keep the local workspace clean before a handoff so existing uncommitted work is not overwritten.

Configuration and changes in a new worktree

New worktrees carry required project configuration. Supported local changes are preferably kept unstaged. Review the configuration and diff before continuing; do not assume the entire original directory or every untracked file is copied.
  • The project must be a Git repository for Worktree to appear.
  • Each worktree uses disk space; remove unused worktrees under Settings → Worktrees.
  • Environment isolation does not replace permission controls. Choose an appropriate Access Permissions option for the task.
An existing task cannot switch between Local and Worktree modes. Create a new task when the execution boundary must change.

Use another device or environment

For projects on a server, see SSH workspaces. To run tasks on another computer, see Connect another computer. For PPT template support across environments, see Office Plugins.