Glossary
These are the words Revue uses, as Help › How Revue Works defines them in the app. Each entry says what the word means, what it doesn’t mean where the two are easy to mix up, and where to find it. A key is given where the thing has one, and a link where Settings changes it.
Revue keeps some everyday words narrow on purpose. A snapshot is a pull request as it stood after one push, and on a local branch the same thing is called a checkpoint. Pending is only for a GitHub review you haven’t submitted, and a local comment says Not sent instead. Addressed is only an agent saying it dealt with your local comment. Read, Viewed and Looked are three different marks. Words with two meanings at the end sorts out the rest.
For how these fit together, start with How Revue works. The concept pages go further on snapshots and ranges, stacks and layers, checkpoints and agent sessions and AI review.
Opening things
Section titled “Opening things”Each tab reads one thing: a pull request, a branch, your working copy or a comparison.
Not: a file. Files are in the tab’s sidebar.
Where: The tab strip at the top of each pane.
Key: ⌘T
Pull request tab and local tab
Section titled “Pull request tab and local tab”A branch and its pull request open in separate tabs. The branch tab shows what is on your Mac. The pull request tab shows what GitHub has, and is where you review.
Not: one tab with both. Revue never switches your branch.
Where: The explain line under the context bar on a branch tab.
The Inbox lists review requests, your pull requests and the ones you follow.
Not: GitHub notifications. Read state is kept on this Mac.
Where: Its own tab. A new tab opens on it.
Inbox views
Section titled “Inbox views”Needs you, Your PRs, Stacks, Snoozed and Done each list one part of the Inbox, with Worktrees and Drafts after them while they have something in them. Worktrees lists the checkouts on this Mac.
Not: a list of local stacks. Stacks lists open pull requests in stacks.
Where: The Inbox’s sidebar, and Go › Inbox.
Mark read and Snooze
Section titled “Mark read and Snooze”Mark read and Snooze are kept on this Mac. They change nothing on GitHub. All and Unread choose what the list shows.
Not: muting GitHub notifications.
Where: The Inbox’s header and each row’s menu, and Go › Inbox › Mark Read.
Key: E
Updated and live updates
Section titled “Updated and live updates”The Inbox’s header says when it last heard from GitHub. Without live updates it asks about once a minute while it is open.
Not: Live changes, the diff mode for the files on your Mac.
Where: The Inbox’s header. Live updates are turned on in Settings › Live updates.
Settings › Live updates
Command palette
Section titled “Command palette”The command palette finds a pull request, a branch, a file or a command. Type > first to list only commands.
Not: only a list of commands.
Where: Anywhere in the window. Go › Command Palette.
Key: ⌘K
The revue command
Section titled “The revue command”In a checkout, type revue to open it here. revue –pr owner/repo#123 opens a pull request from anywhere.
Not: installed with the app. Revue › Install Command Line Tool puts it on your path.
Where: Terminal.
Copy a link to a thread, and anyone with Revue opens straight to it. A link names a pull request and can point at a thread, a comment, a review or a line.
Not: a link for someone without Revue. Copy GitHub Link to Thread gives one.
Where: Edit › Copy Revue Link to Thread, beside Copy Pull Request Link.
New tabs, windows and folders
Section titled “New tabs, windows and folders”A new tab opens on the Inbox. Open Repository picks a folder on this Mac, and Open Recent lists the last ones you opened.
Where: The File menu, and the chooser in an empty pane.
Key: ⌘O
Split panes
Section titled “Split panes”Split a tab to read two things side by side. Both sides share your comments and viewed marks. Revue reopens your windows and tabs when it starts again.
Not: two separate drafts. Panes on one source share one.
Where: The Pane menu, and Window › Show Next Tab.
Key: ⌘\
Following the checkout
Section titled “Following the checkout”A branch tab follows your checkout. When you switch branch, it asks before it moves. Choosing a snapshot pins the tab where it is.
Not: always the files on disk.
Where: The context bar, and Go › Go to Checked-Out Layer.
Detached HEAD and rebases
Section titled “Detached HEAD and rebases”When HEAD is detached or a rebase is under way, the line under the context bar says so, and says what the tab shows instead.
Where: The explain line under the context bar.
Stacks and layers
Section titled “Stacks and layers”A stack is a chain of branches, each built on the one below. Revue reads it from gh-stack.
Not: something Revue creates, rebases or pushes. It only reads gh-stack’s state.
Where: The sidebar, above the files.
Needs gh-stack.
A layer is one branch in the stack. Its diff is compared with the layer below it, not with main.
Not: a diff against main. Only the bottom layer’s is.
Where: The rows of the stack card, L1, L2 and up.
The branch a stack is built on, usually main. A merged layer says In main.
Where: Settings › Sync and stacks, Default trunk branch.
Settings › Sync and stacks
Layer states
Section titled “Layer states”Each layer says where it stands: Open, Draft, Merged, Closed, Needs rebase, GitHub only or Local only. The line under the context bar says what that means for this tab.
Not: a promise to act. Revue reports Needs rebase and does nothing about it.
Where: The stack card’s rows, and the explain line.
Check out a layer
Section titled “Check out a layer”Check out a layer to see its uncommitted work. Revue makes a worktree in a folder beside your checkout and leaves your current checkout alone.
Not: switching branch in your folder.
Where: The explain line’s Check out. Settings › External editor sets up new worktrees.
Settings › External editor
Next layer and previous layer
Section titled “Next layer and previous layer”Move down and up the stack in the same tab.
Where: Go › Next Layer and Go › Previous Layer.
Key: ⇧↓
A branch with no stack
Section titled “A branch with no stack”A branch with no stack is read as a single layer.
Not: a sign that stacks are needed. They aren’t.
Where: A branch tab.
Snapshots, range and live
Section titled “Snapshots, range and live”Snapshot
Section titled “Snapshot”A snapshot is the pull request as it stood after one push. Snapshot 2 shows the full pull request as of its second push.
Not: only what changed since snapshot 1.
Where: The scope in the context bar, and the snapshot menu.
Key: ]
Range compares two snapshots and shows only what changed between them. Use it to catch up on a pull request you already read.
Not: the commits between two pushes. Comments can’t be added in a range.
Where: The scope menu, or Shift-click two snapshot tiles.
Key: ⌥2
Live shows the files on your Mac right now, before you commit. It exists only for a branch that is checked out here.
Not: the Inbox’s live updates.
Where: The scope menu on a local tab.
Key: ⌥3
Ignoring rebases and Including rebases
Section titled “Ignoring rebases and Including rebases”When the base moved between two snapshots, Ignoring rebases shows only how this work changed and leaves out the commits that came in from the base.
Not: hiding real changes. Only the base’s commits are left out.
Where: The scope menu, under Range.
Changes since last look
Section titled “Changes since last look”Opens the changes since the snapshot you last looked at, as one range to the latest. When a push lands on a pull request you read, the context bar offers the same range.
Not: Since my last look, which compares the files on your Mac.
Where: The context bar, and Go › Changes Since Last Look.
Key: R
Mark as looked
Section titled “Mark as looked”Revue remembers the last snapshot you read. Mark as looked sets it by hand.
Not: marking files viewed. Viewed is a mark of its own.
Where: Go › Mark as Looked.
Key: ⇧⌘L
A new snapshot arriving
Section titled “A new snapshot arriving”When someone pushes, the new snapshot arrives and what you are reading stays put. It is the full pull request again, not only the new changes.
Not: a replacement for what is on screen.
Where: A badge on the snapshot control, or a notice. Settings › Sync and stacks chooses which.
Settings › Sync and stacks
Checkpoints
Section titled “Checkpoints”On a local branch, snapshots are called checkpoints. One is recorded when you commit, rebase, or when an agent finishes a turn.
Not: a commit you can restore. Rebase only means the code didn’t change.
Where: The sidebar’s Checkpoints list on a layer with a working copy.
Snapshot tiles
Section titled “Snapshot tiles”Each tile is one snapshot. A hatched tile is a rebase that changed no code. Shift-click a second tile to compare the two.
Where: The snapshot menu and the stack card.
Reading a diff
Section titled “Reading a diff”Viewed
Section titled “Viewed”Mark a file viewed once you have read it. The mark stays until that file’s diff changes.
Not: GitHub’s Viewed checkbox. Viewed files, the last snapshot you read and Inbox read are three marks.
Where: The file’s header, and Review › Mark File Viewed.
Key: V. Settings › Diff and review
Files and comments
Section titled “Files and comments”The sidebar lists the files that changed, with their additions and deletions. The comments list on the right holds everything said about them.
Where: The sidebar, and Review › Show Comments.
Key: ⌘B
Next file and previous file
Section titled “Next file and previous file”Move through the diff a file at a time. Single keys like these act only when no text field has focus.
Not: keys that work while you type.
Where: Go › Next File and Go › Previous File. Edit › Find searches the diff.
Key: J
Unified or split
Section titled “Unified or split”Read a diff in one column or two. In split view each comment card sits under its own side. Wrap lines, line numbers and word highlights are in the View menu too.
Where: View › Split Diff.
Key: U. Settings › Diff and review
Generated files
Section titled “Generated files”Generated files and lockfiles are collapsed, with the reason. Show diff opens one.
Not: a file skipped by mistake.
Where: The file’s header, and View › Show All Generated Files.
More context
Section titled “More context”Show more lines around a change, or the whole file up to 4 MiB.
Where: Above and below each change.
Open in editor
Section titled “Open in editor”Opens the file in your editor at the line you are on.
Not: for a pull request with no checkout on this Mac.
Where: The file’s header. Settings › External editor chooses the app.
Key: O. Settings › External editor
Selection bar
Section titled “Selection bar”Select lines to comment on them, ask about them or open them.
Where: Over the lines you select.
Reviewing on GitHub
Section titled “Reviewing on GitHub”Pending comment
Section titled “Pending comment”A comment you write waits in your pending review. Only you can see it until you submit.
Not: posted when saved.
Where: The card under the line, and the review panel.
Key: C
Review panel
Section titled “Review panel”The review panel shows reviews, checks and your pending comments, and is where you submit.
Not: every comment. That is the comments list.
Where: The column on the diff’s right, on a pull request tab.
Key: ⌥⌘R
Submit review
Section titled “Submit review”Choose Comment, Approve or Request changes, then submit. Until then nothing is posted. A choice that is not open to you here is greyed, with the reason.
Not: the Commit key in the diff. Submit works in the review panel.
Where: The review panel, and Review › Submit Review.
Key: ⌘↩
Counter
Section titled “Counter”The counter shows how many comments still need attention. Click it to see them in the comments list.
Not: a count of every comment. It counts the open ones.
Where: The context bar, and Review › Show Comments.
Key: ⌥⌘K
Next comment and previous comment
Section titled “Next comment and previous comment”Move to the next and previous comment, across files.
Where: Go › Next Comment and Go › Previous Comment. Go › Next Pending Comment skips to your own.
Key: ⌥↓
Threads
Section titled “Threads”Reply to a thread, resolve it or open it on GitHub, as you would there.
Not: a resolve on this Mac. Resolving a GitHub thread resolves it on GitHub at once.
Where: The thread’s card.
Outdated
Section titled “Outdated”GitHub marks a thread outdated when its lines have changed since it was written.
Not: resolved, or wrong.
Where: The thread’s card.
Suggest change
Section titled “Suggest change”Select lines on the right side to suggest a change. A comment can carry an image too.
Where: The comment box, and Review › Suggest Change.
Posting
Section titled “Posting”If a post is cut off, its card says May have posted, with Reload threads to check before you send it again.
Where: The comment’s card.
Check spelling
Section titled “Check spelling”Comments, the commit message and the pull request title are checked as you type. Code in Markdown is left alone.
Where: Settings › Writing, Check spelling.
Settings › Writing
Local work with a coding agent
Section titled “Local work with a coding agent”Local comment
Section titled “Local comment”Comments on a local branch stay on this Mac. They never go to GitHub. They are marked Not sent, never Pending.
Not: comments that post when you push.
Where: A branch, layer or working copy tab.
Key: C
Send to Claude or Codex
Section titled “Send to Claude or Codex”Send your open comments to the coding agent working in this checkout.
Not: automatic. It needs a Claude Code or Codex session in this checkout.
Where: The context bar on a local tab.
Key: ⌥⌘↩. Needs a coding agent in this checkout.
Addressed
Section titled “Addressed”Addressed is the agent saying it dealt with your comment. Check, then resolve it or reopen it.
Not: done.
Where: The status on a local comment’s card.
Key: ⇧E
Agent connected
Section titled “Agent connected”The chip in the context bar says whether a Claude Code or Codex session in this checkout is listening for your comments, and whether it is working.
Not: Revue’s own AI review.
Where: The context bar on a local tab. The Review menu lists the session.
Claude Code plugin
Section titled “Claude Code plugin”The plugin lets a Claude Code session read your comments, reply and mark them addressed. Codex reads a section you add to the checkout’s AGENTS.md instead.
Not: needed for AI review. Only Send needs it.
Where: Revue › Install Claude Code Plugin.
Settings › AI review
Edits from Claude
Section titled “Edits from Claude”With Review Claude’s Edits on, an edit Claude proposes opens here as a diff. Accept all of it, some of it, or reject it.
Not: closing the tab. Reject stops Claude’s turn.
Where: Its own tab. Review › Review Claude’s Edits turns it on.
Terminal
Section titled “Terminal”A terminal opens in the bottom pane, in this layer’s checkout. Claude Code started there connects to Revue by itself.
Where: View › Show Bottom Pane and View › Terminal › New Terminal Tab. Settings › Terminal.
Key: ⌃`. Settings › Terminal
AI and agent sources
Section titled “AI and agent sources”AI review
Section titled “AI review”AI review runs Claude Code or Codex on your Mac to look for problems in a snapshot. It uses your own sign-in to that tool.
Not: a Revue account. Your code goes only to your own AI provider.
Where: The context bar, and Review › Run AI Review.
Settings › AI review
Findings
Section titled “Findings”A finding is a problem the AI thinks it found. Apply writes its fix to your working file. Suggest on GitHub adds it to your pending review.
Not: a commit. Apply changes files and commits nothing.
Where: Cards in the diff, and Go › Next Finding.
Key: F
Ask AI
Section titled “Ask AI”Select lines and ask about them. Each selection keeps a conversation of its own.
Not: a chat that remembers the rest of the app.
Where: The selection bar, and Review › Ask AI.
Key: ⌘I
Agent sources
Section titled “Agent sources”An agent source is a review agent running on a server. Revue shows its results on the pull requests it has reviewed.
Not: AI review, which runs on this Mac.
Where: Settings › Agent sources.
Settings › Agent sources. Needs an agent source.
Confirmed and Apply fix
Section titled “Confirmed and Apply fix”Confirmed means the agent reproduced the problem. Apply fix puts its patch in your working tree. Nothing is staged or committed.
Not: hidden by mistake. Unconfirmed findings are behind a filter.
Where: An agent source’s cards in the diff and the comments list.
Triage
Section titled “Triage”An agent’s opinion of a reviewer’s comment on your pull request: Valid, Already addressed, Incorrect, Question or Unclear.
Not: the Addressed status of a local comment.
Where: Under the first comment of a thread.
Run line
Section titled “Run line”Each agent source has one line saying what its last run did: what it read, what it ran, and how many of its findings a review thread already raised.
Where: The top of the comments list, one line for each source.
Local work reporting
Section titled “Local work reporting”When you turn it on for a source, Revue tells it which of your unmerged branches are in progress, with the name of this Mac: branch names, commit subjects and sizes. Code is sent only when a review of one is requested.
Not: on by default. Nothing is reported until you choose, one repository owner at a time.
Where: Settings › Agent sources, and Review › Review This Slice.
Settings › Agent sources. Needs an agent source.
Writing back
Section titled “Writing back”Commit
Section titled “Commit”Choose files, hunks or lines, write a message and commit. Only what you select is committed.
Not: a commit of everything.
Where: The context bar on a local tab, and Review › Commit.
Key: ⌘↩
New pull request
Section titled “New pull request”Draft the title and description, check the preflight, then push and create. Each is its own click. Preflight reads the base from GitHub, so your local copy of it never needs updating.
Not: a push by itself.
Where: Review › Create Pull Request.
Git hooks
Section titled “Git hooks”revue hooks installs two optional git hooks in a checkout you name: one keeps track of a change across an amend or a rebase, and one adds a Change-Id to commit messages.
Where: The revue command, in Terminal.
The window, keys and settings
Section titled “The window, keys and settings”Single keys
Section titled “Single keys”With the diff focused, single keys act at once. Every key can be changed.
Not: keys that act while you type.
Where: Help › Keyboard Shortcuts lists them. Settings › Keyboard shortcuts changes them.
Key: ⌘/. Settings › Keyboard shortcuts
Show or hide Revue
Section titled “Show or hide Revue”One shortcut that brings Revue forward from any app, or hides it. Choose one to turn it on.
Where: Settings › Keyboard shortcuts.
Settings › Keyboard shortcuts
Notices and notifications
Section titled “Notices and notifications”Notices appear in the window. Notifications come from macOS, only while Revue is in the background and only about a tab that is open. They are off until you turn them on.
Where: Window › Focus Notices. Settings › Notifications.
Key: ⌃⌘N. Settings › Notifications
Settings
Section titled “Settings”Changes in Settings apply when you save, and Revert puts them back.
Where: Revue › Settings.
Key: ⌘,
Themes
Section titled “Themes”The interface theme and the code theme are chosen apart. Themes from VS Code and TextMate can be imported.
Where: View › Appearance › Interface Theme, Code Theme and Import Theme.
Settings › Appearance
Fonts and text size
Section titled “Fonts and text size”Choose the code font from the fonts on this Mac, and the size of the interface’s text.
Where: Settings › Code and Settings › Appearance.
Settings › Code
Zoom and layout
Section titled “Zoom and layout”Zoom from 80 to 140 percent. Density, the sidebar’s side and Reduce motion are in Settings.
Where: View › Zoom In and View › Zoom Out. Settings › Appearance.
Key: ⌘=. Settings › Appearance
Updates
Section titled “Updates”Once you allow it, Revue asks updates.ryc.sh about every hour whether there is a new version, and shows the release notes of any it finds. Check for Updates asks at once.
Where: Revue › Check for Updates. Settings › Updates.
Settings › Updates
Live updates
Section titled “Live updates”Live updates use your browser’s GitHub session to hear about changes as they happen. They are off until you turn them on.
Not: a sign-in. Revue reads the session cookie from Chrome, Brave or Firefox.
Where: Settings › Live updates, and the Live updates row in Settings › Accounts.
Settings › Live updates
Git identity and signing
Section titled “Git identity and signing”The name and email Revue commits with, and whether it signs commits, for each checkout.
Where: Settings › Accounts.
Settings › Accounts
Revue uses jj when the checkout has it, or the backend you choose.
Where: Settings › Sync and stacks, Backend.
Settings › Sync and stacks
Export, import and reset
Section titled “Export, import and reset”Export settings to a file and import them on another Mac. Export leaves out your GitHub sign-in and git identity. Imported settings apply when you save.
Where: Settings › Advanced, beside Reset all settings, Show hints and Reset tour progress.
Settings › Advanced
Context menus
Section titled “Context menus”Right-click a file, selected lines, a layer, a comment or a finding for its commands, with the menu bar’s names and keys.
Where: Anywhere you can right-click, or Edit › Show Context Menu from the keyboard.
Key: ⌃↩
Backport comparison
Section titled “Backport comparison”In the repositories listed in Settings, a pull request labelled as a backport is checked against the pull request it came from. Backport Comparison shows where the two differ.
Not: a new diff. Line numbers, comments and viewed marks stay the snapshot’s.
Where: The line under the context bar, and View › Backport Comparison. Settings › Diff and review.
Key: ⌥4. Settings › Diff and review
Words with two meanings
Section titled “Words with two meanings”Live changes are the diff mode for the files on your Mac. Live updates are how the Inbox hears from GitHub.
Where: The scope menu, and the Inbox’s header.
Both start from your last look. Since my last look reads the files on your Mac, and Changes since last look reads the snapshots pushed after the one you last looked at.
Where: The scope menu, and the context bar.
Read, Viewed and Looked
Section titled “Read, Viewed and Looked”Three marks. Read is for the Inbox, Viewed for a file, and Mark as looked for the last snapshot you read.
Where: The Inbox, the file’s header and the Go menu.
Addressed
Section titled “Addressed”Used alone only for a local comment an agent dealt with. Already addressed is an agent’s triage of a GitHub comment.
Where: Local comment cards, and triage under a thread.
Always writes to your working files and commits nothing, whether the fix is from AI review, Ask AI, an agent source or Claude.
Where: Finding cards and Claude’s edits.
Dismiss
Section titled “Dismiss”Dismissing an AI review finding stays on this Mac. Dismissing an agent source’s finding tells the source.
Where: Finding cards.
Pending
Section titled “Pending”Used only for a GitHub pending comment or review. Local comments say Not sent.
Where: Chips on GitHub comment cards.
Resolve
Section titled “Resolve”Resolving a GitHub thread resolves it on GitHub. Resolving a local comment stays on this Mac.
Where: Thread and comment cards.
Comment
Section titled “Comment”A comment on lines, the Comment verdict, or the comments list. Each is named in full where two could apply.
Where: Cards, the review panel and the comments list.
A draft pull request, a pull request description being written, or a comment not yet saved.
Where: Chips, the New pull request sheet and the comment box.
A coding agent is Claude Code or Codex in a checkout. AI review is Revue’s own run on this Mac. An agent source is a review agent on a server.
Where: The context bar, Settings › AI review and Settings › Agent sources.
Snapshot and checkpoint
Section titled “Snapshot and checkpoint”The same thing. A checkpoint is a snapshot of local work.
Where: The snapshot menu, and the sidebar on a local tab.