Skip to content

Get help

If Common problems and Error codes don’t solve it, send a report. Revue can send one itself, or put everything someone needs to help you on the clipboard for you to send.

  1. Choose Help › Report an Issue.
  2. Write what happened.
  3. Check what’s included.
  4. Choose Send report, and approve or touch your SSH key if you’re asked.

Revue signs the report with an SSH key that’s on your GitHub account, so it needs you signed in to GitHub in Revue. Report an issue has the details, and Privacy says what’s sent and how long it’s kept.

If none of the SSH keys on this Mac are on your GitHub account, Revue says “Add an SSH key to GitHub”. Make a key and add it with the four steps in Add an SSH key to GitHub, then choose Check again.

If you forward your SSH agent to other servers (ForwardAgent yes), those servers can ask it to sign too, including Revue reports. Forward it only to servers you trust.

Choose Help › Copy Diagnostics. Revue takes a few seconds to gather the report, says “Gathering diagnostics” while it works, and then “Copied diagnostics” once the report is on the clipboard. Nothing is sent anywhere until you paste it.

If an error’s details show a code, such as “Error GIT-012”, choose Copy in the details too, and paste it with the report.

  • Revue’s version, the macOS version and where Revue runs from.
  • How updates stand.
  • The tools Revue found (git, the GitHub CLI, jj, Claude Code and Codex) and the PATH it uses.
  • How GitHub is connected, without your account’s name.
  • How much space Revue’s data uses.
  • The last 200 lines of Revue’s log.

Tokens, the update access code, email addresses, repository names and owners, and your home folder are taken out before the report reaches the clipboard. Read it before you send it if you like. It’s plain text.

Paste the diagnostics to Ryan in Slack, with a line about what you were doing, or send them with Help › Report an Issue.

If someone asks for Revue’s log, choose Help › Show Logs in Finder. It shows ~/.revue/desktop/desktop.log. Once the log passes 5 MB, Revue moves it aside as desktop.log.1 when it next opens. Crash reports are in ~/Library/Logs/Revue/.

To make the log say more, set Log level in Settings › Advanced to debug or trace, then quit and open Revue again, since the level takes effect the next time Revue opens. Put it back to info afterwards, as a detailed log grows quickly.

Claude Code and Codex can answer questions about Revue from this site. The whole site is one text file at https://revue.ryc.sh/llms-full.txt, with every page, shortcut, setting and error code in it. Ask your agent to read it, then ask your question.