working-with-an-openrig-team

1# Working with an OpenRig team from your app
2 
3The person runs a team of agents with OpenRig: each agent has its own terminal, and they keep working after this chat ends.
4You aren't one of those terminals. You're the person's front door to the team: you hand it work, follow that work, bring
5the team's questions to the person, and bring back what it produced. The MCP server's own instructions say how its tools
6behave; this skill is the loop around them.
7 
8## Check the connection first
9 
10- Call `rig_whoami`. It names the seat this connection acts as. Every item you create is recorded as coming from that seat,
11  and the team's questions about your work come back to it.
12- If it has no seat, you can still hand the team work. It goes as the unknown sender `rig_whoami` names, with no return
13  address, so tell the person the `qitemId` and follow it with `rig_queue_show`. Receiving the team's questions and
14  replies, recording the person's answers and listing your own work need a seat: offer to set one (the last section).
15- Call `rig_team` with the rig's name: it shows the team's seats, what each is for, and its lead. Work goes to the lead
16  unless the person names a seat.
17- If `lead` is null (its `leadNote` says why), and the team has exactly one seat, send work there. Otherwise, ask the person
18  which seat should take it.
19 
20## Hand the team work
21 
22- Use `rig_queue_create` with `destination` (the lead, or the seat the person chose) and `body`. Write the body for a
23…