Workbenches

Create a separate branch and working tree for a project task, then integrate and remove the finished workbench.

What a workbench contains

A workbench is a project connected to a parent project’s Git roots, with its own branch and working trees. It gives an independent change room to develop without mixing its edits into the parent checkout.

Use one for a feature, a bug fix, or another bounded task. For a multi-root project, the workbench follows the parent’s roots so related repository work stays together.

Create and open a workbench

1. Select a project with Git roots and open its context menu.
2. Choose New Workbench.
3. Provide a new branch name that describes the change, such as feature/search-empty-state.
4. Select Create Workbench, wait for creation to complete, then open it.
5. Start the implementation agent from the workbench context.

The new workbench starts from committed repository state. Uncommitted and untracked changes in the parent are not copied into it. Commit any prerequisites you intend the workbench to contain before creating it.

Work and review inside it

Keep implementation, project checks, and review in the workbench. Check its branch and Git changes before committing. If several agents share a workbench, they still share that workbench’s files; agree on responsibilities.

For two independent features, create two workbenches. This makes it easier to review each diff and decide when each change is ready.

Integrate, then remove

1. Review the result and run the checks required by your project.
2. Commit the completed change on the workbench branch.
3. Integrate the commits using your repository’s normal Git workflow. Creating a workbench does not automatically merge its changes.
4. Confirm the intended commits are present in the destination branch.
5. Open the workbench’s context menu and choose Remove Workbench.