DeepSeek menu bar display is too long

[WXqwer]

Operating environment:
System: macOS 15.7.5
Hardware: MacBook Air M2 8GB
Software version: CodexBar 0.47.0 (111)

Issue: After adding DeepSeek as a provider, the menu bar displays too much content, taking up too many characters. We would like to add an option to "Display remaining bonus credit". Thank you.

Fields involved：balanceDetail = "(total) (Paid: (paid) / Granted: (granted))"

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed August 9, 2026, 5:12 PM ET / 21:12 UTC.

Summary
Keep open: current main and v0.49.0 compact the default DeepSeek balance, but custom menu-bar layouts still render the full detail string. The concrete repair is owned by #2816; a separate granted-only display preference needs product approval.

Reproducibility: yes. from source: a DeepSeek snapshot with the documented full balance description and a custom reset-countdown or reset-absolute token reaches the renderer unchanged on current main.

Maintainer decision needed

Question	Recommendation
After the custom-layout compacting repair lands, should CodexBar add a DeepSeek-specific menu-bar setting that displays granted/bonus credit instead of total balance?	Keep compact total only: Land the narrow custom-layout repair and retain compact total balance as the supported DeepSeek menu-bar value.

Why: The requested preference is new provider-specific configuration, not necessary to correct the current long-text defect, and VISION.md requires sign-off for new features.

Next step
The open linked PR owns the bounded custom-layout defect, while the remaining preference request needs a maintainer product decision.

Review details

Best possible solution:

Merge a proven compact-total fix for custom layouts, then keep total balance as the default unless a maintainer approves a clearly named DeepSeek granted-credit mode.

Do we have a high-confidence way to reproduce the issue?

Yes, from source: a DeepSeek snapshot with the documented full balance description and a custom reset-countdown or reset-absolute token reaches the renderer unchanged on current main.

Is this the best way to solve the issue?

Unclear overall: the linked compacting PR is the narrow solution for the current bug, while the granted-only request should not proceed without explicit product approval.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• Custom-layout DeepSeek balance text remains long on current main until the linked repair is merged and proven in a real menu-bar layout.
• Adding a granted-only metric would introduce a provider-specific persisted display choice without confirmed product direction.

Codex review notes: model internal, reasoning high; reviewed against 4a83b87aff22.

Label changes

Label justifications:

• P2: Custom menu-bar layouts visibly crowd the status item, but the standard display is already compact and users are not blocked.
• impact:ux-friction: The remaining behavior creates avoidable visual clutter in a user-facing menu-bar flow.

Evidence reviewed

What I checked:

• Default menu-bar display is compact: The standard DeepSeek status path calls the balance formatter, which returns only the first whitespace-delimited currency token from the full balance description. (Sources/CodexBar/StatusItemController+Animation.swift:1002, 0e46d1940c35)
• Custom layouts retain the raw description: Custom layout render data wraps the automatic rate window unchanged, and reset tokens render its raw reset description when no reset date exists; DeepSeek stores the full total/paid/granted string in that field. (Sources/CodexBar/StatusItemController+MenuBarLayout.swift:76, 4a83b87aff22)
• Shipped default-path fix: The formatter and its focused test are present in commit 0e46d19, which is tagged v0.49.0; that release fixes the reported standard-display case but not the custom-layout path. (Tests/CodexBarTests/StatusItemBalanceDisplayTests.swift:196, 0e46d1940c35)
• Open repair candidate: The linked PR explicitly covers reset-countdown and reset-absolute custom layout tokens and deliberately leaves the requested granted-only preference out of scope. (Sources/CodexBar/StatusItemController+MenuBarLayout.swift:57, 5c7dde5ae7d2)
• Maturity label unavailable: The required maturity shortlist helper could not locate qa/maturity-scores.yaml in this checkout, so stable maturity could not be verified.

Likely related people:

• Peter Steinberger: Current-source blame and available file history attribute the DeepSeek display formatter, provider balance formatting, and focused test to the v0.49.0 release commit. (role: recent area contributor; confidence: medium; commits: 0e46d1940c35; files: Sources/CodexBar/StatusItemController+Animation.swift, Sources/CodexBar/StatusItemController+MenuBarLayout.swift, Sources/CodexBarCore/Providers/DeepSeek/DeepSeekUsageFetcher.swift)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[Yuxin-Qiao]

Status on current main

The original menu-bar length problem is already addressed on main.

DeepSeek’s status item no longer shows the full
$total (Paid: $paid / Granted: $granted) string. It keeps only the leading balance token (for example $9.32), while the dropdown/menu card still shows the paid/granted breakdown.

Relevant path:

• StatusItemController.deepSeekBalanceDisplayText — takes the first whitespace-delimited balance token from primary.resetDescription
• Covered by StatusItemBalanceDisplayTests (menu bar display text uses deepseek balance)

So for the reported “too many characters in the menu bar” case: no further fix PR is needed for compact total balance. That behavior is newer than the reported 0.47.0 (111) build.

Remaining product question

The issue also asks for an option to display remaining bonus / granted credit only.

That is a separate preference, not required to fix the length complaint. Current recommendation:

Option	Recommendation
Compact total balance (current main)	Keep as the default / supported compact menu-bar value
DeepSeek-specific “Granted only” setting	Needs maintainer sign-off before implementing

If we do want the granted-only mode later, a bounded approach would be:

1. Add a DeepSeek menu-bar metric picker (Total vs Granted), similar to other provider-specific display modes
2. Prefer structured grantedBalance from DeepSeekUsageSnapshot over string parsing
3. Keep the menu card breakdown unchanged
4. Document that “Granted” is DeepSeek’s granted/bonus wallet, not a generic remaining-quota metric

Ask for maintainer

Please decide:

1. Close / mark as fixed for the length issue on main (compact total), or
2. Explicitly approve a follow-up for a DeepSeek “Granted only” menu-bar preference

Until (2) is approved, I would not open an implementation PR for the bonus-only setting.