Thales Maciel
9b9b83ebeb
Extend the chat ergonomics roadmap now that the core workspace and MCP path are in place for the narrowed chat-host persona. Add the next planned phase around project-aware chat startup, host bootstrap and repair, reviewable agent output, opinionated use-case modes, and faster daily loops so the roadmap keeps pushing toward a repo-aware daily tool instead of a generic VM or SDK story. Document the constraints explicitly: optimize the MCP/chat-host path first, keep disk tools secondary, and take advantage of the current no-users-yet window to make breaking product-shaping changes when needed.
53 lines
1.7 KiB
Markdown
53 lines
1.7 KiB
Markdown
# `4.2.0` Host Bootstrap And Repair
|
|
|
|
Status: Planned
|
|
|
|
## Goal
|
|
|
|
Make supported chat hosts feel one-command to connect and easy to repair when a
|
|
local config drifts or the product changes shape.
|
|
|
|
## Public API Changes
|
|
|
|
The CLI should grow a small host-helper surface for the supported chat hosts:
|
|
|
|
- `pyro host connect claude-code`
|
|
- `pyro host connect codex`
|
|
- `pyro host print-config opencode`
|
|
- `pyro host doctor`
|
|
- `pyro host repair HOST`
|
|
|
|
The exact names can still move, but the product needs a first-class bootstrap
|
|
and repair path for Claude Code, Codex, and OpenCode.
|
|
|
|
## Implementation Boundaries
|
|
|
|
- host helpers should wrap the same `pyro mcp serve` entrypoint rather than
|
|
introduce per-host runtime behavior
|
|
- config changes should remain inspectable and predictable
|
|
- support both installed-package and `uvx`-style usage where that materially
|
|
reduces friction
|
|
- keep the host helper story narrow to the current supported hosts
|
|
|
|
## Non-Goals
|
|
|
|
- no GUI installer or onboarding wizard
|
|
- no attempt to support every possible MCP-capable editor or chat shell
|
|
- no hidden network service or account-based control plane
|
|
|
|
## Acceptance Scenarios
|
|
|
|
- a new Claude Code or Codex user can connect `pyro` with one command
|
|
- an OpenCode user can print or materialize a correct config without hand-writing
|
|
JSON
|
|
- a user with a stale or broken local host config can run one repair or doctor
|
|
flow instead of debugging MCP setup manually
|
|
|
|
## Required Repo Updates
|
|
|
|
- new host-helper docs and examples for all supported chat hosts
|
|
- README, install docs, and integrations docs updated to prefer the helper
|
|
flows when available
|
|
- help text updated with exact connect and repair commands
|
|
- runnable verification or smoke coverage that proves the shipped host-helper
|
|
examples stay current
|