# Parallel Isolated Workspaces

Recommended profile: `workspace-core`

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.

Canonical SDK flow:

```python
from pyro_mcp import Pyro

pyro = Pyro()
alpha = pyro.create_workspace(
    environment="debian:12",
    seed_path="./repo",
    name="parallel-alpha",
    labels={"branch": "alpha", "issue": "123"},
)
beta = pyro.create_workspace(
    environment="debian:12",
    seed_path="./repo",
    name="parallel-beta",
    labels={"branch": "beta", "issue": "456"},
)

pyro.write_workspace_file(alpha["workspace_id"], "branch.txt", text="alpha\n")
pyro.write_workspace_file(beta["workspace_id"], "branch.txt", text="beta\n")
pyro.update_workspace(alpha["workspace_id"], labels={"branch": "alpha", "owner": "alice"})
pyro.list_workspaces()
pyro.delete_workspace(alpha["workspace_id"])
pyro.delete_workspace(beta["workspace_id"])
```

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.