Skip to content

Releases

v0.3.0

Choose a tag to compare

@ejklock ejklock released this 15 Nov 22:19

A session can now move itself with a slash command: /hc-teleport <machine> in Claude Code, Codex, OpenCode and Pi runs hc-teleport <machine> --detach and ends the agent's turn, so the session moves once it is idle. The CLI itself is unchanged from v0.2.0.

Changes

  • Claude Code: add the marketplace with /plugin marketplace add ejklock/hc-teleport, then install hc-teleport@hc-teleport. The command is /hc-teleport, because Claude Code's built-in /teleport handles cloud sessions.
  • Codex: codex plugin marketplace add ejklock/hc-teleport, then codex plugin add hc-teleport@hc-teleport. Codex gets the skill.
  • OpenCode and Pi: the npm package hc-teleport-agent adds the /hc-teleport command and the skill (OpenCode through its plugin config hook, Pi through a prompt template).
  • Claude Code sessions only, for now: the CLI moves Claude Code sessions. In another agent's session the command reports not_claude, and the agent tells the person that its sessions cannot move yet.
  • What the agent is told: run the command once and end the turn without waiting; on not_initialized, ask the person to run hc-teleport init in a terminal; with no machine named, offer the machines hc-teleport doctor lists.

Requirements

hc-teleport v0.3.0 (or v0.2.0) on the PATH, a config written by hc-teleport init, Node 26 and hc. See the README's Plugins section.

v0.2.0

Choose a tag to compare

@ejklock ejklock released this 15 Nov 21:32

A coding-agent session can now move itself: from inside a Claude Code session in an hc terminal, hc-teleport <machine> --detach hands the move to a runner terminal and returns at once. This release also requires a one-time setup, and adds moves between machines that share a disk.

Breaking change

  • Run hc-teleport init once. Every move and --dry-run now refuses not_initialized until hc-teleport init has stored which machines may receive a session (~/.config/hc-teleport/config.json). A destination outside that list refuses machine_not_allowed.

Changes

  • Move a session from inside it: hc-teleport <machine> --detach [--wait <s>] starts a runner terminal named hct-<session> on the core, which waits for the session to be idle and then moves it. A second --detach for the same session refuses move_in_progress. When the move fails and the session still runs, the runner types hc-teleport: <phase> (<reason>); see hc-teleport status into it.
  • See detached moves: hc-teleport status [--json] lists each detached move with its start time, phase and runner, and marks runner_lost when the runner died.
  • Choose and check machines: hc-teleport init is an interactive wizard. hc-teleport doctor [--json] checks that hc reaches each allowed machine and that claude --version runs there.
  • Relocate on one disk: when the source and destination share the session's disk (same device and inode of the transcript), the move copies nothing. It stops the source, then resumes on the destination, and resumes on the source again if the destination does not come up. Two hc machines on one disk may move directly. --dry-run --json reports "relocate": true|false.
  • Real sessions are recognized: a session started by herdr-wake or by a wrapper such as claude-klock is found from the terminal's wake label, checked against Claude Code's pid registry, and resumed with its own profile (env CLAUDE_CONFIG_DIR=…). v0.1.0 refused these sessions as not_claude.
  • Fixes: a failed put-back of the transcript is reported; hc get gets -- before the address; the test bed no longer fails on an unread stdin.

Requirements

Node 26 and hc on the PATH. See the README for usage, output, refusals and exit codes.

v0.1.0

Choose a tag to compare

@ejklock ejklock released this 13 Nov 20:10

The first release of hc-teleport: it moves a Claude Code session that runs in an hc terminal from the Mac to another hc machine, and back.

Changes

  • Move a session: hc-teleport <terminal> <machine> plans the move, checks the destination (preflight), carries the git checkout and the transcript, resumes the session in a new terminal on the destination, then stops the source terminal and parks its checkout. A refusal before the first write changes nothing; a destination that does not come up is rolled back.
  • The way back: hc-teleport dev-home/<t> local brings a session from an hc machine back to the Mac with the same flow.
  • Plan only: --dry-run prints what a move would resume and writes nothing; --json prints one JSON object.
  • Resume as it ran: the destination runs the same launcher (such as claude-klock) with its allowed flags and --resume <id>; an unknown flag refuses and is named.

Requirements

Node 26 and hc on the PATH, on the Mac. See the README for usage, output and exit codes.