Your working stack
- Claude, Codex, or another provider CLI
- provider accounts and subscriptions
- repositories and ordinary files
- terminals, tmux, Git, and worktrees
Your Agents, data, and code remain yours
A place to work with your Agents—not a new owner of your work.
Ronin works around the provider accounts, Agent CLIs, terminals, repositories, and documents you already use. It does not replace them with a proprietary runtime, project format, or Ronin-hosted data store.
The ownership boundary
Keep your stack. Add a coworkspace around it.
A lightweight coworkspace
- browser-accessed terminal workspaces
- session launch conveniences
- optional Team coordination
- optional managed file coordination
Local by design
Ronin does not become another destination for your code.
Your repositories, documents, terminal sessions, and Ronin state remain on the machine running your coworkspace. Ronin does not relay Agent traffic or upload your code and conversations to a Ronin cloud. The provider CLI communicates directly with its model provider, so that provider's data terms and zero-data-retention options remain the ones that govern model traffic.
Ronin Services has a separate, explicit choice to share anonymous operating measurements. Those measurements never include your code or conversations; declining sends nothing.
The practical test
What happens if I stop using Ronin?
Your provider accounts still work directly. Your repositories and documents remain ordinary files in their existing locations. Your Git history, terminals, and worktrees do not need to be exported or converted. Ronin-specific conveniences can go away without taking your work with them.