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.1 KiB
1.1 KiB
Codex MCP Setup
Recommended modes:
repro-fixinspect
Preferred helper flow:
pyro host connect codex --mode repro-fix
pyro host connect codex --mode inspect
pyro host doctor --mode repro-fix
Package without install:
codex mcp add pyro -- uvx --from pyro-mcp pyro mcp serve --mode repro-fix
codex mcp list
Run that from the repo root when you want the first workspace_create to start
from the current checkout automatically.
Already installed:
codex mcp add pyro -- pyro mcp serve --mode repro-fix
codex mcp list
If Codex launches the server from an unexpected cwd, pin the project explicitly:
pyro host connect codex --mode repro-fix --project-path /abs/path/to/repo
codex mcp add pyro -- uvx --from pyro-mcp pyro mcp serve --mode repro-fix --project-path /abs/path/to/repo
If the local config drifts later:
pyro host repair codex --mode repro-fix
Move to workspace-full only when the chat truly needs shells, services,
snapshots, secrets, network policy, or disk tools:
codex mcp add pyro -- uvx --from pyro-mcp pyro mcp serve --profile workspace-full