Glossary
Workspace sync
Definition
Workspace sync keeps one developer workspace (source, config, environment variables, Git state, and uncommitted work) consistent across every machine and agent host. It goes beyond file sync by understanding code: dependency folders regenerate locally instead of copying, lockfiles stay intact, and divergent edits are recorded rather than silently overwritten.
Workspace sync is a category distinct from file sync. A file-sync tool moves bytes and treats the newest write as truth. Workspace sync moves a developer environment: it knows that node_modules should regenerate locally rather than travel, that a lockfile must stay internally consistent, and that a project's env and Git working state are part of the thing being synced, not incidental files next to it.
The goal is that opening a project on a second machine or an agent host feels identical to leaving it on the first (same source, same env, same branch, same uncommitted edits) without a clone, a copied .env, or a re-auth step. Because it understands code, it can skip the things that should regenerate and carry the things that must not be lost.
Why it matters
Consumer sync tools resolve conflicts with silent last-writer-wins, which is fine for photos and dangerous for code, where two machines can each hold work you do not want to lose. Understanding code is the line between a tool you can trust with a live project and one that quietly corrupts a lockfile or overwrites an afternoon of edits.
In practice
You edit a feature on your laptop over lunch, then open the same project on a build box. Workspace sync means the uncommitted edits, the .env, and the current branch are already there, not a stale clone from this morning that you have to reconcile by hand.
How Bowline relates
Workspace sync is the category Bowline builds. It keeps one real ~/Code in sync everywhere as ordinary local directories, carrying source, env, opaque Git state, and uncommitted work, while node_modules and caches stay local. If Bowline disappeared, the code is still just files on disk.
Your ~/Code, on every machine and every agent.
Install bowline and your projects follow you. It just works.
curl -fsSL https://install.bowline.sh | shmacOS app · Linux CLI. Then run bowline login.