Parcels

parcels

Package your work — repo, uncommitted changes, .env files, and the live agent
session — and ship it over Tailscale to another machine, where the agent resumes
in tmux and keeps working.

Supports Claude Code, Codex, pi, Droid, and Grok Build sessions.

Install

This symlinks parcel into ~/.local/bin, installs the /parcel skill for
Claude Code (~/.claude/skills/parcel) and Grok Build (~/.grok/skills/parcel)
when those homes exist, and seeds ~/.parcels/targets/ with an example target
config. Requirements: ssh access to your targets (Tailscale MagicDNS names
work great), rsync, tmux + the agent CLIs on the targets.

How it works

1. HANDOFF.md — the sending agent writes its intent (what it was doing, next
   steps, gotchas) at the repo root; parcel appends a mechanical state snapshot
   (branch, last commit, git status). This is the universal fallback: any agent
   on any machine can pick up from it.
2. Working tree — rsync of the whole repo including .git, untracked files,
   and .envs (excludes node_modules, .venv, pycache, build dirs).
3. Session transplant — the session transcript is copied into the remote
   agent's expected per-project location (each agent sanitizes the cwd path
   differently; parcel knows all five layouts) so native resume works:
   - claude: ~/.claude/projects//.jsonl → claude --resume
   - codex: ~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl → codex exec resume
   - pi: ~/.pi/agent/sessions//*.jsonl → pi -c
   - droid: ~/.factory/sessions//.jsonl (+ index entry) → droid exec -s
   - grok: ~/.grok/sessions/// → grok --resume
4. Launch — a tmux session parcel- starts on the target and the agent
   resumes with your prompt (default: "read HANDOFF.md and continue"). Attach any
   time: ssh -t  tmux attach -t parcel-.

Targets

One file per…