Bare Agent
- Claude, Codex, or another CLI
- always-on tmux terminal
- no reading, Library, work record, or Routines
How much coordination do I want?
Start bare. Add only what helps.
Ronin can be an always-on terminal around your existing Agent, or it can add progressively more structured coordination. Beta Ronin Services remain a separate axis.
Four coordination choices
Start bare, then add the layers that help.
Cowork floor
- launch and session identity
- Campaign and Team resolution
- vocabulary, shelf map, and birth receipt
Ronin Base
- show files and keep documents
- fork Agents and send messages
- team wipeboard and work records
Managed file coordination
- separate worktrees and desk status
- hand-in and lead integration
- receipts and Git safeguards
Bare metal remains a complete choice. Choosing Ronin Cowork adds its floor; Base and managed file coordination add further capabilities only when selected.
A separate beta axis
Ronin Services are in beta today.
Ronin Cowork works fully without them. It is early days for Services: capabilities are still becoming ready, and readable transcripts are in development rather than live today.
Ronin Services
- live work records
- readable transcripts in development
- Stats and Voice
- gbrain integrations
Sharing your email is optional. It registers your interest, keeps you part of the Ronin community as it grows, and lets ready capabilities reach you as they land.
Four different facts
Selected is not the same as available.
- EnabledDid Campaign or Team configuration select the Routine?
- InstalledAre its local or service parts present on this machine?
- ConnectedWas an MCP or other live connection delivered?
- ApplicableDoes the present repository or situation use this behaviour?
An enabled but unavailable Routine does not block Agent birth. The Agent opens; the unavailable behaviour is reported as not delivered.