Teleport

Teleport moves a running Claude Code session's work between any two computers you have in Melta, in either direction, with one tap: laptop to server, server to laptop, server to server. The work travels through git, and a session on the other computer picks it up.

Direction does not matter: the phone reaches both computers and runs the same steps on whichever one is the source and whichever one is the target.

The one tap

On the host screen, long-press a Claude Code session and choose Teleport…, or pick it from the session's menu, then pick the other computer. Both computers need Chief set up and the project's git remote. The session must be idle.

What moves

• A handoff. The session writes its goal, state, next steps and decisions while its cache is still warm.
• The work. Changes are committed as a work-in-progress commit and pushed on the session's branch. Teleport never pushes main: when the session is on main, it makes a new teleport/ branch first. It never force-pushes.
• The transcript, when it is under 5 MB.

What stays

Nothing is deleted on the first computer. .env files, keys and credential files never travel: set them up on the other computer. The handoff says so when there were some.

On the other computer

Melta clones the project when it is not there yet, opens a git worktree on the branch, and starts Claude Code. When the transcript came along, the session resumes; otherwise it starts from the handoff. The first computer's row then shows Teleported to the other computer, and its one action is Close.

Examples

• Lid closing: laptop to server. Leaving mid-task? Teleport to your server and the session carries on while the laptop sleeps.
• Back home: server to laptop. Teleport the server's session back. The laptop's worktree on the branch is fast-forwarded and the session continues there.
• Heavy build: small VM to big VM. Server to server works the same way, because the phone reaches both.

Common questions

Must the session be idle?

Yes. Wait until it has finished its turn, or answer its question first.

Can I teleport the work back?

Yes. The branch's worktree on the first computer is brought up to date and the session continues there.

Why does it say there is no git remote?

Teleport needs a remote both computers can reach. Add one with git remote add origin <url>.

What if the push is rejected?

Nothing moves. Fix the push on the first computer, for example pull first, then teleport again.