Using the mw CLI (what has been verified)¶
Only commands that were actually run are listed. Evidence and full results: CLI investigation.
Where it runs¶
The CLI lives in WSL2 (Ubuntu), not native Windows. Open a WSL shell first:
wsl
which mw # ~/.local/bin/mw -> ~/.machineworld/install/v0.2.9/cli/bin/mw-launcher.sh
mw --version # prints 0.2.0 (the install folder says v0.2.9; `mw version` says v0.1.0)
Read-only commands verified on 2026-10-27¶
| Command | What you get |
|---|---|
mw --help |
Command groups: Quick wins, Everyday, Diagnostics, Knowledge, System, Remote |
mw doctor |
Health report: LLM backend, skills loaded, onboarding, keyring, telemetry |
mw skills |
Skill registry with production / draft status |
mw mcp list |
MCP registry entries |
mw workflow list |
Workflow files, with parse errors flagged |
mw connected |
Which MCPs have credentials; workflows with past runs |
mw audit |
Today's events, spend, bytes sent off the machine |
mw history |
The CLI's own chat history (not meeting history) |
mw lang, mw sinhala style-status |
Language settings, Sinhala style-guide status |
mw household list, mw daemon status, mw whoami |
Households; daemon state; login state (Not logged in.) |
--help is not always safe
mw inbox --help ran the inbox command instead of printing help. Check a command's behaviour before adding --help to anything that sends, deletes or logs in.
Interactive chat¶
mw with no arguments opens the chat. In your June 2026 sessions it routed prompts to skills and answered through the Claude Code CLI backend, 28–174 s per reply. Things to know from those logs:
- Typing
mw doctorinside the chat gives an AI-written answer, not the real command. Run real commands in the shell. - "Offline", "Gateway Not connected" and "pipeline call timed out after 180s" appeared in the status bar; no fix was found in-session.
- Some replies failed with
claude CLI failed (exit 1): Warning: no stdin data received in 3s.
Not verified¶
Login and the remote tier, vault, sync, --remote with OpenRouter, --offline, voice and visual modes, running any workflow, the daemon. Do not rely on them until tested.
What the CLI cannot do for this documentation¶
It has no commands for meetings, recordings or transcripts, so it cannot reconstruct discussion history. Its value here is as evidence of what is implemented.