Tokenmax 0.1.16

What’s new

The keychain prompt is gone.

• No more keychain dialog. Tokenmax used to read Claude Code's saved login from its own process, and macOS tied that permission to each individual build — so it asked again after every update, and again every time Claude Code renewed its token, usually once or twice a day. Always Allow could not stop that, and neither could a signing certificate. Tokenmax now reads the login through Apple's security tool, the same tool Claude Code saves it with. macOS already trusts that tool for this item, so nothing asks: not on first launch, not after updating, not when Claude Code renews its login. This is not a new exposure — any program running as you can read the item the same way. If you would rather Tokenmax never read the token at all, Settings → Data Source → Status line only still does exactly that.
• A 403 from the usage server is no longer shown as an expired login. Tokenmax used to treat "this login may not see usage" like "this login has expired": it discarded the credential, waited for a renewal, and asked you to sign in again — forever, because the renewed login is refused the same way. It now says the account or login does not get usage and names the usual cause: a login made with claude setup-token, which claude auth login replaces with a full one.

Install or upgrade

brew install --cask danieldrinhausen/tap/tokenmax

Or download Tokenmax-0.1.16.dmg below.

Tokenmax is signed but not notarized. On first launch, use System Settings → Privacy & Security → Open Anyway. There is no keychain prompt to answer any more.