Skip to main content
Environment and Execution

Execution environments

Choose where Qoder reads files, runs commands, and records changes.

Choose the workspace and execution environment before sending the task. The selection determines where Qoder reads files, runs commands, and inspects Git state.
EnvironmentWhere changes are madeUse it when
Local workspaceThe open project directory on this deviceYou need a small change, fast verification, or immediate access to the result.
WorktreeA separate Git worktreeYou are running parallel tasks or isolating a larger change from the current checkout.
SSH workspaceA directory on a registered remote hostThe code, dependencies, or runtime exist only on that host.
WSL workspaceA Linux directory in a WSL distribution on WindowsYour project is in WSL and should run in its Linux environment.
No workspaceNo project directoryThe task does not need project files or commands.

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.

Worktree

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

  1. Open the current execution mode at the bottom of the task composer.
  2. Select Worktree, then choose the Git branch to use as the starting point.
  3. If Qoder offers to include uncommitted changes, review them before enabling the option.
  4. 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.

SSH workspace

Qoder reads files and runs commands in the remote directory. Make sure the SSH account can read and write the project, then connect the workspace:
  1. Choose Connect SSH or open Settings → Connections. Choose Add, then select a host discovered from ~/.ssh/config.
  2. If the host needs a particular client or configuration file, complete the path settings below before connecting. Choose Connect, complete authentication, and wait for the connected status.
  3. Select the remote project directory and create the workspace.
  4. Confirm the host, path, and branch in the new task before starting work.
If the connection drops, check networking and authentication, reconnect, and confirm the project directory is accessible. Remote branch controls depend on the host's Git capabilities; check the connection and repository if an action is unavailable. To bring existing remote tasks into Qoder, use Data import.

Specify an SSH client and configuration file

If a host needs a particular SSH client or a separate configuration file, set its paths before connecting. Skip this setup when the defaults work for the host.
  1. Find the host in Settings → Connections → SSH. Disconnect it if connected, then choose Edit.
  2. Fill in the fields you need:
    FieldValueIf left blank
    SSH client pathAbsolute path to the SSH executable on this computerSelect a client automatically
    SSH configuration file pathAbsolute path to the SSH configuration file on this computerUse the default configuration
  3. Choose Save, then connect to the host. The changes apply only to future connections to this host.
Do not quote paths or use variables or wildcards in the configuration file path. If the client cannot be found, check the executable path. If configuration ownership or permissions are rejected, check that file and any files it includes.

Choosing safely

  • The project must be a Git repository for Worktree to appear.
  • Each worktree uses disk space; remove unused worktrees under Settings → Worktrees.
  • SSH commands and file operations run on the remote host. Confirm the host, directory, and branch before sending.
  • 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.