Error codes

Git

GIT-000

Unclassified git failure

Revue couldn’t tell what went wrong. Choose Help › Copy Diagnostics and see Get help.

GIT-001

Git didn’t answer in time

Git took too long to answer, so Revue stopped waiting. A very large repository, a slow disk or network drive, or a Mac that’s busy can all cause it. Revue tries again on its next read, or choose Retry where the message offers it. If it keeps happening in one repository, check that git status runs quickly there in Terminal.

GIT-002

Revue couldn’t open the repository

Revue couldn’t read the folder as a git checkout. Make sure the folder still exists and is a git or jj checkout, then open it again with File › Open Repository. Show details has git’s own words.

GIT-003

Revue couldn’t load the diff

Git couldn’t read this comparison, often because a commit it needs isn’t in the checkout or was removed by a rebase. Choose Retry in the bar above the diff. If a pull request’s commits are gone from GitHub, open a snapshot that still exists. Show details has git’s own words.

GIT-004

Revue couldn’t list or read worktrees

Revue couldn’t ask git which worktrees the checkout has, so it can’t tell where a branch is checked out. Choose Retry. If it keeps happening, run git worktree prune in the checkout to clear worktrees whose folders are gone.

GIT-005

Nothing was committed

Git or jj refused the commit. Your message is kept. Show details has their own words: often a commit hook failed, or signing needs a key or a password. Fix what it says, then commit again. To check your signing settings, see Settings › Accounts › Git identity.

GIT-007

Revue couldn’t load branches

The list of branches didn’t load. Choose Try again. If it keeps happening, check the checkout in Terminal with git branch.

GIT-008

Revue couldn’t read the comparison’s revisions

One of the branches, commits or tags you picked to compare couldn’t be read. Check that it still exists in the checkout, then pick it again.

GIT-009

Some files couldn’t be replayed onto the new base

When you read a range that ignores rebases, Revue replays the older snapshot onto the new base. Some files didn’t replay cleanly, so their diff also shows changes that came from upstream. The banner says how many. Read those files with that in mind, or choose Including rebases in the snapshot menu to compare the snapshots as they are. See Re-review with snapshots.

GIT-010

A kept checkout couldn’t be moved or removed

Revue keeps whole checkouts of pull requests for Ask AI and AI review, and couldn’t move or delete one. It tries again later, and a new one is made when it’s needed. If disk space runs short, clear Kept checkouts in Settings › Storage. See Manage disk space.

GIT-011

jj couldn’t be read, so git’s IDs are shown

Revue reads change IDs from jj when the checkout uses it, and jj failed, so Revue showed git’s commit IDs instead. Nothing is lost. Run jj status in the checkout to see what jj says. If it reports divergent operations, fix them with jj, and Revue reads change IDs again on its next refresh.

GIT-012

Revue can’t watch the checkout

macOS didn’t let Revue watch the checkout’s files for changes, so Revue looks for changes on a timer instead. Changes still show up, a little later.

GIT-013

Revue couldn’t read the stack

Revue couldn’t work out the stack this branch is part of. Choose Retry. If it keeps happening, check that the branches in the stack still exist, and see Work with a stack.

GIT-014

A snapshot menu action failed

The snapshot menu couldn’t do what you asked, such as reading a snapshot or setting a range. Choose Retry in the menu. Show details has git’s own words.

GIT-017

The checkout, or its cancel, failed

Revue couldn’t check out the layer in its own worktree, or couldn’t stop a checkout that was running. Show details has git’s own words. Fix what it says and try again.

GIT-018

Revue couldn’t push

Git refused the push. Show details has its words. Most often the branch on GitHub has commits you don’t have, so pull first, or you don’t have permission to push to it.

GIT-019

Revue couldn’t show more lines

Revue couldn’t read the file to show the lines around a change, usually because the commit is no longer in the checkout. Refresh with Review › Refresh (⌘R) and try again.

GIT-020

Refresh failed

Revue couldn’t read the checkout or GitHub again. What you see is from the last read that worked, and Revue tries again on its own. Choose Refresh (⌘R) to try now. Show details has what went wrong.

Not errors in Git

Revue asked you something, or held back for a reason you can act on. Nothing failed.

GIT-006

The commit finished with warnings

The commit was made, and git printed warnings as it ran, usually from a commit hook. Show details has what it said. Nothing is lost, but read the warnings in case a hook changed something.

GIT-015

The checkout changed since you picked these

Files changed in the checkout after you picked what to commit, so Revue didn’t commit a selection that no longer matches. Choose Refresh, check your picks and commit again.

GIT-016

That folder isn’t a checkout of the pull request’s repository

The folder you picked is a clone of a different repository. Pick a clone of the pull request’s repository.

GitHub

GH-000

Unclassified GitHub failure

Revue couldn’t tell what went wrong. Choose Help › Copy Diagnostics and see Get help.

GH-001

GitHub’s rate limit was reached

GitHub limits how many requests an account can make in an hour, and Revue reached it. Wait, then try again. Where Revue knows when the limit resets, it says the time and tries again then. Other apps and scripts using the same account, including the GitHub CLI, count toward the same limit.

GH-002

Sign in to GitHub again

Revue has no GitHub account to use, or GitHub stopped accepting the one it had, for example because the token was revoked or expired. Choose Connect, or sign in again in Settings › Accounts. If Revue uses the GitHub CLI’s sign-in, run gh auth login in Terminal. See Sign in to GitHub.

A sign-in code from Setup or Settings works for a limited time, and only if you allow access on GitHub’s page. If it expired or was declined, choose Try again for a new code.

GH-003

The Inbox couldn’t refresh

Revue couldn’t ask GitHub for your Inbox. It shows the last results it had and tries again on its own. Choose Retry to try now. Show details has what GitHub or the connection said.

GH-004

GitHub returned partial results

GitHub answered without some details for one or more pull requests in your Inbox, so those rows may be missing a status or a count. Revue asks again on its next refresh, which usually fills them in.

GH-005

Some stacks couldn’t be read

Revue couldn’t read some stacks from GitHub, so their pull requests show on their own for now. Revue asks again on its next refresh.

GH-006

The GitHub CLI isn’t working

Revue uses the GitHub CLI’s sign-in, and gh is missing, isn’t signed in or didn’t answer. Install it, or run gh auth login in Terminal, then choose Retry. You can also sign in from Revue with a code in Settings › Accounts. See Sign in to GitHub.

In Setup, the GitHub row offers Copy command for gh auth login and Check again once you’ve run it.

GH-007

The Inbox is showing its last results

The Inbox couldn’t refresh, so it shows what it had last, and the banner says why. Choose Retry. Show details has what GitHub or the connection said.

GH-008

A pull request couldn’t be synced

Revue couldn’t read a pull request’s latest state from GitHub. It tries again at the next sync, and nothing is lost meanwhile. To try now, choose Review › Refresh (⌘R).

GH-009

Revue couldn’t look up a layer’s pull request

Revue couldn’t ask GitHub which pull request a stack layer’s branch has. The layer keeps the last answer Revue had, and Revue asks again later.

GH-010

Your reaction wasn’t saved

GitHub didn’t save the reaction, so Revue put the reactions back as they were. Try again. Show details has GitHub’s reason.

GH-011

Your review or comment wasn’t sent

GitHub didn’t take your review, comment or reply, or Revue couldn’t confirm that it did. Your draft is kept. If the card says May have posted, choose Reload threads first to check what GitHub saved, so nothing posts twice. Then send it again. Show details has GitHub’s reason. See Pending reviews and local comments.

GH-012

Revue couldn’t read GitHub’s branch

Revue couldn’t read the pull request’s branch on GitHub, so it can’t show what a push would replace. Revue reads the pull request again. Try once it has refreshed.

GH-013

GitHub denied the operation

GitHub refused, usually because your account doesn’t have permission for it in this repository, such as pushing, merging or adding to a stack, or because of a rate limit. Check your access to the repository on GitHub.

GH-014

GitHub couldn’t find it

GitHub has no such repository, pull request or comment, or your account can’t see it. Check the repository and your access, and refresh in case it was deleted or moved.

GH-015

GitHub reported a conflict

Something changed on GitHub since Revue last read it, such as a new push or another review. Refresh with Review › Refresh (⌘R), then try again.

GH-016

GitHub rejected the request

GitHub didn’t accept the values sent, often because the pull request changed since Revue read it. Refresh the pull request, check what you picked and try again. Show details has GitHub’s reason.

GH-017

GitHub doesn’t have the pull request yet

GitHub hasn’t finished making the pull request, or hasn’t published what Revue asked for. Wait a moment and refresh.

GH-018

The CI log couldn’t be read

Revue couldn’t read the job’s log from GitHub. It tries again at the next poll while the job runs. If it keeps failing, open the job on GitHub.

GH-019

GitHub hasn’t published this log yet

The job ended, but GitHub hasn’t made its log available. That can take a while for some jobs. Try again later, or open the job on GitHub.

GH-021

The stack is gone, or stacks are off

The pull request was created, but GitHub no longer has the stack it was meant to join, or stacked pull requests are turned off for this repository. Check the stack on GitHub, then add the pull request to a stack there if you want it in one.

GH-022

The stack is busy

Another change to the same stack was going on, so GitHub turned this one away. Try again in a moment.

GH-023

The pull request wasn’t added to its stack

The pull request was created, but GitHub didn’t add it to the stack. Show details has GitHub’s reason. Add it to the stack on GitHub, or check what changed with Check again.

GH-025

Revue couldn’t set up its connection to GitHub

Nothing was sent, because Revue couldn’t prepare a secure connection to GitHub. This can happen when macOS gives Revue no certificates to trust. Revue tries again after a pause. If it keeps happening, copy Diagnostics and see Get help.

Not errors in GitHub

Revue asked you something, or held back for a reason you can act on. Nothing failed.

GH-020

This log has expired

GitHub keeps CI logs for a limited time, and this job’s log is gone. Nothing failed. Run the job again on GitHub if you need its log.

GH-024

The stack changed since you checked

Between the check before creating and the create itself, the stack changed on GitHub, for example a pull request became the new top or joined another stack. Nothing failed. Look at the stack as it is now and try again.

AI

AI-000

Unclassified AI failure

Revue couldn’t tell what went wrong. Choose Help › Copy Diagnostics and see Get help.

AI-001

Revue couldn’t find Claude Code or Codex

Revue runs the AI provider chosen in Settings › AI review, and couldn’t find its command line tool.

1. Install Claude Code or Codex and sign in to it, if you haven’t.
2. If it’s installed somewhere that isn’t on your PATH, set its full path in Settings › AI review › Agent command, as Claude executable or Codex executable.
3. Check that Settings › AI review › Provider names the tool you use.

See Run an AI review for what AI review needs.

AI-002

An AI turn took too long

One call to Claude Code or Codex ran past the per-turn timeout, so Revue stopped it and counted it as failed. A large change can take longer than the limit.

Raise Settings › AI review › Per-turn timeout, which is 180 seconds by default, or review a smaller range, then try again. Lowering Concurrent review turns can help too, since fewer calls then run at once.

AI-003

Your AI account is out of credit

Claude Code or Codex said its account has no credit left, so the turn couldn’t run. Revue uses that tool’s own account and doesn’t pay for it.

Add credit with your provider, or choose the other provider in Settings › AI review, then try again.

AI-004

Ask AI didn’t answer

The question ended without an answer. Ask again. If it keeps happening, check that Claude Code or Codex works in Terminal, and see Show details for what the model said.

AI-005

Nothing was applied

Revue couldn’t make the change Ask AI suggested, usually because the file changed since the answer was written. Ask again so the answer reads the file as it is now. Show details has why.

AI-006

The AI review failed

The review stopped before it finished. Run it again from Review › Run AI Review. If it fails again, check that Claude Code or Codex works in Terminal and has credit, and see Run an AI review.

AI-007

Part of the AI review failed

One step of the review, such as looking for one kind of problem or merging duplicate findings, failed, and Revue went on without it. The findings you see are real, but the review may have missed some. Run it again for a full pass.

AI-008

Revue AI couldn’t answer

Revue’s AI couldn’t answer on a comment card. Try again. Show details has what the model said. If it keeps happening, check that Claude Code or Codex works in Terminal.

AI-009

The fix wasn’t applied

Revue couldn’t apply the fix to your checkout, often because the files changed since the fix was written. The card says why. Where it’s offered, a three-way apply merges the fix with your changes, but it may leave conflict markers to resolve. You can also make the change by hand.

AI-011

The checkout doesn’t match the fix

The fix was written for a commit your checkout isn’t at, or the pull request no longer has. The card says which. Fetch the commit where it’s offered, check out the layer, or choose another folder. If the pull request moved on, ask for a new fix.

AI-012

Revue couldn’t undo the suggestion

Revue couldn’t take back a suggestion it applied, often because the file changed since. Your files are as they were after the suggestion. Undo it by hand in your editor. Show details has why.

AI-013

Ask AI couldn’t get the snapshot’s files

Ask AI works on a copy of the snapshot, and Revue couldn’t fetch or copy its files. Check your connection and that your GitHub account can read the repository, then ask again.

AI-014

Interrupted AI reviews couldn’t be cleared up

When Revue opens, it marks AI reviews that were running when it last quit as failed. That step failed, so an old review may still say it’s running. Run the review again.

AI-015

Claude Code disconnected, or its file couldn’t be read

Claude Code disconnected before you answered its edit, or Revue couldn’t read the file it wants to change. Answer Claude in the terminal instead. See Review Claude Code’s work.

AI-017

Revue couldn’t stop the AI review

The review goes on. Try again, or let it finish. Show details has why.

AI-018

A finding or comment action failed

Revue couldn’t do what you chose on a finding or triaged comment, such as dismiss it or add it as a comment. Try again. Show details has why.

AI-019

A problem with an agent source or the Claude Code plugin

Revue couldn’t add, change, remove or reach an agent source, or the Claude Code plugin needs attention. For a source, check its address and token in Settings › Agent sources. For the plugin, see the state Settings › AI review shows and Claude Code plugin.

Not errors in AI

Revue asked you something, or held back for a reason you can act on. Nothing failed.

AI-010

The fix was applied with conflicts, or is still staged

The fix is in your files, but either some parts conflicted with your changes and left conflict markers, or its files are still staged. Nothing failed and nothing was committed. Resolve the markers, check the change, then commit.

AI-016

A fix changes files that can run code

The fix touches files that can run code on checkout, on build or when an editor opens them, so Revue warns and lists them before you apply it.

This isn’t an error. Read the change to each listed file before you apply the fix, and leave it if you aren’t sure what it does.

Creating pull requests

PR-000

Unclassified pull request failure

Revue couldn’t tell what went wrong. Choose Help › Copy Diagnostics and see Get help.

PR-001

Revue couldn’t update the base

Revue couldn’t bring the pull request’s base up to date before creating it. Check that the base branch still exists on GitHub, pick it again and try again.

PR-002

The pull request wasn’t created

GitHub didn’t create the pull request. Your draft is kept, so nothing you wrote is lost. Show details has GitHub’s reason. Fix what it says and try again. See Commit and create a pull request.

PR-004

Preflight found a problem

Before creating the pull request, Preflight checks the branch and the base with git and GitHub, and one check didn’t pass. Its row says what’s wrong. Fix it, then check again before you create the pull request.

PR-005

A problem with the pull request draft

Something in the draft couldn’t be used. The banner says what went wrong. Fix it, or dismiss the banner and try again.

Not errors in Creating pull requests

Revue asked you something, or held back for a reason you can act on. Nothing failed.

PR-003

A force push needs your answer

Your branch on GitHub has commits that a push from here would replace, so Revue asks before it force pushes. Nothing failed. Read what would be replaced, then choose whether to go on.

PR-006

The pull request was created with warnings

The pull request exists, but GitHub didn’t take everything, for example some reviewers or labels. Nothing else failed. Show details says what was left out, so you can add it on GitHub.

PR-007

That backport source wasn’t accepted

The pull request you named as a backport’s source couldn’t be used, for example because it isn’t a pull request of this repository. Nothing failed. Check the number or link and try again. See Check a backport against its source.

Data on this Mac

STORE-000

Unclassified local data failure

Revue couldn’t tell what went wrong. Choose Help › Copy Diagnostics and see Get help.

STORE-001

The diff cache isn’t available

Revue couldn’t open its diff cache file, so it keeps diffs in memory for now. Everything still works, but diffs are worked out again after Revue quits. Check that your disk has space and that ~/.revue is yours, then restart Revue. See Files and folders.

STORE-002

Revue couldn’t tidy its caches

Revue keeps its caches within the limits in Settings › Storage, and a pass that removes old entries failed. It tries again later. Nothing you made is lost. If space runs short, clear caches in Settings › Storage. See Manage disk space.

STORE-003

Revue couldn’t load comments

Revue couldn’t read the local comments for this checkout. It tries again on its next read. If it keeps happening, check that your disk has space, then restart Revue. Show details has why.

STORE-004

Inbox history couldn’t be saved

Mark read and Snooze still work, but Revue couldn’t save them, so they may not last until Revue opens again. Check that your disk has space. Show details has why.

STORE-005

Revue couldn’t restore your windows or tabs

Revue couldn’t reopen a window or tab, or the drafts it had saved. The saved file is kept and never overwritten with an empty one. Choose Retry on a tab that couldn’t be reopened, or open the checkout or pull request again.

STORE-006

A comparison wasn’t kept in the diff cache

Revue worked out a diff but couldn’t save it in its cache. Nothing is lost: it’s worked out again next time you open it.

STORE-007

A slice request’s answer wasn’t recorded

Revue answered a request to review a local slice, but couldn’t record the answer, so it may ask again. Nothing else failed.

Network

NET-000

Unclassified network failure

Revue couldn’t tell what went wrong. Choose Help › Copy Diagnostics and see Get help.

NET-001

Revue can’t reach GitHub

Revue sent a request and got no answer, so your Mac may be offline, or a VPN, proxy or firewall is in the way. Revue tries again on its own, and local review works meanwhile. If a review or comment was being sent, refresh before sending it again, as it may have been saved.

NET-002

Live updates couldn’t connect

Revue couldn’t keep its live connection to GitHub through your browser’s sign-in. Pull requests still update through pull request sync, and Revue reconnects on its own. If Settings › Live updates says why, such as a sign-in or Keychain problem, fix that. See Turn on live updates.

If Settings › Live updates says Keychain access wasn’t allowed, choose Try again, then choose Always Allow when macOS asks. Revue reads nothing until you do.

NET-003

Revue couldn’t list your browser’s profiles

Revue couldn’t read the browser’s list of profiles, so there’s none to choose in Settings › Live updates. The details say what went wrong. Check that the browser is installed, or choose another browser.

The app

APP-000

Unclassified app failure

Revue couldn’t tell what went wrong. Choose Help › Copy Diagnostics and see Get help.

APP-001

Revue couldn’t load settings

Revue couldn’t read your saved settings. Choose Open settings, then Retry. If it keeps happening, check that your disk has space and that ~/.revue is yours. Show details has why.

APP-002

Revue couldn’t save the setting

The change didn’t reach your saved settings, so it may not last. Try it again in Settings. If it keeps happening, check that your disk has space. Show details has why.

APP-004

The update check or install failed

Revue couldn’t check for updates or install one. Settings › Updates says why:

• Running from the disk image, or from a temporary location macOS chose. Revue can only update itself from Applications. Quit Revue, drag it to Applications, eject the disk image and open Revue from Applications.
• It couldn’t replace itself in its folder. Your account can’t write there. Move Revue to an Applications folder you own, or ask whoever manages your Mac.
• It couldn’t reach the update server. Check your network and try Revue › Check for Updates later. If a number in brackets follows, the server answered and turned the request away, so copy Diagnostics and see Get help.
• An update or the update list failed its signature check. Revue installs only updates signed by its developer, so it installed nothing and nothing on your Mac changed. Don’t try to work around it. Copy Diagnostics and see Get help.

See Update Revue.

APP-005

The theme couldn’t be imported

Revue couldn’t read the theme you picked, or it isn’t a kind Revue imports. Revue imports themes from VS Code, JetBrains IDEs, Zed, Sublime Text and TextMate. Check the theme and import it again. See Themes and fonts.

APP-006

A theme changed, can’t be read, or is hard to read

The theme you chose was changed or removed since you picked it, couldn’t be read, or has too little contrast between text and background. The banner says which. Choose another theme, import it again, or change its colours in Settings › Appearance › Custom themes.

APP-007

Revue couldn’t open a window

macOS didn’t give Revue a new window, for example when moving a tab to its own window. Try again. If it keeps happening, quit and reopen Revue.

APP-011

A link couldn’t open

Revue couldn’t open the Revue link you followed, often because it names something that no longer exists or that your account can’t see. The notice says why. Where it offers it, choose Retry, or open the pull request on GitHub.

APP-015

The review server couldn’t start

revue serve couldn’t listen on its address, usually because another copy is already serving there. Stop the other one, or set REVUE_BIND to another address. If it warns that the address isn’t local, set REVUE_UI_TOKEN too. See Environment variables.

APP-016

Background refresh failed

Revue couldn’t read the checkout or pull request again in the background. What’s on screen is from the last read that worked. Choose Try again. Show details has what git said.

APP-017

Revue couldn’t open the file chooser

macOS didn’t show the window for picking a file or folder. Choose Try again.

APP-018

Revue couldn’t save the log

Revue couldn’t write the CI log to the place you picked, often because that folder is read-only or full. The notice says why. Choose Try again and pick another folder.

Not errors in the app

Revue asked you something, or held back for a reason you can act on. Nothing failed.

APP-003

Settings are still saving

You tried to quit or close while Settings was still writing your changes, so Revue waited. Nothing failed. Wait a moment, or retry in Settings, then close again.

APP-008

Your shortcuts changed

A default key changed in this version of Revue, and Revue moved yours to the new key, or kept the old key because you already use the new one for something else. Nothing failed. The notice says which. Its button opens Settings › Keyboard shortcuts, where a banner offers Keep to go back to your old key. See Change keyboard shortcuts.

APP-009

Reset all settings?

You chose Reset all settings in Settings › Advanced, and Revue asks before it does. Nothing has changed yet. Confirm to put every setting back to its default, or cancel. Accounts, reviews and viewed marks are kept either way.

APP-010

Closing waits for work to finish

A request, a draft save or Settings was still finishing when you tried to close, so Revue kept the window or tab open. Nothing failed. Close again once it finishes.

APP-012

A detached HEAD is shown

The checkout isn’t on a branch, so Revue shows the commit it’s at. Nothing failed, but checkpoints and some branch actions need a branch. Check out a branch to use them.

APP-013

This tab stays on its layer

The branch moved, but the tab has a comment draft open, so Revue keeps it where it is so the draft isn’t lost. Nothing failed. Finish or discard the draft, or choose Switch to follow the branch now.

APP-014

This slice can’t be reviewed

Review This Slice isn’t available for this slice right now, and the notice says why. Nothing failed.

Notices and forms

UI-000

Unclassified notice or banner

Revue couldn’t tell what went wrong. Choose Help › Copy Diagnostics and see Get help.

Not errors in Notices and forms

Revue asked you something, or held back for a reason you can act on. Nothing failed.

UI-001

Revue didn’t do that

What you asked for can’t happen right now, and the notice, or the line under the control you used, says why. Nothing failed. Do what it says, then try again.

UI-002

The dismiss reason is too long

A reason for dismissing a finding has a length limit, and the line under it says how far over you are. Shorten it, then dismiss again.

UI-003

That value isn’t accepted

A field in the theme editor has a value Revue can’t use, and the line under it says why. Colours are hex values, such as #1F6FEB. Change the value, or press Esc to put back the one you had.

Crashes

PANIC-001

Revue crashed

Something inside Revue went wrong and it quit. Open Revue again. A crash report was saved in ~/Library/Logs/Revue/. If it keeps happening, choose Help › Copy Diagnostics and see Get help.