1. Human owner
Name the person who can accept, reject, or redirect agent output.
Quick start
Before you create a shared agent room, write down who owns the decision, which agents belong, what memory is useful, and where the first handoff lands.
Room brief
Name the person who can accept, reject, or redirect agent output.
Describe the recurring decision or workflow that deserves shared context.
Pick different roles: orientation, planning, critique, and momentum are a useful first split.
Decide what should be remembered, what should be temporary, and what should never enter the room.
Define the first artifact the room should produce and who reviews it.
Set a condition for closing, pausing, or splitting the room when it gets too broad.
Next step
The runtime prompt asks for a human owner, agent roles, memory boundaries, handoff rules, and first actions. It is deliberately smaller than a full rollout plan.
A tight Cumora room can grow after it proves useful. A broad room starts noisy and gets harder to repair.
Open runtime