Boot puts your entire code folder on any laptop or cloud agent in seconds. It remembers which git repos live where and recreates that layout on any other machine. Every repo appears instantly as a tiny placeholder and turns into a real clone the moment you open it. Boot also syncs your env vars (encrypted) and runs a small background daemon so no machine ever builds on a stale main.

Does boot replace Git or live-sync my edits?

No. Boot only syncs which repos live where, plus your encrypted env vars - never the files you're editing. Your code stays in ordinary git repos with their own remotes.

How do I set up a new machine with boot?

Use one private git repo to hold your workspace layout (a name like code-map works well) - you only do this once. If it does not exist yet and you have the GitHub CLI installed, boot can offer to create it during setup; otherwise create an empty private repo first. Then run 'boot setup git@github.com:me/code-map.git ~/code' on each machine. It connects the workspace, creates a secret key, installs the shell hook and background daemon, and prints a health check. Your whole layout shows up as placeholders that clone themselves when you touch them.

Are my env vars safe in the synced map?

Yes. Env vars are encrypted with AES-256-GCM before they leave your machine, so the map is safe to host anywhere. The secret key stays local and never enters the map - you move it to a new machine with a short passphrase via 'boot env key share / receive'.

Which platforms does boot support?

macOS, Linux, and Windows, as standalone binaries. No Node required - Git is the only thing boot needs installed. Install with a one-line command and update anytime with 'boot update'.

Your workspace, on every machine.

Boot puts your entire code folder on any laptop or cloud agent in seconds. Every repo appears instantly and turns into a real clone the moment you open it.

View on GitHub Setup →

$ curl -fsSL https://useboot.co/install.sh | bash

Quick Start

Use one private git repo to hold your workspace layout (a name like code-map works well). If it does not exist yet and you have the GitHub CLI installed, boot can create it during setup; otherwise create an empty private repo once. After that, one command sets up each machine.

# link the workspace, create a secret key,

# install the shell hook + background daemon

$ boot setup [email protected]:me/code-map.git ~/code

# your first sync seeds the map with everything in ~/code

How it works

┌──────────────┐            ┌──────────────┐            ┌──────────────┐
│   MacBook    │            │   the map    │            │   Desktop    │
│   ~/code     │◀──────────▶│  (tiny git   │◀──────────▶│   ~/code     │
│   47 repos   │  daemon    │    repo)     │  daemon    │ placeholders │
└──────────────┘  syncs     └──────┬───────┘  syncs     └──────────────┘
                                   │
                                   │  boot agent
                                   ▼
                            ┌──────────────┐
                            │ cloud agent  │
                            │  ready in    │
                            │   seconds    │
                            └──────────────┘

1.Boot scans your code folder and saves its layout, which repos live where, to a tiny private git repo called the map

2.A background daemon syncs that layout every minute, add a repo on one machine and it shows up on the others on its own

3.Other machines recreate your folder structure with tiny placeholders,the whole shape of your workspace, no gigabytes

4.Open a placeholder and it becomes a real clone on the spot, and the daemon keeps every clean repo up to date with its remote

Syncs the layout, not the files

Boot remembers which repos live where and recreates that layout on any machine. Your code stays in git, boot never copies your edits.

Repos appear before you clone them

Every repo shows up as a tiny placeholder folder. Open one, with cd, a write, or even a read, and it becomes a real clone on the spot.

Never build on a stale main

A background daemon quietly keeps clean repos up to date with their remote. Anything with local work is reported and left alone.

Encrypted env vars

Your secrets travel with the layout, encrypted with AES-256-GCM. The key stays on your machines, you move it with a short passphrase, never the raw key.

Jump to any repo

Type bcd web and land in the right repo, even one you have never cloned on this machine. It clones itself on the way.

One command for CI & agents

boot agent gives a fresh container your whole workspace: it clones only the repos you ask for and writes your .env files.

Touch it and it appears

Placeholders keep a fresh machine small. You choose when they turn into real clones, and every option follows the same rules: never overwrite a real repo, and if a clone fails, the placeholder stays put.

# the shell hook (installed by boot setup) clones repos as you navigate

$ eval "$(boot shell-hook zsh)" # ~/.zshrc, also bash | fish | powershell

$ cd ~/code/apps/kplane

# kplane clones in the background before your command runs

Handy commands

You don't have to remember to sync, the daemon does it for you. Most days you never run push or pull.

boot setup <remote> [path]Set up a machine in one shot, safe to re-run anytime.

boot pushPublish this machine's layout by hand (the daemon already does this for you).

boot pullPull the latest layout by hand; add --dry-run to preview.

boot cd <name>Jump to any repo by name, it clones itself if needed (use the bcd shell shortcut).

boot hydrate <path>Turn a placeholder into a real clone.

boot env key share / receiveMove your encrypted secrets to a new machine with a passphrase.

boot agent <remote> [path]Set up a CI job or cloud agent in one shot.

boot updateUpdate boot itself to the latest version.

boot doctor --systemCheck that a machine is set up correctly.

Env-var sync, the Dropbox-folder transport, FUSE mounts, and the full command reference live in docs/detailed.md.

Frequently asked questions

What boot syncs, what it never touches, and how secrets stay safe.

Set up your next machine in seconds

One command per machine. Free and open source.

View on GitHub Setup →