The same code, live
on all your machines.

hilo keeps every repo in step across your Mac, your server and the cloud while your agents work. No push, no pull, no copying .env files around.

curl -fsSL https://raw.githubusercontent.com/damkandev/hilo/main/install.sh | sh

macOS and Linux · MIT ·
~50 ms per write on home Wi-Fi

Each agent works on its own copy.

What one changes, the other doesn't see until someone commits, pushes and pulls. Meanwhile they step on each other and work on stale code.

macbook · claude code~/code/api/src/retry.rs
    F: FnMut() -> BoxFuture<'static, Result<T>>,{    let mut delay = Duration::from_millis(250);not on devbox    for attempt in 1..=MAX_ATTEMPTS {        match op().await {            Ok(v) => return Ok(v),            Err(e) if attempt == MAX_ATTEMPTS => return Err(e),            Err(_) => sleep(delay).await,

line 13 · not on devbox

devbox · codex/srv/api/src/retry.rs
    F: FnMut() -> BoxFuture<'static, Result<T>>,{    let mut delay = Duration::from_millis(50);    for attempt in 1..=MAX_ATTEMPTS {        match op().await {            Ok(v) => return Ok(v),            Err(e) if attempt == MAX_ATTEMPTS => return Err(e),            Err(_) => backoff(&mut delay).await,not on macbook        }        delay *= 2;

line 18 · not on macbook

Every write, everywhere.

A file an agent writes appears on the other machine in about 50 ms, on a home Wi-Fi.

macbook~/code/api

devbox/srv/api

The first write on a version wins.

A write travels with the hash of the version its writer had. The anchor accepts the first and rejects the rest. hilo never merges two edits: the version that lost is kept on a branch.

macbook · claude codewrites retry.rs on a3f9
devbox · codexwrites retry.rs on a3f9
anchor
first: acceptedchange #4812
second: rejectedkept on hilo/conflict/main/20261113-142207-481920000

Branches move on every machine.

Commits, worktrees and new repos travel with the files. .env variables travel encrypted, key by key.

A branch graph and, below it, the same graph mirrored

After the install, this is the whole setup.

$ hilo

  1. installs hilo on the other machine and starts it as the anchor
  2. pairs both machines; the join code travels over SSH
  3. links the folder on both sides and waits until every repo is in sync
  4. installs a background service, the Claude Code hooks and the MCP server
A server in the middle, with laptops and cloud sandboxes connected around it

Cloud agents can join too.

Each sandbox joins as a short-lived machine, with a token. The branch it works on shows up on your Mac while the agent works, before any push.

Encrypted between machines. Nothing runs without you.

Machines pair with a single-use code inside a Noise handshake. Keys stay in the macOS Keychain. Changes to paths that run code wait for hilo approve, which shows the diff.

No external audit yet ·
Not in v1: Windows, NAT traversal

A smiling padlock

Common questions.

How is hilo different from git push and pull?
With git, a change reaches another machine only after someone commits, pushes and pulls. hilo sends every file write as it happens: it appears on the other machine in about 50 ms on home Wi-Fi. It doesn't replace git. Commits, branches and worktrees travel with the files.
What happens when two agents edit the same file at the same time?
The first write on a version wins. Each write travels with the hash of the version its writer had; the anchor accepts the first and rejects the rest. hilo never merges two edits: the version that lost is kept on a hilo/conflict/… branch.
Which coding agents does it work with?
hilo syncs the files themselves, so it covers whatever writes to the folder: Claude Code on your Mac, Codex on a server, an agent in a cloud sandbox. Setup also installs the Claude Code hooks and an MCP server.
Does hilo sync .env files?
Yes. .env variables travel encrypted, key by key, so you never copy them between machines by hand.
Is it secure?
Traffic between machines is encrypted. Machines pair with a single-use code inside a Noise handshake, and keys stay in the macOS Keychain. Changes to paths that run code wait for hilo approve, which shows the diff. There has been no external audit yet.
Which platforms does it run on, and what does it cost?
hilo runs on macOS and Linux. Windows and NAT traversal are not in v1. It is free and open source under the MIT license.

Get started with one command.

curl -fsSL https://raw.githubusercontent.com/damkandev/hilo/main/install.sh | sh

macOS and Linux · MIT ·
~50 ms per write on home Wi-Fi