[alwaysmavs]

The composer context usage ring changed to warning colors at 70% and red at 85%, making normal progress toward automatic compaction look like an error. Hovering also changed the ring to a high-contrast foreground.

Keep the ring in the muted foreground color at every usage level and on hover, while preserving its progress, focus indication, and usage details. Automatic compaction behavior is unchanged. Add a regression test confirming the meter uses the latest request snapshot and falls from 100% to 10% when a newer request reports lower usage.

Validation: 75 tests pass across context usage, composer mode controls, model limits, and agent event translation. TypeScript, changed-file lint and formatting, and git diff --check pass. No live long-session compaction or Electron visual test was performed.

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI; Enforced overrides: Organization
• Review profile: CHILL
• Plan: Essentials
• Run ID: dd5d5e63-8a71-49a6-a4f2-1384fe03d8ae

Commits

Reviewing files that changed from the base of the PR and between fbcf8f6 and cc9a435.

Files selected for processing: 2

• src/routes/Chat/ComposerContextUsageIndicator.tsx
• src/routes/Chat/context-usage.test.ts

Included review availability: This review used your included allowance. 3 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour.

Summary by CodeRabbit

• Style
  • The context usage indicator now uses muted text and an accent background on hover, rather than changing text color based on usage.

Walkthrough

The context usage indicator now uses muted text and an accent background on hover, without percentage-based text colors. A test checks that context usage reports 100% for a 240,000-token snapshot and 10% for a later 24,000-token snapshot.

Priority: Low

Merge Risk: Minimal · up to cc9a4

The change is mergeable with normal checks; no concrete production or workflow risk is identified.

Pre-merge checks: 3 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Description check		The description clearly explains the change and reports validation results, but it does not follow the required template. The Verification checklist and the entire Safety and Compatibility section are…	Organize the description under ## Summary, ## Verification, and ## Safety and Compatibility. Include the required verification checklist with completed or unchecked status, and address BYOK/OOMOL modes, credential exposure, agent tool…

Passed checks: 3 passed

Check name	Status	Explanation
Title check		The title follows the required <type>(<scope>): <subject> format, uses English, and accurately describes the neutral context usage ring change.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description clearly explains the change and reports validation results, but it does not follow the required template. The Verification checklist and the entire Safety and Compatibility section are missing.

Resolution

Organize the description under ## Summary, ## Verification, and ## Safety and Compatibility. Include the required verification checklist with completed or unchecked status, and address BYOK/OOMOL modes, credential exposure, agent tools and prompts, migration and packaging implications, documentation, and tests.

Finishing Touches

✨ Simplify code

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}