Tips & Troubleshooting
Workspaces and branches
The easiest way to identify a workspace is by which branch it's on.
For instance, this workspace is on the scroll-to-bottom-btn branch:

(The secondary name shown, warsaw-v2, is the directory name.)
Watch the Git workflow
Conductor wraps common GitHub and branch tasks in the app UI, but the branch is still the core unit that explains what a workspace is and how it fits into review and PR flow.
When you create a new workspace, Conductor will create a new branch for it. When you start your first chat, Conductor will instruct the agent to rename this branch to match what you're working on.
Switching branches
If what you're working on changes, you can check out a different branch:
git checkout some-other-feature...or rename the current branch:
git branch -m new-name...or create a new branch:
git checkout -b new-branchStarting from an existing branch
If you have an existing branch and you want to start a new workspace from it, you can follow these steps:
- Use ⌘ + shift + N or click the
...icon next to the "New workspace" button - Choose the "Branches" tab and select a branch
You could also create a new workspace and then switch to the branch you want using the instructions in the "Switching branches" section above.
One workspace per branch
A branch can only be checked out in one workspace at a time.
If you want to check out the scroll-to-bottom-btn branch in tokyo, but you already have
that branch checked out in warsaw, try one of these:
- In
tokyo, rungit checkout -b scroll-to-bottom-btn-2 scroll-to-bottom-btnto create a new branch based off ofscroll-to-bottom-btn - In
warsaw, switch to any other branch (e.g.,git checkout -b dummy), then intokyorungit checkout scroll-to-bottom-btn