← ClaudeAtlas

session-porterlisted

Full context for Claude Code session export/import/migration operations via sesh-mover CLI
Sertelegger/claude-sesh-mover · ★ 1 · Data & Documents · score 65
Install: claude install-skill Sertelegger/claude-sesh-mover
# sesh-mover Session Porter Skill This skill provides background knowledge for all sesh-mover slash commands. It is not invoked directly by users — the individual commands (export, import, migrate, browse, configure, hub-init, hub-encrypt, hub-rekey, push, pull, whereis, hub-unlink, hub-retire, hub-delete) reference this knowledge. ## CLI Location The sesh-mover CLI is at `${CLAUDE_PLUGIN_ROOT}/dist/cli.js`. Claude Code sets `CLAUDE_PLUGIN_ROOT` automatically inside plugin command execution, so **no plugin-cache discovery is needed** — invoke directly: ```bash node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" <command> [options] ``` Do not run `find` over `~/.claude*/plugins/cache` to locate the plugin; the env var is authoritative. All commands output structured JSON to stdout. Parse it with JSON.parse(). (The two internal hook endpoints, `hub hook-session-end` and `hub hook-session-start`, are the deliberate exception — they speak Claude Code's hook protocol and are never invoked from this skill layer. See "Hub automation" below.) ## Exit Codes **Keep branching on the parsed JSON, not on the exit code** — the body is what carries `reason`, `linkCandidates`, `warnings` and everything else a command flow needs. But the codes exist and mean something specific, so know them: a non-zero exit is *never* a reason to discard the JSON, and a zero exit is not by itself proof of success (a `--dry-run`, a `collision: true` export and an `upToDate: true` push all exit 0 and all need their