Select the three-dot button at the right of the channel header, then Review in the Switch surface menu.
(Result: The Review surface opens, headed with the pull request, its checks and its comments. A pull request card in the conversation opens the same place, already on the right one.) 1.Read the list. Each row is a pull request, with the repository it belongs to beside it.
(Result: The list covers every repository in view, not one, so a change that spans two of them is one reading rather than two tabs.) 1.Read the job bars on the row. They are the CI jobs for that pull request, one bar per job, showing what has run and what it did.
(Result: Each bar shows whether its job has run and how it ended. A row whose bars are still running is a row to come back to.) 1.Read the reviewer states on the row.
(Result: The row names each reviewer and where they stand, so it says whether the change still needs you before you have opened it.) 1.Open the pull request you came for.
(Result: The change, its checks and its comment thread open together.) 1.If you need the code in front of you, use the launch workspace action on the pull request.
(Result: A machine comes up on that branch — a Workspace channel, in the product's terms — so you can run the change rather than read it. That is the gesture for a diff you cannot judge by reading.) 1.Approve it, or say what is missing in a comment.
(Result: Your approval is the last gate on the change. Lens holds the merge until a human approves it, unless an admin has turned on “Agents may merge without a human” in this channel's “Access” rows.) - **If this doesn't work:**If Review is not in the Switch surface menu, this channel’s kind does not open it — a dashboard channel has no pull requests to show. If a job bar reports a failure, read it in the conversation: the agent that ran it posts a test-run card with Open in Test, and that card is the shortest route to what failed. If the list is empty, the surface says so — “No open pull requests in your connected repos.” — and offers Sync pull requests; select it. The surface lists what its own data holds rather than what this channel’s agents opened, so a channel whose header carries a pull request badge can still list nothing — the note after the procedure records that. If the approval is not offered to you, A control in a guide is not visible says who to ask.
You have read the change against its checks and its reviewers, and either approved it or said what it needs. **Planned.** The Review surface still runs on its own data rather than the channel's, so the pull requests it lists may not be the ones this channel's agents opened. - [Review agent suggestions in docs](https://crusible.dev/docs/guides/review-agent-suggestions-in-docs/) — Open the suggestions waiting on a doc, read each one beside the text it changes, and accept or reject it block by block.- [Surfaces answer to the conversation](https://crusible.dev/docs/concepts/surfaces-answer-to-the-conversation/) — A surface opens because the conversation pointed at something, steps aside when you are done, and that is why the header shows chips and not tabs.- [Your first melt](https://crusible.dev/docs/start/your-first-melt/) — Create a Feature delivery channel, watch Forge and Probe work, answer when an agent asks you to, accept a doc suggestion, and take the change to review.