Skip to main content
Choose a workspace based on where the files and development tools should live. A separate worktree gives a parallel task its own repository files; a remote workspace runs the agent and tools in the selected SSH, WSL, or Docker environment.

​
Branches and worktrees

You can arrange open sessions in up to four panes. Each session has its own conversation history, but the project folder determines which files it works on. Two sessions pointed at the same folder can change the same files, even when their conversations are separate. For a Git project, you can choose among these workspace arrangements: For two fixes that need to run at the same time, give each its own worktree so their working files are separate. Each checkout may need the project’s dependency installation and local configuration before tests can run. A worktree separates repository files; commands still run with the access granted by the operating system.

​
Prepare an isolated task

  1. Start a new Code session and select the Git project.
  2. Check the branch in the composer. Select the starting branch and enable a separate worktree before the first run.
  3. Send a request that includes any setup the new checkout needs, such as reading the README and identifying the test command.
  4. Confirm the session’s folder and branch before allowing edits. Install the project’s dependencies in that checkout when required.
A worktree is useful when one session is fixing checkout quantities while another is reviewing a different feature. Giving them different conversation names alone does not separate their files. See Review and commit when each change is ready.

Enable worktree before the first run to give the task a separate checkout.

​
Arrange sessions in panels

Open Search sessions and use the panel actions to choose one panel, two or three side-by-side panels, or four in a grid. A session’s sidebar menu offers Open in panel to place that session in a specific panel. Closing a panel leaves the session in the sidebar. Use panels to compare an implementation and its review or to watch two independent tasks. Panel layout changes what is visible; each session still uses its selected workspace.

​
Remote environments

Use Remote development when the repository and tools should run on an SSH host, in WSL, or in Docker. The desktop interface stays on your computer, while file operations and commands run in the selected environment. The remote guide covers connection fields, tool and credential transfer, saved connections, and what happens when you disconnect. A new session is required to change execution destinations. Continue with Remote development.