Onboarding: reliable MCP attach + setup wizard, and a Windows-native MCP package (1.5.0)

[mertkayacs]

First-time setup is harder than it should be, and the MCP attach path is the sharpest edge.

Problems

• attach writes a bare reevesagents mcp command, so a host CLI that launches the server with a different PATH (nvm/fnm/pnpm/volta installs, GUI-launched CLIs) silently fails to start it. attach and hosts both still report success, so the failure is invisible.
• claude mcp add defaults to local scope, so an attach in one directory does not show up in another.
• attach never verifies the server actually launches, and never reminds you to restart the host CLI.
• No guided first-run: install is passive by design, but nothing walks a newcomer from install to a first driven agent.

Plan (1.5.0)

• Harden attach: resolve an absolute launcher (PATH-independent), pin user scope for Claude Code, self-verify the server starts, print a restart reminder
• doctor: add an MCP self-launch check
• Agent-facing MCP onboarding payload (what it is + the exact commands to run)
• Setup wizard + short tutorial across CLI, TUI, and Web (all 10 languages)
• A separate, maintained Windows-native MCP-only package (ConPTY instead of tmux)
• Dogfood the whole flow, fix every bug found, then release

Keeps every invariant: still goes through each CLI's own mcp add, no stored credentials, passive install, loopback web.