moshi-best-practices

Use this skill to make any host feel easy to use from Moshi. Use it for either: Target outcome: Inspect with a small set of real checks. Keep OS-specific mechanics minimal, but do not skip verification. Useful checks: Useful macOS-specific checks when relevant: Verify after changes: Then ask the user to reconnect from Moshi. Expected result: the tmux selector appears, and the transport can use Mosh instead of plain SSH when configured. Use these defaults unless the user wants something different: Workflow: MOSHI_CLIENT=1 is an opt-in environment variable the Moshi iOS client exports into the remote shell so rc files, prompts, and tmux configs can detect a Moshi-launched session and adapt. The user enables it in the app under Settings → Integrations → Export ENV (off by default). When on, it is set identically on both the Mosh path (via mosh-server -l MOSHI_CLIENT=1 ) and the SSH fallback (via an injected export at shell start).