Boot - Your workspace, on every machine We're sorry but Boot doesn't work properly without Javascript<br>enabled. Please enable it to continue.<br>Your workspace, on every machine.<br>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.<br>View on GitHub Setup →
macOS / LinuxWindows<br>$ curl -fsSL https://useboot.co/install.sh | bash
Quick Start<br>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.<br>First machineNext machineCloud agent / CI<br># link the workspace, create a secret key,<br># install the shell hook + background daemon<br>$ boot setup [email protected]:me/code-map.git ~/code<br># your first sync seeds the map with everything in ~/code
How it works
┌──────────────┐ ┌──────────────┐ ┌──────────────┐<br>│ MacBook │ │ the map │ │ Desktop │<br>│ ~/code │◀──────────▶│ (tiny git │◀──────────▶│ ~/code │<br>│ 47 repos │ daemon │ repo) │ daemon │ placeholders │<br>└──────────────┘ syncs └──────┬───────┘ syncs └──────────────┘<br>│ boot agent<br>┌──────────────┐<br>│ cloud agent │<br>│ ready in │<br>│ seconds │<br>└──────────────┘
1.Boot scans your code folder and saves its layout, which repos live where, to a tiny private git repo called the map<br>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<br>3.Other machines recreate your folder structure with tiny placeholders,the whole shape of your workspace, no gigabytes<br>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
01Syncs the layout, not the files<br>Boot remembers which repos live where and recreates that layout on any machine. Your code stays in git, boot never copies your edits.
02Repos appear before you clone them<br>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.
03Never build on a stale main<br>A background daemon quietly keeps clean repos up to date with their remote. Anything with local work is reported and left alone.
04Encrypted env vars<br>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.
05Jump to any repo<br>Type bcd web and land in the right repo, even one you have never cloned on this machine. It clones itself on the way.
06One command for CI & agents<br>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<br>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.<br>On cdFuzzy jumpOn first writeOn read (FUSE)<br># the shell hook (installed by boot setup) clones repos as you navigate<br>$ eval "$(boot shell-hook zsh)" # ~/.zshrc, also bash | fish | powershell<br>$ cd ~/code/apps/kplane<br># kplane clones in the background before your command runs
Handy commands<br>You don't have to remember to sync, the daemon does it for you. Most days you never run push or pull.<br>boot setup [path]Set up a machine in one shot, safe to re-run anytime.<br>boot pushPublish this machine's layout by hand (the daemon already does this for you).<br>boot pullPull the latest layout by hand; add --dry-run to preview.<br>boot cd Jump to any repo by name, it clones itself if needed (use the bcd shell shortcut).<br>boot hydrate Turn a placeholder into a real clone.<br>boot env key share / receiveMove your encrypted secrets to a new machine with a passphrase.<br>boot agent [path]Set up a CI job or cloud agent in one shot.<br>boot updateUpdate boot itself to the latest version.<br>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<br>What boot syncs, what it never touches, and how secrets stay safe.<br>Does boot replace Git or live-sync my edits?<br>Where does my workspace layout live?<br>Will the daemon ever touch my work in progress?<br>How do my env vars stay safe?<br>What do I need before the first machine?<br>Which platforms are supported?
Set up your next machine in seconds<br>One command per machine. Free and open source.<br>View on GitHub Setup →