Introduce explicit repro-fix, inspect, cold-start, and review-eval modes across the MCP server, CLI, and host helpers, with canonical mode-to-tool mappings, narrowed schemas, and mode-specific tool descriptions on top of the existing workspace runtime. Reposition the docs, host onramps, and use-case recipes so named modes are the primary user-facing startup story while the generic no-mode workspace-core path remains the escape hatch, and update the shared smoke runner to validate repro-fix and cold-start through mode-backed servers. Validation: UV_OFFLINE=1 UV_CACHE_DIR=.uv-cache uv run pytest --no-cov tests/test_api.py tests/test_server.py tests/test_host_helpers.py tests/test_public_contract.py tests/test_cli.py tests/test_workspace_use_case_smokes.py; UV_OFFLINE=1 UV_CACHE_DIR=.uv-cache make check; UV_OFFLINE=1 UV_CACHE_DIR=.uv-cache make dist-check; real guest-backed make smoke-repro-fix-loop smoke-cold-start-validation outside the sandbox.
1.7 KiB
1.7 KiB
Workspace Use-Case Recipes
These recipes turn the chat-host workspace path into five concrete agent flows. They are the canonical next step after the quickstart in install.md or first-run.md.
Run all real guest-backed scenarios locally with:
make smoke-use-cases
Recipe matrix:
| Use case | Recommended mode | Smoke target | Recipe |
|---|---|---|---|
| Cold-start repo validation | cold-start |
make smoke-cold-start-validation |
cold-start-repo-validation.md |
| Repro plus fix loop | repro-fix |
make smoke-repro-fix-loop |
repro-fix-loop.md |
| Parallel isolated workspaces | repro-fix |
make smoke-parallel-workspaces |
parallel-workspaces.md |
| Unsafe or untrusted code inspection | inspect |
make smoke-untrusted-inspection |
untrusted-inspection.md |
| Review and evaluation workflows | review-eval |
make smoke-review-eval |
review-eval-workflows.md |
All five recipes use the same real Firecracker-backed smoke runner:
uv run python scripts/workspace_use_case_smoke.py --scenario all --environment debian:12
That runner generates its own host fixtures, creates real guest-backed workspaces,
verifies the intended flow, exports one concrete result when relevant, and cleans
up on both success and failure. Treat make smoke-use-cases as the trustworthy
guest-backed verification path for the advertised workspace workflows.
For a concise review before exporting, resetting, or handing work off, use:
pyro workspace summary WORKSPACE_ID