sesh

Use this skill when the user wants to use sesh — the multi-machine coding-agent session manager — not develop it. sesh is one Go binary plus a per-machine daemon.

Mental model: each machine runs a daemon that owns a local SQLite store, drives a tmux "work" server, and maintains a background probe of every local thread's live state. A thread's runtime identity is its pane (a @sesh-thread-id marker), so a tmux session may host many threads (their own windows, or splits) — by default a new thread gets its own session, but see --into-session/--into-window/--into-pane. Daemons are linked into a mesh (peers, over ssh or an HTTP API) so any machine can see and route to threads on any other. The CLI/TUI is a thin client over the local daemon's HTTP+JSON surface; --machine <m> routes a command to machine m. sesh is mechanism, not UX — it is explicit and machine-readable (--json everywhere); ergonomic shell glue lives in the user's dotfiles.