Independent Agent
Keep the session independent. A session on no Team is a normal, complete way to work.
Do my Agents have to work as a team?
Independent by default. Coordinated when useful.
Agents can work side by side without talking to one another. When a job benefits from coordination, you choose the Routines and shared surfaces that support it.
The optional coordination shape
Start together, then choose how closely to work.
Start Coworking
Name the work and begin with an Agent.
Name the work and begin with an Agent.
Optional Team coordination
A lead can shape the work and launch help as needed; the owner still chooses the breadth of execution.
- Shape the work and bring in Agents only when useful.
- Coordinate through focused direct messages and the shared team wipeboard.The wipeboard is short-lived communication, not the durable record.
- For reviewed repositories, Ronin Worktrees can give Agents separate worktrees.This requires that selectable Routine and a repository that enables Worktrees.
- Agents hand coherent work in; the lead reviews the combined candidate at the lead gate.
- Accepted state returns to the work, where the next independent or coordinated pass can begin.
Continue the work
The result may feed either path next.
The result may feed either path next.
This is a coordination shape you may use, not a workflow Ronin forces. Messages, wipeboards, worktrees, and hand-in support the choice; they do not control an Agent's behaviour.
What Ronin adds
Start bare, then add only the coordination you want.
A bare Agent is simply its provider CLI in an always-on tmux terminal. A Cowork Agent receives the minimal Cowork floor, then the Routines selected by its Campaign and Team. Changing a switch never rewrites an Agent already running.
- Cowork floorLaunch, identity, Campaign and Team resolution, the vocabulary and shelf map, and a birth receipt.
- Ronin BaseSimple structured coordination: show a file, fork an Agent, send a message, post to the wipeboard, and keep documents or work records.
- Managed file coordinationSeparate worktrees, desk status, hand-in, lead integration, receipts, and Git safeguards for parallel file work.
Specialized Routines such as Machine, gbrain, Koshi, or Ronin Koe remain separate optional packages.