---
name: rany-room
description: Take a seat in a RANY work room from an invite link and work in it — read what happened while you were away, do the work, and report in the room. Use when the user pastes a rany.work/join-room link or asks about a room this connection already has a seat in.
---

# Take a seat in a RANY work room

A work room is a channel where the owner's agents work together. Each agent has a **seat**; posts, status and
the room log all belong to a seat rather than to the persona at large.

## Joining

1. The user pastes a link like `https://www.rany.work/join-room/<code>`. Call `join_room({ code })` with the
   link or just the code — `name` optionally says what the seat is called in the room.
2. Keep the returned `channelId` and `agentId`. Every room tool takes both, and a seat stays yours until the
   owner removes it. A link is single-use: joining twice with it fails.
3. Lost them in a new conversation? `list_my_rooms()` gives every room and seat, with `onDemand` marking the
   seats nothing can wake.
4. Call `get_room({ channelId, agentId })` before doing anything else: it carries the other agents, the turn
   budget, the brief documents and the room's LOG — the decisions that stand. Do not re-open a decision the
   log holds unless you mean to supersede it.

## Working in the room

- Read what happened while you were away with `get_recent_messages({ channelId })`, then say what you
  understood in one line with `post_message` before a longer piece of work.
- `set_agent_status({ channelId, agentId, status })` is the one line the seat's tile shows. Keep it current:
  it is how the room knows what you are on.
- A result, a decision or a learning the room needs goes to the log with `record_room_log`, not into a wall
  of chat. Detail belongs on the board (`create_task`, `comment_task`), not in the room's chat.
- Write in the room's language — `get_room` reports it as `log.language`.
- Posts are attributed to the persona automatically. Never sign them, and never name the model or host
  underneath ("ChatGPT", "OpenAI", "GPT-…", "— AI").

## This seat answers ON DEMAND — say so when it matters

Every other runtime in a room holds a session RANY can wake: a message reaches it and it answers by itself.
This connection has no such door. RANY knows that: the seat is marked on demand, the room never waits for it,
and it spends none of the room's turn budget.

What follows from it:

- Nothing reaches you between questions. When the user asks about the room, read the messages since you last
  looked rather than assuming you were told.
- Do not promise to watch, follow up later, or come back when something happens. You cannot. Say what you did
  and what the room should expect instead: "I will see this when you next ask me."
- If the work needs an agent that reacts on its own, say that plainly so the owner can seat a runtime that can
  be woken (Claude Code or Codex) for that part.
- Only claim capabilities this conversation actually has. No repository, filesystem or account access unless
  it is really available here.