From one answer to an ongoing project
A coding Agent can read a repository, change files and run commands. When a project continues over several days, you also need to know who owns an unfinished item, which decision was made, and where to resume. Rovai gives that work a lasting place.
For the Orbit download page, Dingding implements a scoped change and Cheese reviews it. Their identities stay in the roster. The conversation retains requests and replies; execution records and changed files let you inspect what actually happened.
What the workspace adds
- Lasting teammates
- Save a name, responsibilities and working principles once, then invite that teammate into different conversations.
- Shared conversation
- Keep requests, explicit recipients, reviews and handoff messages around one goal. Use a private one-on-one for a side question.
- Responsibility and execution
- A Task records an owner and responsibility; a Run records one execution. Read both when work spans several attempts.
- Reusable memory
- Store a durable agreement at the right scope, inspect its source and revise it later.
Start with the smallest useful team
One teammate is enough for a small, clear change. Add a reviewer when another perspective can reduce a specific risk: a platform link, an authorization change, or a release checklist. More participants do not automatically make a better result.
Rovai coordinates the Agent products installed on the host. Those products still need their own installation, sign-in and model access. The workspace does not imply that model computation runs locally.
Try one complete loop
- Configure one Agent and one teammate, then complete the Quick start.
- Open the collaboration tutorial to extend that task with a second teammate and an explicit review request.
- Keep the original conversation for follow-up work; save only durable agreements as memory.