Skip to content

Workspace sessions

A workspace session is a session that does not belong to a task. It has no workflow steps. It uses the same session page as a task session. The agent can read your repository and create tasks.

A workspace session creates the missing tasks, then starts a Builder in the background.

Start a workspace session

Start a session in a new worktree, then send the first message to the agent.

In a collapsed sidebar, select +, then New session. You can also run New session from the command palette.

Runtime and model starts with the Default model of the repository. For OpenCode, also check Runtime profile.

Work locationWhere the agent works
Current checkoutIn your repository folder, on its current branch. The agent changes the files of your checkout.
New worktreeIn a new folder, on a new branch or an existing branch. Enter a Worktree name. Your checkout does not change.
Existing worktreeIn a worktree that you select. Use it to continue work in the worktree of a task or an earlier workspace session.

The session compares its changes with the Target branch.

New session has no Goal mode. To give the agent a goal, send /goal and the objective in its composer. See Set a goal with /goal.

Use a custom role

A custom agent role, such as a code reviewer, gives a workspace session its own instructions.

  1. Open Settings, then Custom agent roles, and select Add role.
  2. Enter a Name and a System prompt, then select Save settings.
  3. Start a workspace session, and choose the role in Custom role in the New session dialog.

Roles are available in every workspace. New sessions use the saved role. Existing sessions keep their role when you edit or delete it.

Create tasks from a request

Ask the agent to create tasks, for example:

Message to the agent
Let people export a notebook to Markdown and to PDF. Split this into tasks that each fit in one pull request. Search the board first, and do not create a task that exists.

New tasks start in Backlog. Their first step depends on their issue type.

  1. Each new task shows as a card in the session. Select Open on a card. The task details open.
  2. Select the workflow action, for example Start Builder. Then select Run in background. The task session starts, and the workspace session stays open.

Fork a workspace session

Fork a session from an earlier reply into a new worktree, then send another follow-up.

A fork is a new workspace session with the conversation of the source session up to one reply. Use it to try another follow-up and keep the source session as it is.

Fork from this reply shows under the last reply of each completed turn. The fork keeps the runtime, the model, the role, and the target branch of the source session.

Work locationWhere the fork works
Same folderIn the folder of the source session. The two sessions change the same files.
New worktreeIn a new worktree, on a new branch from the last commit of the source folder. Uncommitted changes do not go to the new worktree. The source folder must have a commit.

Import a session from an external runtime

Continue in OpenDucktor a conversation that you started in OpenCode, Codex, or Claude Code.

Import a Claude Code conversation of the repository, then continue it in OpenDucktor.

Select the arrow beside New task, then Import session from an external runtime. You can also run it from the command palette.

The list shows only the main conversations that started in the repository folder or in one of its Git worktrees, and that no task or workspace session uses yet. For Codex, it also shows the sessions that you archived in Codex.

The import does not copy the conversation. OpenDucktor continues the same session, with the same session ID, in the same folder. It uses the title and the model of the session, and the default target branch of the repository.

The list stays current for 10 minutes. If an import fails with a message that ends with Reload sessions., close the dialog and open it again.

Archive a workspace session

  1. Select Archive in the session header.
  2. For a session in a worktree, Remove worktree and branch is on. Archive then deletes the worktree and its branch. To keep them, turn it off. If another workspace session or an open task uses the worktree, OpenDucktor keeps it.
  3. Select Archive session. The session moves to Archived sessions, and its agent and terminals stop.

To restore a workspace session, select the arrow beside New task, then Archived sessions, then Restore on the session.

Next

On this page