Make repo-root chat startup native by letting MCP servers carry a default project source for workspace creation. When a chat host starts from a Git checkout, workspace_create can now omit seed_path and inherit the server startup source; explicit --project-path and clean-clone --repo-url/--repo-ref paths are supported as fallbacks. Add project startup resolution and materialization, surface origin_kind/origin_ref in workspace_seed, update chat-host docs and the repro/fix smoke to use project-aware workspace creation, and switch dist-check to uv run pyro so verification stays stable after uv reinstalls. Validated with uv lock, focused startup/server/CLI pytest coverage, UV_CACHE_DIR=.uv-cache make check, UV_CACHE_DIR=.uv-cache make dist-check, and real guest-backed smokes for both explicit project_path and bare repo-root auto-detection. |
||
|---|---|---|
| .. | ||
| cold-start-repo-validation.md | ||
| parallel-workspaces.md | ||
| README.md | ||
| repro-fix-loop.md | ||
| review-eval-workflows.md | ||
| untrusted-inspection.md | ||
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.