claw-mo-up

# claw-mo-up Bring up the mo markdown viewer for the current project and open the browser. When a server is already running, **restart it by default** so new files on disk become visible (fsnotify can silently miss events). For config schema, decision tree, `--restart` vs `--clear` semantics, and browser opening: read `${CLAUDE_PLUGIN_ROOT}/references/shared.md` ## Arguments - `$ARGUMENTS` (optional) - `--reuse` — Skip `mo --restart` when live matches config. Use this when the running session is known-good and the user explicitly wants zero interruption. ## Steps > [!NOTE] > With autosync enabled (default), `/claw-mo-up` is only needed to (a) start mo for the first time in a session, (b) recover from a silent fsnotify miss via `mo --restart`, or (c) reconcile a drifted runtime to saved config. Routine new-file visibility does not require a restart anymore. 1. **Prerequisites**: `command -v mo >/dev/null 2>&1`. If missing, tell user `brew install k1LoW/tap/mo` and stop. 2. **Project key**: `git rev-parse --show-toplevel` (fallback: `$PWD`). 3. **Read config** from `${CLAUDE_PLUGIN_DATA}/config.json`. If no entry for this project, tell the user to run `/claw-mo-setup` and stop. 4. **v1 migration**: If the entry has `patterns` instead of `groups`, migrate to `groups` format and save back. 5. **Probe server**: `mo --status --json 2>/dev/null`. Extract the server whose port matches `$PORT`. 6. **Branch on state** — see the decision tree in `shared.md`: **(a) No s...