USE CASE · ONE CONTEXT, MANY MACHINES

The work is continuous.Your machines aren't.

Laptop, desktop, a server. Claude Code, Codex, Gemini CLI. One project mounted on all of them, so whichever agent you talk to starts from the same files.

Start free →Read the full guide

No credit card. Offline is a normal state.

💻MacBook~/workClaude Code
🖥️Desktop~/Documents/workCodex
🗄️Server/srv/ctxa cron agent
p-79d0a07cone project · three paths · same files

The folder doesn't have to match. State is keyed by a stable project id, so moving or renaming a folder later is free.

A DAY

Pick it up where you left it, on whatever's in front of you.

  1. 9:04
    MacBookClaude Code writes the spec
  2. 13:20
    DesktopCodex picks it up mid-sentence
  3. 14:00
    MacBookon a train — edits queue locallyno network · edits queue locally
  4. 18:10
    MacBookback online, converges in seconds
  5. 19:40
    Serverthe nightly agent starts from all of it

Changes queue while a machine is unreachable and reconcile when it comes back. Working offline for a day is the same mechanism, just with a longer window.

MORE THAN ONE AGENT PER MACHINE

Four agents, one folder, legible history.

The hooks are written per platform, into each agent's own user config, so several agents can be wired into the same folder at once.A write made through an agent is stamped with that session.

📄spec.mdClaude Code on MacBook · 9:04amv1
📄spec.mdCodex on Desktop · 1:20pmv2
📄spec.mdcron agent on Server · 7:40pmv3

bdrive log and the hub's history stay readable even when four agents share a project.

WHEN TWO MACHINES EDIT THE SAME FILE

They converge. Without a lock service.

How each device writes only its own log

  • Append-only per device. No object ever has two writers, so there is nothing to lock.
  • Deterministic replay. Every device folds every log in the same order, so they land on the same answer.
  • Later write wins per path — and the loser is kept beside it as a conflict copy.

Result nothing is lost

📄spec.mdDesktop · 1:20:09pmkept
📄spec (conflict from macbook).mdMacBook · 1:20:02pmpreserved

You decide what to merge. Nothing was dropped to get here.

SET IT UP

The second machine connects. It doesn't create.

1

On the first machine, set it up normally.

You · MacBook — Claude9:00am

Set up BearDrive for this folder.

ClaudeSyncing work as project p-79d0a07c.

2

On every other machine, name that project.

You · Desktop — Claude9:06am

Set up BearDrive here, connecting to project p-79d0a07c.

ClaudeConnected. Pulling now — the folder can live anywhere you like.

The hub shows the project id on the project's home page. The hooks are registered once per machine, not per project — the pull hook is what makes each agent start its turn current.

One context. However many machines you own.

Start free →see the other use cases
Skills and hooks in detail →What to run on each new machine, and why the pull hook is the one that matters.How sync works →Journals, blobs, and deterministic replay — why this converges rather than hoping to.