thaloco/pyro-mcp
1
Fork 0
Code Pull requests Releases Packages Activity Actions
pyro-mcp/docs/roadmap/llm-chat-ergonomics/3.8.0-chat-host-onramp-and-recommended-defaults.md
Thales Maciel 788fc4fad4
Add second-pass chat UX milestones 
Extend the chat-ergonomics roadmap with the remaining UX work highlighted by the readiness review.

Document a second pass focused on removing shell glue from canonical CLI handoff flows, making the recommended chat-host profile more obvious without changing 3.x compatibility defaults, and polishing human-mode content reads for cleaner transcripts and copy-paste behavior.

Keep these milestones explicitly workspace-first and scoped to product UX, with CLI-only shortcuts allowed where the SDK and MCP surfaces already provide the structured behavior natively.
2026-03-13 10:44:44 -03:00

1.6 KiB
Raw Blame History

3.8.0 Chat-Host Onramp And Recommended Defaults

Status: Planned

Goal

Make the recommended chat-host entrypoint obvious before a new integrator has to read deep integration docs.

Public API Changes

No breaking API change is required in this milestone.

The main user-visible change is guidance:

  • pyro mcp serve help text should clearly call workspace-core the recommended chat-host profile
  • README, install docs, first-run docs, and shipped MCP configs should all lead with workspace-core
  • workspace-full should be framed as the explicit advanced/compatibility surface for 3.x

Implementation Boundaries

  • keep the 3.x compatibility default unchanged
  • do not add new profile names
  • make the recommendation visible from help text and top-level docs, not only the integrations page
  • keep provider examples and MCP examples aligned on the same profile story

Non-Goals

  • no breaking default flip to workspace-core in 3.x
  • no new hidden server behavior based on client type
  • no divergence between CLI, SDK, and MCP terminology for the profile ladder

Acceptance Scenarios

  • a new chat-host integrator sees workspace-core as the recommended first MCP profile from the first help/doc pass
  • the top-level docs include one tiny chat-host quickstart near the first-run path
  • shipped config examples and provider examples all align on the same profile progression

Required Repo Updates

  • top-level docs updated with a minimal chat-host quickstart
  • pyro mcp serve --help rewritten to emphasize workspace-core
  • examples and config snippets audited so they all agree on the recommended profile