Repository navigation
Troubleshooting
Full guide: docs/troubleshooting.md.
The installed app has no (or a mismatched) Sparkle public key — usually a local
dev build rather than the notarized release, so it can't validate any update.
Fix: brew upgrade --cask tokmeterbar, or download the notarized zip from
Releases and replace the app in
/Applications. From 1.14.1 on, a keyless build no longer advertises auto-update,
so it can't produce this error.
The daemon isn't answering: tokmeter-mcp daemon status, then
tokmeter-mcp daemon start (or daemon install-agent for always-on). A bar that
reads "offline" while the daemon is healthy is usually a stale /tmp pidfile; it
self-heals in ~10s, or daemon restart forces it. If the daemon is running but
not answering (curl http://127.0.0.1:9877/api/ready times out),
tokmeter-mcp daemon restart restarts it (under the LaunchAgent:
launchctl kickstart -k gui/$(id -u)/com.tokmeter.daemon).
Sealed days are immutable and frozen at the prices of the day they sealed; a normal scan never re-derives them. A dropped total is almost always a display issue (daemon drift, or a project fragmented across subfolders) — sum the aggregate files on disk to confirm the ledger is intact.
Don't call a full scan in a loop — read the daemon (127.0.0.1:9877) or MCP
server instead. Editing/re-saving old transcripts bumps their mtime and can
trigger a rescan.
A registry search lists every published version oldest-first; the newest
active entry is the latest. Don't read the first row as "current."