Review changes in a Solo workspace
Review the changes produced inside a Solo workspace before bringing them back.
Last updated 17 September 2026
Review the changes produced inside a Solo workspace before bringing them back.
Before you begin
Let the current agent pass finish and keep the intended requirements available. Review the working tree as well as the agent’s summary.
The demo Solo adds a small review document; Git displays its actual file diff for inspection.
Steps
Select the Solo conversation and read its result, remaining limitations, and any manual checklist.
Open Git → Changes and select the Solo scope. Open each file’s diff and confirm the work matches the requested boundary.
Inspect new and untracked files as well as modifications. Exclude unrelated material from any commit.
Run appropriate checks inside the Solo folder. If you preview an app, confirm the server belongs to that Solo and that it uses the intended configuration.
Ask for focused corrections in the Solo conversation, then repeat the relevant review.
When ready, choose the delivery path deliberately: Rejoin for a local target branch or Ship for the configured remote workflow.
What to expect
You have assessed the actual Solo changes and know what will be delivered.
Troubleshooting
The screenshot shows an untracked Markdown file’s eight added lines in Git. Diff and repository state are stronger evidence of what changed than a short agent summary. A clean working tree after committing still needs comparison with the target branch before Rejoin.