DocsHelp

Troubleshooting

This page covers prompts macOS may show while you use Whaatcher, and what to do when something looks wrong. For the prompt on first launch, see Install Whaatcher.

Access to Documents, Desktop or Downloads

macOS asks before an app reads protected folders such as Documents, Desktop and Downloads. It asks when a repository is in one of them, or when a program in a Whaatcher terminal, such as your agent, reads one. Click Allow.

If you don't, Whaatcher and programs in its terminals can't read that folder, and cards of repositories there may say Failed to read this repository. To change this, turn on Whaatcher in System Settings › Privacy & Security › Files & Folders.

Keychain access

Whaatcher keeps the tokens you add in Settings › Accounts in your macOS Keychain. If macOS asks whether Whaatcher can use a keychain item, enter your Mac login password and click Always Allow.

If you deny it, pull requests from that server don't load, and its row in Settings › Accounts says No token is saved for this server. Click Check there to be asked again.

SSH key confirmations

Whaatcher's git reaches your remotes when a repository's Graph opens or you press ⌘R, to see which remote branches still exist, and when you select an open or merged pull request, to fetch its code. It uses only credentials git already has and never asks for a password.

If your SSH agent confirms each use of a key, as 1Password or Secretive can with Touch ID, approve its prompt. If you decline, or git has no credentials for the remote, branch chips in Graph say why in their tooltip, and the pull request panel shows the reason with Fetch Again. Check that git fetch works in a terminal.

Your agent's sessions don't show up

Whaatcher records only agents started in the main terminal of a Whaatcher tab, not in a child terminal or another terminal app. Other agents, such as Codex, are recognized by name only. See Run an agent and Supported agents and hosts.

Analysis pending or failed

Analysis pending means the repository's analysis hasn't finished; large repositories take a while. Settings › Code Analysis shows each repository's status: turn the switch on if it reads off, and point at failed for the reason. Whaatcher retries at the next launch or when the analyzed branch gets new commits; Rebuild Analysis… in the ⋯ menu starts over. See Code Analysis.

Pull requests don't show up

Pull requests need a code host account. Without one, Pull Requests in Graph only asks you to add the repository's server in Settings › Accounts. If you've added it, the remote may use another host name, such as an SSH alias. See Accounts.

Code blocks aren't drawn

Code blocks are drawn only in the Preview of Markdown files in Files, for languages turned on in Settings › Code Blocks. Turning one on installs it with npm, so you need Node.js. After an update, a language may need Reinstall. See Code Blocks.

A terminal is gone after you reopen Whaatcher

When you quit, terminals running a program, such as your agent, keep running and reattach when you reopen Whaatcher; a terminal running only its shell closes. Restarting your Mac or logging out ends every session. If one ended unexpectedly while Whaatcher was closed, its tab says why. See Terminal.