Moshi Best Practices

This walks you through making any host feel native to Moshi, whether you're doing a fresh setup or debugging an existing one. It covers Easy Pair QR setup for SSH/Mosh access, fixing PATH issues in non-interactive shells, configuring tmux defaults, creating project-rooted tmux sessions, and using the MOSHI_CLIENT environment variable to adapt your shell and tmux config when connecting from the iOS app. The newer section on moshi-hook is worth attention: it replaced the old fire-and-forget CLI with a persistent WebSocket daemon that lets you approve or deny Claude Code tool calls from iOS Live Activities or Apple Watch, with the response traveling back to the terminal in real time. Solid for anyone running agents on remote machines through Moshi.

skills.sh installs: 2.1K
GitHub stars: 31
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add rjyo/moshi-skill --skill moshi-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

Moshi Best Practices

Use this skill to make any host feel easy to use from Moshi.

Use it for either:

fresh setup
verification of an existing setup

Moshi treats Herdr, tmux, and Zellij as first-class multiplexers. Herdr support landed in iOS 3.1; the workflow features below assume 3.10 or later. Prefer Herdr for agent work: Jump To, Chat View, Agents inbox, deep links, two-finger session/space/pane swipes, and Open Terminal all land more cleanly on Herdr workspaces and agent tabs. Keep tmux installed even on Herdr-first hosts — the packaged moshi DIR launcher and Moshi's Recent-directories one-tap flow still create tmux sessions. Zellij is supported when the user already runs it.