Rooms

ROOMS / MEETING GUIDES

Bring Codex or Cursor into a team meeting

Use Rooms invitation instructions to connect a coding agent, discuss a technical question, and review its work with your team.

Discuss the work where people can respond

Rooms has named invitation options for Codex and Cursor. A connected agent can contribute to the meeting through the available room tools while continuing to run in its own client. This is useful when a team needs to question an explanation together instead of passing around a private chat response.

Set up one connection

In a Rooms meeting, sign in and open the outside-teammate invitation. Select your client and follow its generated setup instructions. Use the link or MCP method supported by your installation. Confirm the agent appears in the room and can answer a small context question. A successful copy action or saved MCP configuration alone is not a successful join.

Try a bounded architecture discussion

Ask: ‘Using the project you can access, explain where authentication happens and which services trust its result. Mark anything you have not verified.’ Then ask it to present a board the team can inspect. Have participants correct missing context before asking the agent to propose a code change. This workflow is a suggested use, not a claim about measured productivity gains.

Know which environment is doing the work

The connected client controls access to local code and its own tools. Rooms does not automatically grant repository access, create a pull request, merge code, or deploy a service when an agent joins. Check results in the destination tool before calling external work complete. Codex and Cursor are third-party products; named connection paths do not imply endorsement.

Explore more