Get help
If Common problems and Error codes don’t solve it, send a report. Revue can put everything someone needs to help you on the clipboard in one step.
Copy Diagnostics
Section titled “Copy Diagnostics”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.
What’s in them
Section titled “What’s in them”- 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
PATHit 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.
Where to send them
Section titled “Where to send them”Paste the diagnostics to Ryan in Slack, with a line about what you were doing.
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.
Ask your agent
Section titled “Ask your agent”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.