Entangle

entangle

Hand a live coding session to anyone.

Claude Code, Codex, and opencode.

Encrypted, no account, three spoken words.

If this saves you a hand-off, a star helps other people find it.

Your coding sessions live only on the machine that made them. So the day you want to
hand a conversation to a teammate, or move to a new laptop, you are stuck: copying the
folder by hand does not work, because every session is pinned to the exact path your
project sat at, and that path is different everywhere else.

entangle makes it one command. Send a live session straight to someone with a short
code they type in, or pack your whole history and carry it to a new machine, with every
path rewritten so the conversation opens where it left off.

It works across coding agents, not just one. A Claude Code session goes to Claude Code,
a Codex session to Codex, an opencode session to opencode - listed together, shared the
same way. (Opening one tool's session *inside another* is a different problem, and not
one this solves yet.)

Two scopes, and it matters which you need. Sharing one session covers all three tools.
Packing a whole machine covers Claude Code only so far - move a Codex or opencode
session with entangle share instead. entangle export tells you what it left out rather
than letting you discover it on the new laptop.

It is private by construction. Nothing is uploaded, there is no account and no server in
the middle; a direct transfer is end-to-end encrypted, likely secrets are scrubbed before
anything leaves your machine, and your login never travels at all. The one exception is an
anonymous once-a-day check for a new release, which sends nothing about you and
can be turned off.
Renamed. This project was claude-teleport until it outgrew a single vendor.
The old command…