Code in sync, everywhere.
Keep your laptop, cloud boxes, and Codex or Claude agents on the same live working tree.
treesync cloud
delta stream live
Remote box
encrypted mirror
Second device
Laptop
Why treesync
The part of your workflow git was never meant to carry.
Git is for history. treesync is for live working state: the half-finished, high-context, not-ready-to-commit work that still needs to follow you.
Live workspace
laptop
edited web/app/page.tsx
cloud mirror
encrypted delta accepted
remote box
pulled current tree
codex host
patch returned safely
Mirrors the real working tree
Every repo, every .git directory, every branch, stash, hook, local file, and agent scratchpad moves together.
Only changed content moves
After the first mirror, small edits and branch switches sync as deltas instead of re-sending the world.
Encrypted before upload
Keys stay on your devices. The service coordinates encrypted blobs; it does not need to read your code.
No silent clobbering
If two machines touch the same file, both versions are preserved as sidecar copies for you to resolve.
Built for agent fleets
Codex, Claude, and remote hosts can work from the same live context and return changes to your laptop.
Setup
One command, then your workspace starts following you.
No migration project. No new source of truth. Run it from the folder you already work in.
cd ~/code && curl -fsSL https://treesync.dev/install.sh | sh && treesync initmacOS
Linux
agents
Point at ~/code
01Choose the folder that contains your repos. treesync treats it as one living workspace, not a pile of unrelated files.
Keys and mirror start
02Init signs in, provisions device keys, uploads the encrypted first snapshot, and starts the background daemon.
Every host catches up
03Remote machines and agent hosts pull the same working tree. Conflicting edits are preserved instead of overwritten.
Workflows
Use it where commits are the wrong handoff.
treesync is for the moments before work is clean: experiments, branch switches, generated patches, model context, and local state.
laptop
edit
cloud
encrypt
remote
pull
agent
patch
Laptop to remote box
Move from local coding to a beefy remote machine without turning every context switch into a checkpoint commit.
- Pick up exactly where you left off
- Every repo's full history travels with you
- Private encrypted mirror of your working state
Human to human
Keep each developer's private mirror consistent without a shared drive full of source or fragile rsync scripts.
- Per-member encrypted mirrors
- Conflict-safe by design, no clobbered work
- Onboard a new machine in seconds
Human to agent
Run Codex or Claude on any host against your live workspace and bring their edits back into your local flow.
- Agents start from your exact, current code
- Hand work between humans and agents
- Multi-machine fleets stay in lockstep
Trust
Built for source code, not random folder sync.
The important answers are simple: treesync does not replace git, does not read your code, and does not silently overwrite conflicts.
What happens after I join early access?
You get on the invite list for the first hosted treesync.dev rollout. We'll use the email only for early-access updates and invitations.
How is this different from Dropbox or iCloud?
treesync is built for source code, not generic files. It mirrors each repo's .git directory byte-for-byte, dedupes content across repos, and is end-to-end encrypted by default.
Does it interfere with git?
No. treesync doesn't wrap, rewrite, or proxy git. It mirrors the actual files on disk — including .git — so you keep using git exactly as you do today. There's no fragile git integration to break.
Can treesync read my code?
No. Your code is encrypted on your device before upload, and the keys stay with your devices. End-to-end encryption is on by default.
What happens on a conflict?
If the same file changes on two machines, treesync keeps both versions as sidecar copies rather than overwriting either one. You decide what to keep — you never silently lose work.
Which platforms are supported?
macOS and Linux today, with more on the way. A single mirror can span any mix of supported machines — your laptop, a remote build box, and the hosts your agents run on.
Is it good for AI agents?
Yes — it's a core use case. Agents can run on any machine and start from your exact, up-to-the-second workspace, and their changes sync back conflict-safe alongside yours.
Early access
Put your laptop, cloud box, and agents on the same working tree.
We are inviting developers already moving code between local machines, remotes, and AI-agent hosts.