matrix-onboarding
Matrix OS Setup and Recovery
Prepare the user's Matrix cloud computer without collecting or transferring local secrets. Prefer the bundled hosted Matrix MCP tools with browser OAuth; no Matrix CLI installation is needed. Keep the separately authenticated CLI fallback optional for diagnosis and recovery.
MCP readiness
When remote tools are available, call list_computers first. After selecting an explicit runtimeSlot, use run_command for captured readiness checks and the terminal tools (create_terminal, create_terminal_tab, select_terminal_tab, and send_terminal_input) for observable authentication or recovery work. Never pass credentials as tool arguments.
For HTTP authentication failures, use codex mcp login <configured-server-name> or Claude Code's /mcp browser authentication. matrix login repairs only stdio/CLI credentials. If hosted tools are unavailable, explain the status and offer the CLI fallback. Never collect OAuth tokens or codes in chat. Hosted run_command takes a command array and defaults to/caps at 45 seconds; longer work belongs in persistent terminals.