Every seat in a room is sent a brief: the standing instructions about how to lead, how to review, how to treat a fetched page or a tool's description, when to ask. The Model Prompt Editor shows what is yours and keeps the shipped brief out of the editor on purpose, so this page is where the shipped brief is accounted for. The version in force is 2026-11-05.3; the Mac stamps each turn's receipt with it and with a hash of the whole assembled prompt, so an audit can prove two runs saw the same instructions without exposing anyone's prompt.
Changes
The changes since October 2026, newest first. Earlier ones are on the next page, linked below.
| Version | Date | What changed |
|---|---|---|
| 2026-11-05.3 | 2026-11-05 | The lead's core brief (how to write, how to work, asking the person) keeps every rule in fewer words. |
| 2026-11-05.2 | 2026-11-05 | Guidance for screen checks, the full browser pane, documents, device toolchains, marking text and renaming files goes to a lead only when the request or project needs it. |
| 2026-11-05.1 | 2026-11-05 | A change is proved by the cheapest check that settles it, in the project's own environment; a from-source build or new install is named as not verified instead. check-it-works is for changes seen on a screen. |
| 2026-11-04.1 | 2026-11-04 | Claude Code leads keep the step-by-step progress-list line; it follows the CLI a seat runs, not its name. |
| 2026-11-03.1 | 2026-11-03 | CLI leads get the progress list tool's names and input and are asked for it twice, first step and last; leads without the bridge, and the closing turn, are not asked. API leads are unchanged. |
| 2026-10-29.2 | 2026-10-29 | Someone learning is taught: plain terms with examples, how parts relate, a short summary. An attachment-only message continues the question, a diagram's marks are read by what they do, and the answer never names the seat's working files. |
| 2026-10-29.1 | 2026-10-29 | A general question is answered as asked even when the advice is against it, naming the options that fit, with cost and when each makes sense. A request to recommend something names specific options, with prices checked by search or marked unchecked. The final answer opens with the answer; how the room got there follows briefly. |
| 2026-10-28.2 | 2026-10-28 | Page citations are sparing: at most once a paragraph or list item, where a reader would check. Under Clear report, a document summary gives what it is, its main point and key points. A one-round, no-tool answer from a room of one is not written again. |
| 2026-10-28.1 | 2026-10-28 | An objection gives the evidence it rests on. A suspicion with none yet is written "Objection (concern):"; it holds the work for one round, and raised again without evidence it is not counted either way. An objection is let go only on evidence, not a confident reply. Changes stay the size of the ask inside a file too, and a reviewer's "what if" is a note, not a requirement. |
| 2026-10-19.3 | 2026-10-19 | On the Mac, the lead is pointed at app_screenshot for photographing the workspace's own Electron app, including the screen before a change from a git ref. |
| 2026-10-19.2 | 2026-10-19 | After a visual change, your answer's writer shows Before and After screenshots, or says why it could not; the Answer style brief is shorter to make room. Off under "Show before and after screenshots for visual changes". |
| 2026-10-19.1 | 2026-10-19 | Your answer's writer, never a reviewer, gets the Answer style brief. |
| 2026-10-14.5 | 2026-10-14 | A reviewer with the phone or simulator tools reads the device evidence itself. |
| 2026-10-14.4 | 2026-10-14 | Evidence from a tool others lack is quoted and judged from the quote. |
| 2026-10-14.3 | 2026-10-14 | A question about how things stand is answered by checking, not by doing the thing again. |
| 2026-10-14.2 | 2026-10-14 | The lead does not restore a file deleted before its turn, from the workspace or by an earlier commit, unless the person asks. |
| 2026-10-14.1 | 2026-10-14 | A report is linked by its workspace path (artifacts/…), which opens on the Mac, the phone and the web, never by a path on the Mac's disk; reviewers do not object to such a link. |
| 2026-10-13.5 | 2026-10-13 | Reviewers find before they read, and are told a listing (git status, ls) shows files changed, not that the change is right. They are asked to open the changed code and run a test. |
| 2026-10-13.4 | 2026-10-13 | The lead finds before it reads, and a run carrying on cut-off work is given what that work already ran. |
| 2026-10-13.3 | 2026-10-13 | On a trivial ask, every reviewer's last line asks for the agreement token alone. |
| 2026-10-13.2 | 2026-10-13 | A reviewer does not object to a file that was already in the workspace before the run started: an untracked file the run did not make is the person's own. |
| 2026-10-13.1 | 2026-10-13 | A general question about the world is answered in full and ends with one short question when the best answer depends on something only the person knows; the apps show it above the reply box. On the web the opening answer is written for the person. A question through ltb chat is told it has no project. |
What the hash covers
The system text a seat received on a turn: the brief, the person's own rules for that role, the project's instruction files it was allowed to read, the memory block, and the notes the room added for that run. Not the conversation. Two turns with the same hash saw the same instructions.