Switch folders without discarding needed work

Change projects only after preserving the current workspace's useful text and review state. Switching folders changes the agent context, cancels the old worker, and discards its queue and review cards; it is not a way to move an unfinished request into another project.

Preserve the old workspace

1. Check the currently displayed root and open tabs.
2. Save direct edits you intend to keep and inspect the saved files. Preserve any text that cannot yet be saved separately.
3. Review the active agent turn and queued requests. Record the outcome you still need and the relevant non-secret error or trace details before leaving.
4. Resolve needed proposals in the old workspace, or retain enough of their intent to ask for a fresh proposal later. Do not expect their review cards to survive the switch.

Stopping a turn does not prove it made no changes, and a queue entry is not an execution receipt. Inspect work already performed before deciding what needs to be repeated.

Open the next folder

1. Select Workspace / Files, then Open folder.
2. Choose the new project's folder.
3. Check the new displayed root before opening files or submitting a request.
4. Open a known file from that folder and confirm its contents belong to the intended project.

Check the transition

Your next request must refer to the new workspace, not an assumption carried from the previous transcript. Do not interpret the absence of old cards as proof that the old task finished. If you need to continue that task, reopen its original folder, inspect the saved state, and formulate a bounded continuation from what actually remains.

Use the first-folder walkthrough for orientation and the editor/agent concept to distinguish a request from a verified file result.