Getting started
Coordinate two coding-agent conversations around one shared change after installing CoordRooms.
Use this guide after completing Installation. It shows a common way to coordinate two agent conversations around one shared change and inspect the resulting record.
Before you begin
Installation provides each supported client with the CoordRooms skill and local MCP operations. Tell an agent to use CoordRooms when work needs coordination. Once a room has a name, you can refer to it naturally in later prompts.
Start two conversations in the same room
For a change with adjacent responsibilities, open two supported coding-agent conversations. Before either begins substantive work, tell each one to use CoordRooms and work in the same named room.
For example, if one agent will change a database operation and another will update its dashboard view, tell both to use a room named dashboard-filtering before assigning the work.
In the database-operation agent's coding-agent session:
Use CoordRooms and join the dashboard-filtering room before work begins. Own the filtering operation and its database constraints.In the dashboard agent's separate coding-agent session:
Use CoordRooms and join the dashboard-filtering room before work begins. Own the dashboard controls for the filtering behavior.You do not need to provide a conversation ID or direct the underlying room operations.
Assign the adjacent work
Give each agent its responsibility after it has joined the room. One can establish the filtering behavior and database constraints; the other can implement the dashboard controls around that behavior.
The installed skill uses the local MCP operations to reconstruct relevant room history before substantive work. As the agents work, it records material coordination updates such as decisions, questions, warnings, and handoffs.
Let the work stay coordinated
When one agent makes a material decision or needs an answer that affects the other responsibility, it records that update in the room. Supported lifecycle hooks deliver new room updates into the other active agent's context, so it can continue with the current shared record.
For example, the database-operation agent might follow up with:
In dashboard-filtering, I decided that archived rooms are excluded by default. Make the dashboard control reflect that behavior, and flag any conflict with the current view.If a decision needs explicit direction from you, state it in either conversation and refer to the room by name.
Verify delivery and inspect the record
Continue both conversations and confirm that the shared work stays aligned. Then start the dashboard:
coordrooms dashboard --openSelect the room to inspect its decisions, questions, warnings, handoffs, and membership events.