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.
56 lines
2.1 KiB
Markdown
56 lines
2.1 KiB
Markdown
# `4.1.0` Project-Aware Chat Startup
|
|
|
|
Status: Planned
|
|
|
|
## Goal
|
|
|
|
Make "current repo to disposable sandbox" the default story for the narrowed
|
|
chat-host user, without requiring manual workspace seeding choreography first.
|
|
|
|
## Public API Changes
|
|
|
|
The chat entrypoint should gain one documented project-aware startup path:
|
|
|
|
- `pyro mcp serve` should accept an explicit local project source, such as the
|
|
current checkout
|
|
- the product path should optionally support a clean-clone source, such as a
|
|
repo URL, when the user is not starting from a local checkout
|
|
- the first useful chat turn should not depend on manually teaching
|
|
`workspace create ... --seed-path ...` before the host can do real work
|
|
|
|
Exact flag names can still change, but the product needs one obvious "use this
|
|
repo" path and one obvious "start from that repo" path.
|
|
|
|
## Implementation Boundaries
|
|
|
|
- keep host crossing explicit; do not silently mutate the user's checkout
|
|
- prefer local checkout seeding first, because that is the most natural daily
|
|
chat path
|
|
- preserve existing explicit sync, export, diff, and reset primitives rather
|
|
than inventing a hidden live-sync layer
|
|
- keep the startup story compatible with the existing `workspace-core` product
|
|
path
|
|
|
|
## Non-Goals
|
|
|
|
- no generic SCM integration platform
|
|
- no background multi-repo workspace manager
|
|
- no always-on bidirectional live sync between host checkout and guest
|
|
|
|
## Acceptance Scenarios
|
|
|
|
- from a repo root, a user can connect Claude Code, Codex, or OpenCode and the
|
|
first workspace starts from that repo without extra terminal choreography
|
|
- from outside a repo checkout, a user can still start from a documented clean
|
|
source such as a repo URL
|
|
- the README and install docs can teach a repo-aware chat flow before the
|
|
manual terminal workspace flow
|
|
|
|
## Required Repo Updates
|
|
|
|
- README, install docs, first-run docs, integrations docs, and public contract
|
|
updated to show the repo-aware chat startup path
|
|
- help text updated so the repo-aware startup path is visible from `pyro` and
|
|
`pyro mcp serve --help`
|
|
- at least one recipe and one real smoke scenario updated to validate the new
|
|
startup story
|