Give parallel tasks their own space.

Ask your agent to prepare two full copies of the project, each on its own branch. These are ordinary Git clones with separate working files.

The agent verifies both copies start at the same commit. The original stays on main. Each experiment has its own folder and feature branch.

Tell the coordinator to open a worker in each copy. One owns the documentation change. The other owns the settings change. Both must check their directory and branch first.

The two workers appear in the sidebar. Their folder names are shown beneath them, and the coordinator lists the branch and session for each job.

Select the documentation worker. Its reply shows the docs branch and the README change. The settings file and the other copies remain untouched.

Open the worker’s session menu. Its coordinator is listed under Ancestors, so you can follow the relationship back to the original conversation.

The settings worker needed a restart at the folder-trust prompt. Here I confirm the prepared folder in its new session. The completed documentation work stays in its own copy.

The second worker checks that it is in the configuration copy on the config branch. It changes only the settings file and validates the result.

Its actual diff changes the display setting. The README in this copy is unchanged. Both jobs remain visible in their own Code Overlord conversations.

Return to the coordinator. Both workers have finished, and the final table confirms which file changed in each branch. The original repository is still clean. Separate copies keep these working files independent.