Support

reviewdawg requires macOS 26 or later. If something is not working, start here — and if the answer is not on this page,email jake@canucklelabs.com.

Connecting to GitHub

Sign in with your browser

The recommended route. Sign in with GitHub starts GitHub's device flow: reviewdawg shows a short code and copies it to your clipboard, you approve it on github.com, and the token GitHub issues is stored for you. It carriesrepo, read:org and notifications, so every feature works. It does not expire; revoke it from Settings → Applications on GitHub whenever you like.

Classic personal access token

Everything works, including the notification inbox. Create one atgithub.com/settings/tokens/newwith these scopes:

ScopeWhy
repoRead pull requests, diffs and review threads; submit reviews
read:orgSee pull requests in organisation repositories
notificationsPopulate the notification inbox and mark items read

Fine-grained personal access token

Scoped to repositories you choose and expiring on a date you set. Create one atgithub.com/settings/personal-access-tokens/new, pick your repositories, then set these repository permissions:

PermissionLevelWhy
MetadataRead-onlyRequired by GitHub; selected for you
Pull requestsRead and writeRead diffs and threads, comment, submit reviews
ContentsRead-onlyExpand context around a hunk
Commit statusesRead-onlyShow CI status on a pull request
ChecksRead-onlyShow individual check runs

The notification inbox does not work with a fine-grained token.GitHub's notifications API accepts classic tokens only, so reviewdawg switches the inbox and the menu-bar unread count off rather than letting them fail on every poll. Everything else works normally.

Troubleshooting

"GitHub rejected the credential."

The token was revoked or has expired — fine-grained tokens expire on a date you chose when creating them. Create a new one and reconnect. Your open pull request and any unsubmitted draft comments are preserved while you do.

"Your token is missing the … permission."

Regenerate the token with the scopes above. Classic tokens report their scopes, so reviewdawg warns in Settings when one is short; fine-grained tokens report nothing, so a missing permission only shows up when an action fails.

The notification inbox is empty and Settings says notifications are off

You are connected with a fine-grained token. Reconnect with a classic token carrying the notifications scope.

My organisation's repositories do not appear

If your organisation restricts third-party OAuth apps, an owner has to approve reviewdawg first. A personal access token is not subject to that restriction.

Switching accounts

Account → Switch Account…, or the Account section of Settings (⌘,). Switching clears the loaded queue and any cached pull requests, so nothing from the previous account remains on screen.

Managing your subscription

reviewdawg Pro is an auto-renewing subscription billed through your Apple Account. Manage or cancel it in System Settings → your name → Media & Purchases → Subscriptions, or from the Subscription tab of reviewdawg's own Settings (⌘,). Cancelling at least 24 hours before the period ends stops the next renewal; Pro stays active until the period you have paid for runs out.

Getting in touch

Email jake@canucklelabs.com. Bug reports are more useful with your macOS version, whether you connected by device flow or token, and what you were doing when it went wrong.