Troubleshooting

”cannot verify the developer” on macOS

The binaries are currently unsigned. The shell installer clears the com.apple.quarantine xattr automatically; if you installed via npm and still see the warning, run:

xattr -d com.apple.quarantine "$(which mm)"

Proper Apple notarization is on the roadmap.

mm status says my model is “custom”

The string didn’t match any canonical id, slug, or alias in the registry. If it’s a real production model we missed, email it@llmstatus.ai — we’ll add it within a day. The registry refreshes every 6 hours, so additions roll out automatically once merged.

Offline / behind a corporate proxy

The CLI caches the snapshot at ~/.config/llmstatus/registry-cache.json and falls back to it when fetches fail. Run online once to seed the cache, then it works offline indefinitely (with a staleness warning after 30 days).

To point at a private mirror instead of cdn.llmstatus.ai:

export LLMSTATUS_REGISTRY_URL=https://mirror.acme-internal.com
mm status

The mirror must serve the same registry/keys.json + registry/latest.json + registry/VERSION.json layout. The signing chain still gets verified end-to-end against the pinned root key, so a malicious mirror can’t substitute snapshots.

mm login doesn’t open a browser

Set LLMSTATUS_NO_OPEN=1 to skip the auto-open (useful in headless / remote shells), then copy the printed URL into a local browser yourself.

npm publish returns EOTP

When publishing the package yourself, the npm 2FA web-auth flow needs a real interactive TTY. The Claude Code Bash tool, Remote Control’s pipe, and some terminal multiplexers can break TTY detection. Run from a regular Terminal.app / iTerm window, or set up an Automation token  which bypasses per-publish OTP.

CDN-cached 404 right after publish

Just after a fresh npm publish, npm install PKG may 404 for a few minutes while the registry metadata CDN propagates. The package IS published — the + PKG@VER line printed during publish is authoritative. Verify via the package page on npmjs.com  or by downloading the tarball directly.

Still stuck?

Email it@llmstatus.ai with the command you ran, the full output, and your OS / Node version. We answer fast.