Repository navigation
Conversation
StuBehan
force-pushed
the
feat/usage-row-per-claude-login
branch
from
November 19, 2026 19:24
fe86a8e to
e798b9d
Compare
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.
Stacked on #261. Each extra Claude login gets its own row in the Usage tab under the default one, named by its org (or the dir, for a second personal plan) and plan, with its own history from that dir's transcripts. Alerts fire per login and say which, and while a Claude row is selected the mascot's stress takes the hottest login, so a team seat running out still shows when you're looking at your own plan.
UsageClient gets a claudeLogin case so everything already keyed by client picks the extra rows up.