fix: mobile view usage bar fix#914
Conversation
How to use the Graphite Merge QueueAdd the label Main to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
Claude finished @MaheshtheDev's task in 2m 33s —— View job Review Complete
Summary: This PR fixes broken mobile usage bar code that was referencing undefined variables ( No bugs or security issues found. The percentage value is already properly bounded (0-100) upstream. Score: 10/10 — Clean bug fix, ready to ship. |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-mcp | 5fdd733 | May 09 2026, 04:54 PM |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
supermemory-app | 5fdd733 | Commit Preview URL | May 09 2026, 04:55 PM |
There was a problem hiding this comment.
Overview: Fixes mobile usage bar by replacing broken code (referencing undefined variables) with a working unified "Plan usage" display.
Issues found: None — this looks good to ship.
Details: The previous implementation referenced tokensToCredits, tokensLimit, tokensPercent, searchesPercent, and searchesLimit which were never imported or defined — this would cause runtime ReferenceErrors. The new code correctly uses planUsagePct, tokensUsed, and searchesUsed which are properly exported from useTokenUsage. The planUsagePct value is already bounded to [0, 100] by calculateUsagePercent() in billing-utils.
Score: 10/10

No description provided.