About Bowline
One real ~/Code, everywhere you work
Bowline gives every machine and every coding agent the same ~/Code tree. Your source, config, env, and secrets follow the project. No commits to move work around, no keys to copy, no setup ritual. You open a folder and the code is there. It just works.
The setup layer, removed
Developers and their agents now work across laptops, remote servers, and short-lived agent hosts. Keeping the same code folder usable on all of them used to be a running list of chores.
Cloning repos again on a new box. Copying .env files around. Re-authenticating the same tools. Fixing a worktree that drifted. Trying to remember which machine had the latest work. Bowline takes that layer away.
Open a project on any machine or agent you trust and the code is there. Source, opaque Git state, env, indexes, and agent leases travel with the workspace. No commits to shuttle work between machines, no keys to copy, no hydrate step to run first.
What we hold to
A few rules keep the product honest as it grows.
~/Code stays the center
The folder you already work in is the product. Status and sync run underneath it, not in a dashboard you have to visit.
Your tools keep working
Shell, editor, Git, package managers, and agents behave exactly as before. Git stays your tool for history and review. Bowline does not wrap it.
Trust once, then quiet
You approve a machine or agent one time. After that it has the code it needs and gets out of your way.
See problems early
A stale base, missing env, or degraded sync shows up before it wastes your time or an agent's run, without asking you to manage any of it.
Who builds Bowline
Bowline is an independent project, built by one engineer who got tired of setting up the same code folder on every new machine and agent host.
It is small and opinionated on purpose. The goal is narrow: make one real ~/Code appear and stay useful everywhere you work, then stay out of the way.
The CLI and daemon are open source under the Apache 2.0 license. You can read the code, file issues, and check how the security-sensitive parts work, including device trust, Recovery Keys, and workspace encryption, on GitHub.
Try it
macOS app and Linux CLI. Install, run bowline login --root ~/Code, and open a folder.
curl -fsSL https://install.bowline.sh | shThen run bowline login --root ~/Code to connect your first machine.