A seat can look back through your history the way you would: search your past discussions, open one, and pass something on to another discussion that needs to know. It works the same on the Mac, the web and the iPhone.
Searching and reading
search_discussions finds your discussions by words, an error message, a file name or a key such as GEN-437. Each result gives the title, the key, the project, when it was last active, a short excerpt around the match and its id. A seat asks for 8 by default and 20 at most, and can keep to the ones you started or the ones your team shared.
open_discussion reads one of them by id or key: the title, key and date first, then your questions and the final answers, then the other replies, cut to about 8,000 characters unless the seat asks for more (at most 20,000).
Neither asks you first, in any approval mode: they only read, as reading a file does, and the warden does not stop to judge them.
What a seat may reach
Only what you could open yourself:
- your own discussions, and the ones your team shared with you or that a teammate shared with you by name;
- never a teammate's private discussion, and never another account's;
- never a temporary discussion, nor one kept on your Mac as private;
- never the discussion the seat is working in.
On the Mac the search covers that Mac's discussions first, then, while you are signed in, the rest of your account. Whatever comes back reaches the seat marked as outside material: the record of another discussion, to read and judge, never instructions.
Sending a message to another discussion
With app_action message, a seat sends text to another discussion you may write in. It lands there as a card, "From GEN-12 · its title", with a link back, and never as your own words: it does not name the discussion, count as your question or mark it unread as if you had written. If that discussion is idle, its room starts on the message, on your account and that discussion's own settings. If it is running, the message joins the run at its next step, as one you type mid-run does. The seat is told which happened, or why it could not: not found, no permission, private, read-only, out of credit, or a team policy.
The receiving seats read it as information from another room. Where it differs from what you said in that discussion, your words win.
The limits
- Asking. A message reaches outside the discussion, so on the Mac it is asked about as other outward actions are: Manual and Accept edits show a card naming the target, Auto lets it through, Smart judges it, Bypass does not ask. A web or iPhone run asks no cards for its tools, this one included. The warden judges it everywhere.
- Three a run. One run sends at most three messages.
- Chains stop. A message started by another message carries its place in the chain, and a relayed message can start at most two more. After that the seat is told to tell you instead.
- The record. Each one is a discussion.relayed audit event: from, to, by whom.