Use case
Share one workspace namespace with a small team
Give a small team one workspace namespace with per-device trust, audit logs, and revocable access. Everyone's ~/Code and env stay consistent, with no setup docs.
Who this is for
Search intent: shared dev environment for a small team.
You lead a small, agent-forward team. Onboarding a new engineer is a day of README archaeology, secret hand-offs over chat, and "works on my machine" drift. You want a shared, consistent workspace with some control: who has access, what they can reach, and the ability to revoke a lost laptop.
Before and after
The status quo, and what changes once bowline is keeping this workspace in sync.
Today
- Onboarding is a stale setup doc, a secrets hand-off over chat, and half a day before anyone can run the app.
- Everyone's environment drifts, so "works on my machine" is a daily conversation.
- There's no record of which person or device holds which secrets, and no clean way to revoke a departed laptop.
- Agent hosts multiply the problem: each one needs the same manual setup, per engineer.
With bowline
- A shared workspace namespace means a new hire's ~/Code, config, and env are consistent from the first login.
- Per-device trust is explicit and revocable: cut off a lost or departed laptop in one step.
- Audit logs record which devices joined and what they hold, so access isn't a mystery.
- The same policy covers laptops and agent hosts, so onboarding a machine and an agent look the same.
The setup
Install once, approve the device, and open the folder. No manifests and no keys to copy between machines.
curl -fsSL https://install.bowline.sh | shEach teammate installs, then bowline login.
bowline connectA teammate's device joins the shared namespace after approval.
cd ~/Code/acme/web && pnpm devConsistent source and env on day one, with no setup doc.
What makes it work
The bowline capabilities that carry this workflow.
Shared workspace policy keeps every teammate's ~/Code and env consistent.
Audit logs record device joins and workspace access for visibility.
Revocable per-device trust and device governance to cut off a lost or departed machine.
SSO and dedicated support on the Team tier.
Common questions
Short answers to the questions this setup raises first.
What does the Team tier add over Pro?
Team adds shared workspace policy, audit logs, SSO, and per-device governance on top of everything in Pro. It is aimed at small teams that want a shared namespace with control and visibility, priced custom.
Can I revoke a teammate's access when they leave?
Yes. Device trust is explicit and revocable. Cut off a departed engineer's laptop or agent host and it can no longer decrypt or sync the shared workspace.
How much of the onboarding setup does this actually remove?
The parts that usually eat the first day: cloning every repo, copying .env files, and re-authenticating tools. A new device joins the shared namespace and the source and env are already there. There is no setup doc to follow.
Is this aimed at large enterprises?
No. Today it is built for small, agent-forward teams. Teams under strict compliance regimes that cannot route encrypted workspace state through a third-party relay are out of scope for now.
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.