Thales Maciel d0cf6d8f21 Add opinionated MCP modes for workspace workflows

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.

2026-03-13 20:00:35 -03:00

2.3 KiB

Raw Blame History

MCP Client Config Example

Recommended named modes for most chat hosts in 4.x:

repro-fix
inspect
cold-start
review-eval

Use the host-specific examples first when they apply:

Claude Code: examples/claude_code_mcp.md
Codex: examples/codex_mcp.md
OpenCode: examples/opencode_mcp_config.json

Preferred repair/bootstrap helpers:

pyro host connect codex --mode repro-fix
pyro host connect codex --mode inspect
pyro host connect claude-code --mode cold-start
pyro host connect claude-code --mode review-eval
pyro host print-config opencode --mode repro-fix
pyro host doctor --mode repro-fix
pyro host repair opencode --mode repro-fix

Use this generic config only when the host expects a plain mcpServers JSON shape or when the named modes are too narrow for the workflow.

pyro-mcp is intended to be exposed to LLM clients through the public pyro CLI.

Generic stdio MCP configuration using uvx:

{
  "mcpServers": {
    "pyro": {
      "command": "uvx",
      "args": ["--from", "pyro-mcp", "pyro", "mcp", "serve", "--mode", "repro-fix"]
    }
  }
}

If pyro-mcp is already installed locally, the same server can be configured with:

{
  "mcpServers": {
    "pyro": {
      "command": "pyro",
      "args": ["mcp", "serve", "--mode", "repro-fix"]
    }
  }
}

If the host does not preserve the server working directory and you want the first workspace_create to start from a specific checkout, add "--project-path", "/abs/path/to/repo" after "serve" in the same args list.

Mode progression:

repro-fix: patch, rerun, diff, export, reset
inspect: narrow offline-by-default inspection
cold-start: validation plus service readiness
review-eval: shell and snapshot-driven review
generic no-mode path: the fallback when the named mode is too narrow
workspace-full: explicit advanced opt-in for shells, services, snapshots, secrets, network policy, and disk tools

Primary mode for most agents:

repro-fix

Use lifecycle tools only when the agent needs persistent VM state across multiple tool calls.

Other generic-client examples:

Claude Desktop: examples/claude_desktop_mcp_config.json
Cursor: examples/cursor_mcp_config.json

2.3 KiB Raw Blame History

MCP Client Config Example

2.3 KiB

Raw Blame History