Comments and teammates

Comments sit on the lines they are about, reviewers are listed on the review itself, and a model can walk you through a change one step at a time.

Leaving a comment

You leave comments on reviews that were sent to you, the ones under For Your Review. On your own reviews you read the comments and reply to them.

To comment on code, open the review's Code section.

• Press on a line and drag over the lines you mean. A single click picks one line.
• A box opens under the last line you picked, with Confirm and Cancel. Clicking away saves what you wrote, and Escape throws it away.
• Dragging over exactly the lines of an existing comment reopens it for editing. Any other range starts a new comment.
• Clicking inside lines that already carry a comment opens or closes that comment's card, so a comment never gets a second one inside it.

A comment card shows the author, the lines it is on and the text as Markdown. A comment on a removed line says so. Your own comments have a pencil to edit them and a trash icon to delete them. A card folds back to a pin on its line once it scrolls away, and clicking the pin opens it again.

A button in the section bar hides and shows the comments while you read the code.

To comment on the review's description, click the description in the Description section and a box opens under it.

The Comments section

The Comments section lists every comment on the review. Each one shows the file it is on and the lines it was left on, drawn the way the diff draws them. A comment on the description sits under PR description, and a comment on the review as a whole has no file.

• On a review sent to you, a box at the top takes a comment on the whole review.
• On your own review, each comment has a reply button and a tick. The tick is for your own tracking. The person who left the comment sees it once you tick it.

With nothing there the section reads No comments yet.

Reviewers

The Reviewers section lists who is on the review. Each row shows a badge, a name and a verdict, 0/1 while waiting and 1/1 once approved. On your own review each row also has an x to take that reviewer off. The top of the section shows how many approvals the review has out of how many it needs. With no one on it the section reads no reviewers yet.

On your own review there are two ways to add a reviewer.

• Add reviewer lists model reviewers for each provider you have a linked account on. For Claude those are Opus 4.8 at medium and at high effort, and for Codex it is GPT 5.6 Sol at high effort.
• The email box beside it adds a person by their email address. You need to be signed in to a Warshall account. Without one the section reads sign in to a Warshall account to add people.

The model walkthrough

Every review has a Walkthrough Your Code button in its section bar. The fallback model reads the review's full diff, its title and description and the project's WorkMap, and writes a short tour of the change as numbered steps, each tied to lines in a file.

Hover the button first to see what it will cost. The card names the fallback model and shows an ESTIMATED range of tokens and share of the five hour usage window. Once a walkthrough has run it also shows what it USED, and a STATUS line says whether one is ready and how many steps it has.

Pressing the button runs the model. While it works the button reads Generating… with a count of the seconds. When it is done the review switches to its Code section and the walk starts.

• The lines for the current step are highlighted and scrolled to the middle.
• A callout beside them shows the step number out of the total, the step's title and its explanation.
• Previous and Next move between steps, and so do the left and right arrow keys. On the last step Next becomes Finish.
• View in Editor closes the review window and continues the walk in the editor, and remembers where to bring you back.

Escape, the close button on the callout, or leaving the review or its Code section ends the walk.

A walkthrough is kept with the review and its newest commit, so opening it again later costs nothing. When new commits land on the review, the next walkthrough is made fresh.

The button is not available on a review that has no commits yet.