Troubleshooting
macOS refuses to open the app the first time
If macOS reports the app "cannot be opened" on first launch, right-click the app in Applications and choose Open once — macOS remembers the choice afterwards. This is Gatekeeper's standard prompt for apps downloaded outside the App Store, not a fault in the download; see Download & Install for where releases come from.
The footer says the AI provider is unreachable
The app checks your configured AI endpoint at startup and shows a footer pill with the result. "Disconnected" means nothing answered at the configured URL — with the default setup that means Ollama isn't running. Set up your AI provider covers the two-command fix, and the Test connection button in Settings → AI re-checks on demand. Every non-AI feature works regardless.
My GitHub account is listed, but nothing loads
Pull requests, issues and avatars come up empty, or the app asks you to reconnect an account that is plainly still there. Your account and your token are stored separately on purpose: the account lives in ~/.git-manager/settings.json and the token in your encrypted vault / Keychain (Private by design explains why). Anything that removes one without the other leaves exactly this state — deleting vault.enc, resetting credentials, or copying settings.json over from another Mac without the corresponding secret.
The fix is the same in every case: Settings → Integrations, remove the account, and sign in again. That takes a few seconds and saves a fresh token in the vault.
If using Keychain mode and macOS asks whether Git Manager may use your confidential information, that prompt is the app reading your token — allowing it is what lets GitHub work. In default vault mode, no OS prompt is displayed.
Something went wrong — where are the logs?
The footer's activity button opens the activity log: every Git operation the app ran on your behalf, with its arguments, result and timing — the first place to look when an action didn't do what you expected. The activity log page shows how to filter it to errors only, and the same screen can reveal the on-disk log files to attach to a bug report.
A commit or push was refused
If your repository installs hooks (pre-commit, commit-msg, pre-push), they run here exactly as they do on the command line — a refusal shows the hook's own output, and the commit button's menu offers a one-time "without hooks" escape hatch. See Repository hooks.
Still stuck? Report it from the app
The footer's report button (the speech bubble, next to the activity button) opens the activity log filtered to failures. Pick the operation that went wrong and choose Report this problem: the app assembles the issue for you — the error, the operations that led to it, your app version and platform — and shows you the exact text before anything is sent. Paths, repository names and argument values are stripped out first; see Private by design.
With a GitHub account connected, one button posts it as an issue under your own account. Without one, copy the report and open an issue yourself.
Reporting a problem shows the whole screen.
The app will also tell you when a failure is not a bug — a protected branch, a hook of your own that refused a commit, an AI provider that isn't running — and explain what happened instead of filing it. That is the check working, not a refusal to listen: if you think it is wrong, there is a box to report it anyway.