# Parallel Isolated Workspaces

Recommended mode: `repro-fix`

Recommended startup:

```bash
pyro host connect codex --mode repro-fix
```

Smoke target:

```bash
make smoke-parallel-workspaces
```

Use this flow when the agent needs one isolated workspace per issue, branch, or
review thread and must rediscover the right one later.

Chat-host recipe:

1. Create one workspace per issue or branch with a human-friendly name and
   labels.
2. Mutate each workspace independently.
3. Rediscover the right workspace later with `workspace_list`.
4. Update metadata when ownership or issue mapping changes.
5. Delete each workspace independently when its task is done.

The important proof here is operational, not syntactic: names, labels, list
ordering, and file contents stay isolated even when multiple workspaces are
active at the same time. Parallel work still means “open another workspace in
the same mode,” not “pick a special parallel-work mode.”
