Skip to content

feat(usage): refresh every Claude login on the machine - #261

Open
StuBehan wants to merge 2 commits into
mainfrom
feat/refresh-other-claude-accounts
Open

StuBehan wants to merge 2 commits into
mainfrom
feat/refresh-other-claude-accounts

Conversation

@StuBehan

@StuBehan StuBehan commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

stack-nudge only ever ran claude /usage for the default login, so a second account run with CLAUDE_CONFIG_DIR (Mercury's StackOne Team seat in my case) never got its usage refreshed. Claude Code only writes cachedUsageUtilization when something asks, so the claude-usage extension had nothing to send for it either.

Now it finds the other config dirs by the .claude.json they all have, not by name, since nobody else will have called theirs ~/.claude-*. Three places: a scan two levels under home every hour (skipping Documents, Desktop, Downloads, Library etc so macOS doesn't throw a permission prompt), CLAUDE_CONFIG_DIR off any claude that's running (remembered in ~/.stack-nudge/claude-config-dirs so the row survives the session ending), and STACKNUDGE_CLAUDE_CONFIG_DIRS for anything else. Each one with a login gets the same probe with CLAUDE_CONFIG_DIR set, at most every 5 minutes per login.

A login is account + organization now, since your own plan and a team seat share an accountUuid, which also means a /login into another org counts as a switch for the default probe.

Ran it against my real machine, scan and the running session both find the Team seat (0.25s and 0.19s) and it comes back with its own numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant