Pocket ChiefHelptroubleshooting
Chief is missing or in the wrong place
Confirm the app is running, check other displays, open the workbench from the tray/menu bar, reset or center Chief, and verify size plus Always on top. Reinstall only after these checks.
First setup cannot finish
- Consent blocked: accept the screen-processing explanation in the move-in guide.
- Screen Recording denied: grant
Screen & System Audio Recordingin macOS System Settings, return to Pocket Chief, and retry. - Screen-reading check failed: keep readable text visible, confirm Pocket Chief is enabled in system settings, then retry. If macOS still uses an old app entry, restart the currently installed copy before trying again.
Automatic recording did not start
Completing move-in should start both automatic recording and record organization. If either did not start, open Settings > Recording, confirm both settings are on, and check Screen Recording permission. The first organized result may take one or two hours.
Current Work is not updating
Confirm automatic recording and record organization are on, the 15/30-minute window has elapsed, the selected AI source works, and Current does not show an organization error. One cycle may update an existing title or invested time instead of adding a row.
Footprints or Summary is empty
Footprints need automatic records. Summary also needs retained records and a working AI source. Check the selected date, category filters, hidden/deleted records, and source status. Fix the underlying records before regenerating Summary.
AI is unavailable
| Source | Check |
|---|---|
Cloud |
Sign-in, Cookies, visible status, network, and support ID |
Your API key |
Provider, model, base URL, API key, and provider balance |
Local |
Local service process, model availability, base URL, and resource limits |
Pocket Chief never changes source automatically. If one source fails, fix it or choose another in Settings.
Cloud login or Starter Cookies failed
The screen-reading check must pass before the connection chapter. For Direct, use the latest 6-digit email code and request a new one after expiry. For a Steam build, start it through the signed-in Steam client and verify the Steam identity path. Starter Cookies are granted once per Direct or Steam account after move-in, not once per installation.
Balance or purchase looks wrong
Refresh Cloud status, wait briefly for webhook processing, and confirm the Cookies appear on the Direct account that created checkout. Do not expect Direct and Steam balances to merge. For support, provide support ID, time, pack, currency, provider order ID, and the visible error—never card details or a full receipt link.
Voice is not working
Push-to-talk needs Microphone permission and local Whisper; the global macOS shortcut also needs Accessibility. Speech output needs speech synthesis or beep mode, audible volume, and a working Piper installation. Chief pauses proactive speech while hidden.
Agent integration or webhook has no content
For Claude Code / Codex, allow the project, repair/reinstall wiring if shown, rotate a changed token, and wait for a real summary. For outbound webhook, confirm it is enabled, the URL and credentials are correct, and the latest delivery status is successful. Failed outbound delivery has no persistent replay queue.
Installation and updates
macOS supports Apple Silicon only and uses in-app updates. Windows is an unsigned public beta and updates by manual download; SmartScreen or Unknown publisher may appear. Verify links and SHA256 on the download cards.
What to send support
Send version, platform, distribution/channel, exact symptom, approximate time, visible status, support ID, and a redacted error. Never send passwords, API keys, OTPs, card data, full logs, screen text, private screenshots, or full receipts.