intertwine — Don't lose your contexts

See it

intertwine resume

a live walk through intertwine resume — filter, sort, navigate. no audio.

Why

the directory shuffle

Relaunching into every directory to find a session is a pain.

Claude only shows sessions in your current folder. Agent managers solve this by taking over your whole workflow.

intertwine is a thin wrapper over Claude Code instead. Resume any session from anywhere, and keep every other dev tool exactly as it is.

context sharing today

Sharing knowledge is bloated markdown, junk commits, and slop.

Your most valuable context is the long-running session — the one that knows how to run and submit a job that isn't easy or obvious.

Share your best sessions as they are. Pick up a teammate's work when they're out sick, or fork it to learn how they did it.

Across machines

Your session follows you onto the box.

SSH'd into a cluster or a remote dev box? Resume the exact session you started on your laptop — same context, no copy-paste, no re-explaining the job. The conversation is pulled down and dropped into your checkout on that machine; if the repo lives at a different path there, you point it once with --dir and it's remembered. Pick it back up at home and it just continues.

laptop → ssh → laptop

one session, three machines, zero re-explaining.

How it works

⊙

Capture

Claude and Codex sessions, kept for the folders you opt in. intertwine asks once per folder, then it's automatic — and each one is labeled so you can find it later.

↗

Resume from anywhere

No more opening Claude in the wrong directory and seeing nothing. Pull up any past session from any working directory.

◇

Fork a teammate's

Continue a colleague's session from where they left off, same context, on your machine.

Getting started

1Solo dev

Keep every session, resume any of them from anywhere.

$npm i -g intertwine-cli && intertwine login

$intertwine setuponce · makes claude & codex capture-aware

$claudework as usual · the first time in a folder it asks once: keep these sessions?

$intertwine resume/ filter · s sort · ↑↓ move · Enter resume

2Start a team

Create a team, invite people, see and fork their work.

$intertwine login

$intertwine teams create my-teamyou're the admin · prints an invite link

$intertwine teamspicker: n new · c copy invite · j join

$intertwine resumeteammates' sessions show by default; Enter → Fork or Resume

3Join a team

Already signed in? Redeem an invite, or match automatically by GitHub org.

$intertwine login --invite <link>redeem at sign-in

$intertwine teams join <link>already signed in? redeem here (or j in the picker)

$intertwine teams refreshor auto-join if your GitHub org matches

$claude / codexopted-in folders sync to your team automatically

Resuming on another machine (cluster, dev box, second laptop)? Clone the repo first and run intertwine resume from inside it. intertwine syncs the conversation, not your code — it drops the session into the checkout that's already on that machine. If the repo lives at a different path there, point at it once with intertwine resume --dir <path> and it's remembered for next time.

Team

Works better together

→

Sign in with GitHub. No AWS, no buckets.

→

Sharing follows your GitHub org membership.

→

Fork a teammate's session and continue on your machine.

Supported tools

Claude Code Live

Codex Live

Gemini CLI Coming soon

Kiro Coming soon

Resume returns you to the tool that made the session — a Codex session reopens in Codex, a Claude one in Claude. Carrying a transcript across tools is on the roadmap.