boxd connect staging and lands on the same machine. Unsharing only changes who can reach it, never who’s billed.
One command, and the whole org can reach the machine.
Sharing controls organization access, and the web URL is a separate thing. The machine’s
https://<machine>.boxd.sh URL is already public to the internet. Sharing decides which org members can get a shell on the machine.The agent login handoff
A machine you’ve been working on holds your own agent logins on disk. Claude Code, Codex, and OpenCode keep their tokens in your home directory, and the moment a machine becomes reachable by the rest of your org, those tokens should not be sitting there for anyone with a shell to read. boxd enforces this for you. Sharing a machine wipes the agent logins on it the moment it goes shared:git and gh on the machine also switch from your personal Git sign-in to the organization’s GitHub App, so repo access on a shared machine belongs to the org rather than to you.
The guarantee is that no member’s personal login is ever left readable on a machine the rest of the org can reach.
Unsharing brings your logins back
Runboxd machine unshare and the machine is private to you again. Your agent logins come back too:
- Claude Code and Codex. They re-authenticate automatically. boxd serves your Claude Code and Codex logins for that org the next time you start a session on the machine.
- OpenCode. It needs an
opencodelogin on the machine, since OpenCode has one login per machine. After that it persists, because a private machine is never wiped.
Fork a shared machine for private work
Forking a shared machine gives you a private fork by default. The org keeps paying, the copy is yours alone, and your agent logins work in it right away:--shared when you want the fork to stay open to the org. Forking a private machine works the same way, and the fork stays private.
At a glance
See the CLI reference for every flag, and Authentication for how billing and org context work.