Switch projects. Keep the whole workspace together.

A product rarely lives in one repository. This prepared Ember Studio workspace contains an app and its website. Both appear in the file tree, while each keeps its own Git history. Now give the agents a job that crosses that boundary.

When launching Codex, the directory chooser offers both workspace folders. I choose app for the coordinator. Its working directory matters: the website worker will receive the other repository explicitly.

Directly in the agent terminal, I ask for an app inspection and an independent website inspection. Compare the saved-search behaviour with the public promise, write two reports, and add one shared Quill note. Keep the application code unchanged.

The completed result identifies both real sessions, their repository roots and unchanged Git commits. The app's sixteen tests pass. The reports agree that search survives a reload, and identify details the website could explain more clearly.

Open Summon and choose Ember Planning under Recent Strongholds. This is an actual workspace switch. The next project has its own folder and its own notes.

Here is Planning's repository, and its note about choosing a release date. The Studio review note is in Studio. Switching projects changes the context you see, so a planning task stays with its planning workspace.

Use Recent Strongholds again to return to Ember Studio. Waiting is cut from this film. Let's check the saved work after the switch.

The app report opens in Peruse, both repositories are back in the tree, and Studio's original note is visible again. The recorded repository identity and test results remain available to read.

The website report is here too, in its own repository. Give each agent an explicit working directory, coordinate work across the product, and switch to another workspace when the job changes. Each repository keeps its own commit boundary.