Switch between your main project and Solo work
Move between the main project and Solo work without confusing their file scopes.
Last updated 17 September 2026
Move between the main project and Solo work without confusing their file scopes.
Before you begin
Keep both conversations available in the project sidebar. A Solo has its own branch and folder even though it belongs to the same project.
The Solo branch is selected in Git; its documentation diff is separate from the main project.
Steps
Select the Solo conversation and read its Solo branch strip.
Open Git and use the scope strip to select the Solo or main project. Inspect the selected label before staging, committing, or opening a diff.
Select the normal project conversation when you want to continue work in the main folder. Recheck the active scope after switching.
When running or previewing a Solo app, use its own preview controls and confirm the actual service URL and port. An existing main-project server can still be running.
Return to the Solo conversation to continue its task. Switching views by itself does not merge its changes into the main project.
What to expect
You can inspect and continue each work stream while knowing which files and branch each action affects.
Troubleshooting
The Git screenshot includes separate main and Solo scope choices. Do not use the project’s unchanged top-level branch label alone to infer a Solo’s working branch; read the selected Git scope and Solo strip as well.