Tokenmax 0.1.10

What’s new

Claude credential recovery that explains the real state

A Claude Code conversation can stay active on its existing connection while Tokenmax’s older saved Keychain credential is rejected by the quota endpoint. Tokenmax now says that plainly instead of implying your working session is broken.

When a fresh status-line quota reading is available, Tokenmax uses it while waiting for the saved credential to renew. If Claude Code does not renew it on its own, Open Terminal + Copy Login opens your configured terminal and copies claude login for a deliberate recovery. Tokenmax still never refreshes or writes your Claude credential itself.

Codex quota reads restored

Codex CLI 0.149 removed the old -a untrusted approval policy. Tokenmax now uses the supported never policy for its read-only App Server query, restoring Codex quota and model reads.

Correct Keychain log path

The troubleshooting guide now points directly to the real diagnostic log:

~/Library/Application Support/Tokenmax/logs/tokenmax.log

Install or upgrade

brew install --cask danieldrinhausen/tap/tokenmax

Tokenmax is signed but not notarized, so first launch requires System Settings → Privacy & Security → Open Anyway. Because this is a new binary, Keychain monitoring may ask once for access; choose Always Allow if you want macOS to record the grant.