Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
stack-nudge only ever ran
claude /usagefor 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.jsonthey 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 anyclaudethat's running (remembered in~/.stack-nudge/claude-config-dirsso 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
/logininto 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.