Add project-aware chat startup defaults
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.
This commit is contained in:
parent
9b9b83ebeb
commit
535efc6919
28 changed files with 968 additions and 67 deletions
29
README.md
29
README.md
|
|
@ -30,7 +30,7 @@ SDK-first platform.
|
|||
- Troubleshooting: [docs/troubleshooting.md](docs/troubleshooting.md)
|
||||
- Stable workspace walkthrough GIF: [docs/assets/workspace-first-run.gif](docs/assets/workspace-first-run.gif)
|
||||
- Terminal walkthrough GIF: [docs/assets/first-run.gif](docs/assets/first-run.gif)
|
||||
- What's new in 4.0.0: [CHANGELOG.md#400](CHANGELOG.md#400)
|
||||
- What's new in 4.1.0: [CHANGELOG.md#410](CHANGELOG.md#410)
|
||||
- PyPI package: [pypi.org/project/pyro-mcp](https://pypi.org/project/pyro-mcp/)
|
||||
|
||||
## Who It's For
|
||||
|
|
@ -76,7 +76,7 @@ What success looks like:
|
|||
```bash
|
||||
Platform: linux-x86_64
|
||||
Runtime: PASS
|
||||
Catalog version: 4.0.0
|
||||
Catalog version: 4.1.0
|
||||
...
|
||||
[pull] phase=install environment=debian:12
|
||||
[pull] phase=ready environment=debian:12
|
||||
|
|
@ -96,13 +96,26 @@ for the guest image.
|
|||
## Chat Host Quickstart
|
||||
|
||||
After the quickstart works, the intended next step is to connect a chat host.
|
||||
Bare `pyro mcp serve` starts `workspace-core`, which is the default product
|
||||
path.
|
||||
From a repo root, bare `pyro mcp serve` starts `workspace-core`, auto-detects
|
||||
the current Git checkout, and lets the first `workspace_create` omit
|
||||
`seed_path`.
|
||||
|
||||
```bash
|
||||
uvx --from pyro-mcp pyro mcp serve
|
||||
```
|
||||
|
||||
If the host does not preserve the server working directory, use:
|
||||
|
||||
```bash
|
||||
uvx --from pyro-mcp pyro mcp serve --project-path /abs/path/to/repo
|
||||
```
|
||||
|
||||
If you are starting outside a local checkout, use a clean clone source:
|
||||
|
||||
```bash
|
||||
uvx --from pyro-mcp pyro mcp serve --repo-url https://github.com/example/project.git
|
||||
```
|
||||
|
||||
Copy-paste host-specific starts:
|
||||
|
||||
- Claude Code: [examples/claude_code_mcp.md](examples/claude_code_mcp.md)
|
||||
|
|
@ -136,6 +149,10 @@ OpenCode `opencode.json` snippet:
|
|||
}
|
||||
```
|
||||
|
||||
If OpenCode launches the server from an unexpected cwd, add
|
||||
`"--project-path", "/abs/path/to/repo"` after `"serve"` in the same command
|
||||
array.
|
||||
|
||||
If `pyro-mcp` is already installed, replace `uvx --from pyro-mcp pyro` with
|
||||
`pyro` in the same command or config shape.
|
||||
|
||||
|
|
@ -146,7 +163,9 @@ snapshots, secrets, network policy, or disk tools.
|
|||
|
||||
1. Validate the host with `pyro doctor`.
|
||||
2. Pull `debian:12` and prove guest execution with `pyro run debian:12 -- git --version`.
|
||||
3. Connect Claude Code, Codex, or OpenCode with `pyro mcp serve`.
|
||||
3. Connect Claude Code, Codex, or OpenCode with `pyro mcp serve` from a repo
|
||||
root, or use `--project-path` / `--repo-url` when cwd is not the source of
|
||||
truth.
|
||||
4. Start with one recipe from [docs/use-cases/README.md](docs/use-cases/README.md).
|
||||
`repro-fix-loop` is the shortest chat-first story.
|
||||
5. Use `make smoke-use-cases` as the trustworthy guest-backed verification path
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue