Add workspace summary across the CLI, SDK, and MCP, and include it in the workspace-core profile so chat hosts can review one concise view of the current session. Persist lightweight review events for syncs, file edits, patch applies, exports, service lifecycle, and snapshot activity, then synthesize them with command history, current services, snapshot state, and current diff data since the last reset. Update the walkthroughs, use-case docs, public contract, changelog, and roadmap for 4.3.0, and make dist-check invoke the CLI module directly so local package reinstall quirks do not break the packaging gate. Validation: uv lock; ./.venv/bin/pytest --no-cov tests/test_vm_manager.py tests/test_cli.py tests/test_api.py tests/test_server.py tests/test_public_contract.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 workspace create -> patch apply -> workspace summary --json -> delete smoke.
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 profile | Smoke target | Recipe |
|---|---|---|---|
| Cold-start repo validation | workspace-full |
make smoke-cold-start-validation |
cold-start-repo-validation.md |
| Repro plus fix loop | workspace-core |
make smoke-repro-fix-loop |
repro-fix-loop.md |
| Parallel isolated workspaces | workspace-core |
make smoke-parallel-workspaces |
parallel-workspaces.md |
| Unsafe or untrusted code inspection | workspace-core |
make smoke-untrusted-inspection |
untrusted-inspection.md |
| Review and evaluation workflows | workspace-full |
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