待翻譯：Show HN: Entangle, hand a live AI coding session to anyone with three words

AI 服務暫時不可用，以下為來源正文，待恢復後補全翻譯。

Notifications You must be signed in to change notification settings Fork 3 Star 20 BranchesTags Open more actions menu Folders and files NameName Last commit message Last commit date Latest commit History 122 Commits 122 Commits .github .github docs docs internal internal vscode vscode .gitignore .gitignore .goreleaser.yaml .goreleaser.yaml CONTRIBUTING.md CONTRIBUTING.md DESIGN.md DESIGN.md LICENSE LICENSE README.md README.md SECURITY.md SECURITY.md go.mod go.mod go.sum go.sum install.ps1 install.ps1 install.sh install.sh main.go main.go Repository files navigation Hand a live coding session to anyone. Claude Code, Codex, and opencode. Encrypted, no account, three spoken words. 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 still works and still updates itself; it will tell you how to switch. Install macOS and Linux: curl -fsSL https://gowthamsai.in/install.sh | sh With Homebrew: brew install gowtham-sai-yadav/tap/entangle Windows (PowerShell): irm https://gowthamsai.in/install.ps1 | iex Each one fetches the right prebuilt binary, verifies its checksum, and puts it on your PATH. Confirm with entangle version. Other ways: Go, direct download, from source With Go: go install github.com/gowtham-sai-yadav/entangle@latest This installs into $(go env GOPATH)/bin (usually ~/go/bin). If the command is not found afterward, that folder is not on your PATH yet: echo 'export PATH="$HOME/go/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc. Direct download: grab the file for your machine from the latest release (...-darwin-arm64 for Apple Silicon, -darwin-amd64 for Intel Macs, -linux-amd64, or -windows-amd64.exe), then on macOS/Linux chmod +x it and move it onto your PATH. From source: git clone https://github.com/gowtham-sai-yadav/entangle cd entangle && go build -o entangle . Start here: the interactive cockpit The quickest way in is to just run: entangle With a terminal attached, that opens a full-screen cockpit: your sessions in a searchable list, with every action a keypress away. Send one to a teammate over an encrypted code, share it to a file, receive one, export or import a backup, or update in place, all without remembering a single flag. Press ? for what each key does. Run entangle tui to open it explicitly; piped or scripted, the same binary behaves like a normal CLI. Prefer typing the commands yourself? Everything below works on its own too. Share a session with a teammate Hand one conversation to someone else, with all its context intact, so they can carry it forward. Find the session first: entangle sessions Then send it one of two ways. Straight across, by code (no file to move, nothing uploaded anywhere): entangle send You read out the short code it prints; they run entangle receive from their copy of the project. The transfer is end-to-end encrypted, so no server can read it. If they do not have entangle, you do not have to talk them through installing it. Both send and the cockpit's c key give you a message that is ready to paste into chat, with the install line and the receive command already in it: Run these from inside your copy of the project (skip the first line if you already have entangle): curl -fsSL https://gowthamsai.in/install.sh | sh entangle receive 6-pioneer-village Windows PowerShell: irm https://gowthamsai.in/install.ps1 | iex Received sessions attach to the directory they are run in, and every file path in the conversation is rewritten to match. That is why it says to run it from inside their copy of the project. From the wrong folder it still imports, but the paths in it point at files that are not there. This is what they see. It shows the rewrite it is about to do before it does it, then confirms the session can actually be resumed rather than leaving you to find out: Path remapping: /Users/alex/work/dashboard -> /Users/sam/projects/dashboard /Users/sam -> /Users/sam /Users/alex -> /Users/sam Projects: OLD NEW SESSIONS + /Users/alex/work/dashboard /Users/sam/projects/dashboard 1 Done. 1 file(s) written, 0 skipped (already present); 0 project entries merged into .claude.json. Verify: 1/1 migrated project(s) look resume-ready. IMPORTANT: your login was NOT transferred - credentials never are. Open Claude Code, log in once, then run claude --resume inside a project. As a file, if they are not around right now: entangle share They import it later with entangle import . Either way, likely secrets (keys, tokens, passwords) are scrubbed before anything leaves your machine, and your login is never included. --last picks your most recent session, and --with-context also includes the project's memory files. Move to a new machine Moving all of your work to a new computer is two commands, one on each. On the old machine, pack everything into a file: entangle export Copy the file it creates to the new machine any way you like: AirDrop, a USB stick, scp. On the new machine, install Claude Code and sign in once, then restore: entangle import entangle-backup-*.tgz It shows you every project and where it will land, asks you to confirm, fixes the paths, and checks your sessions are resume-ready. Add --dry-run to preview without writing anything, and --map /old/path=/new/path if it guesses a location wrong. Or import by clicking entangle gui does the same restore in a browser: point it at a bundle, see every project as a from → to row, untick what you do not want, and nothing is written until you confirm. Add a bundle path to skip straight to the review, or --port N to pin the port. It serves on 127.0.0.1 only and needs no network. Then open a project and carry on: cd ~/path/to/your/project claude --resume Your login does not transfer, on purpose. Credentials are locked to each machine, so just sign in once on the new one. In your editor Prefer to stay in VS Code? The entangle extension adds the same actions to the Command Palette, a status-bar button, and a sidebar: send a session by code, receive one, share to a file, or browse your sessions. It drives the CLI under the hood and offers to install it for you on first use. It is not on the VS Code marketplace yet (#41). Until it is, run it from this repo: open vscode/ in VS Code and press F5. The CLI above is the supported way in. Updating entangle update checks for a newer release and swaps the binary in place. If you installed with Homebrew, run brew upgrade entangle instead. Replacing the file inside a keg works, but leaves brew still believing the old version is installed, and a later brew upgrade can then put an older build back over the top. entangle warns you before doing this. You will also be told when a release exists, so a stale copy is a choice rather than an accident: note: entangle 0.7.0 is available (you have 0.6.0). Update with: entangle update The cockpit shows the same thing in its header. The rules behind it: It never makes you wait. The check runs after your command has finished and only writes down what it found; the note appears the next time you run something. Your session list is never behind a network round trip. It asks at most once a day, and stays quiet for a day after a failure too, so an offline machine does not retry on every command. It never writes to stdout. The note goes to stderr, and only when a terminal is attached. entangle sessions --json stays machine-readable, and scripts and CI never see it. It says nothing when it fails. No network errors you did not ask for. It is off for builds from source (dev versions), which would otherwise be told forever that they are behind. This is the one thing entangle asks the network about on its own: an anonymous, unauthenticated GET api.github.com/repos/.../releases/latest. No account, no identifier, and nothing about your sessions. To turn off both the message and the request: export ENTANGLE_NO_UPDATE_CHECK=1 What moves, and what doesn't Moves: your Claude Code sessions, project memory, settings, prompt history, and the portable parts of ~/.claude.json, all re-pathed for the new machine. Codex and opencode sessions move one at a time with entangle share. Never moves: your login. Credentials are machine-locked and deliberately left out. Skipped: caches, telemetry, and other throwaway files that rebuild themselves. Different operating systems Import runs on the destination, so it detects the OS and translates everything, including Windows drive letters and backslashes. Linux and macOS paths look like /home/you or /Users/you; Windows uses C:\Users\you. You do not have to do anything special, it just works in any direction. Is it safe, and how does it work? Safe by default: It never overwrites an existing file. It merges and tells you what it skipped; --overwrite backs up each replaced file first. --dry-run shows exactly what will happen before anything is written. The file-based flow is fully offline. Sharing scrubs likely secrets (best effort, so glance at what you send) and never includes your login. How it works: A bundle is a .tgz with a manifest that records each project's true absolute path, the piece the folder name throws away, read from ~/.claude.json and the cwd stored inside each transcript. On import it re-encodes the folder names for the target OS, rewrites the in-file paths (matching Windows paths in their JSON-escaped form so none are missed), merges without overwriting, and verifies every session is resume-ready. The full design and reasoning is in DESIGN.md. All commands and flags entangle open the interactive cockpit (default when a terminal is attached) entangle tui open the interactive cockpit explicitly entangle export [--out FILE] [--config-dir DIR] entangle import [flags] entangle inspect entangle verify [--config-dir DIR] entangle sessions [--tool T] [--project P] [--config-dir DIR] [--json] entangle share [--tool T] [--project P] [--out FILE] [--with-context] [--no-redact] [--yes] entangle send [--tool T] [--project P] [--with-context] [--no-redact] [--rendezvous URL] [--relay HOST:PORT] [--yes] entangle receive [--config-dir DIR] [--map OLD=NEW]... [--rendezvous URL] [--relay HOST:PORT] [--yes] entangle update [--check] [--yes] entangle gui [bundle] [--port N] import flags: Flag What it does --dry-run Show the plan and write n [truncated for AI cost control]