Brimline

Troubleshooting

The usual cases, and what to do.

An account does not appear

  • Check that Claude Code is signed in with that account: start it with the folder of the account and run /status.
  • The folder must be ~/.claude or be named ~/.claude- something, and hold a .claude.json file. Otherwise, add it by hand with Add a Claude Code folder… in Settings, tab Accounts.
  • Click Search again after signing a new account in.
  • Check that the account is not hidden (switch in the Accounts tab).

A provider does not appear

  • ChatGPT, Gemini, Grok and Cursor are off until you turn them on: switch the provider on in its block in Settings, tab Accounts (or run brimline providers enable <name>). A provider that is off is not read at all, and has no account in the answers your agents get.
  • Brimline reads the sign-in of the official tool, so that tool must be installed and signed in: Codex for ChatGPT (~/.codex/auth.json), the Grok CLI (~/.grok/auth.json), Cursor itself, and Google's Antigravity CLI (agy, at ~/.local/bin/agy) for Gemini. A Codex folder somewhere else is added by hand with Add a Codex folder….
  • “Antigravity was updated: update Brimline.” means that the build of agy on your Mac is not one Brimline has verified: it launches nothing until a new version of Brimline lists it.

A provider says it has no limit to show

Some accounts have no limit Brimline can read, and it says so in one sentence instead of showing a number: Codex or the Grok CLI signed in with an API key (“there is no subscription limit to show”), Codex or Cursor keeping its sign-in where Brimline does not read it (“Cursor protects its sign-in on this Mac: Brimline does not read it. Usage is on cursor.com, Dashboard, Usage.”), Gemini without Antigravity, or a free Grok account (“xAI returns no credit limit for this account.”). Nothing is broken, and Brimline never shows a 0 % for a number it does not have. Learn more in the window opens the rest.

An account says “Session expired”

The access token that Claude Code keeps for that account has expired. Claude Code renews it when you use it; Brimline never does. Open Claude Code with that account (for example CLAUDE_CONFIG_DIR=~/.claude-work claude) and use it once; if Claude Code asks you to, run /login. At the next reading the account is up to date again. For the other providers it is the same with their own tool: “Open Codex to refresh the sign-in.”, “Open the Grok CLI to refresh the sign-in.”, “Open Cursor to refresh the sign-in.”

An account says “Sign in again”

The provider refused the token. Open Claude Code with that account and run /login.

An account says “Not signed in”

Brimline found the folder, but Claude Code has no sign-in for it in the Keychain. Start Claude Code with that folder and run /login.

If you signed in while the Keychain was locked (for example over SSH), Claude Code keeps the sign-in in a .credentials.json file inside the folder instead. Brimline 0.1 reads the Keychain only: sign in again from a normal session on the Mac, following Claude Code's recovery steps.

An account says “Unavailable”

The provider did not answer, answered with an error, or asked to slow down; the window gives the reason and the time of the next try. Brimline waits a little longer before each new try; nothing to do. If every account stays unavailable for hours, or the reason says the answer was not understood, the endpoint may have changed: check the issues of the repository.

The numbers look old

A Mac that sleeps does not read. Click Refresh, or shorten the interval in Settings, General.

An agent gets old numbers

The command and the MCP server read the cache that the app writes. If the app is not running, the cache gets old: start the app, or use brimline status --live.

No weekly limit on a team seat

That is what the provider reports for some team seats: no weekly limit across all models. Brimline shows “No weekly limit across all models” instead of an empty gauge. A weekly limit for one model may still appear.

Still stuck

Open an issue on GitHub with your macOS version and what the window shows. Never paste a token, and replace your addresses with examples.