feat: heat gauge colors for context percentage widget#179
Open
EthanJStark wants to merge 13 commits intosirmalloc:mainfrom
Open
feat: heat gauge colors for context percentage widget#179EthanJStark wants to merge 13 commits intosirmalloc:mainfrom
EthanJStark wants to merge 13 commits intosirmalloc:mainfrom
Conversation
added 13 commits
February 18, 2026 11:19
- Add is1MModel parameter to getHeatGaugeColor() - Define conservative thresholds: 40%/55% for standard, 10%/15% for [1m] - Add comprehensive test coverage for both model types - Maintain backward compatibility (defaults to standard thresholds)
- Pass is1MModel flag to getHeatGaugeColor() based on context config - [1m] models now use conservative 10%/15% thresholds - Standard models use 40%/55% thresholds - Add comprehensive tests for model-aware color application
- Add detailed JSDoc for getHeatGaugeColor function - Document threshold rationale for both model types - Explain why [1m] models need more conservative thresholds - Add usage examples showing different model behaviors - Document color selection from Tailwind CSS palette
- Add null assertions in ContextPercentage tests to satisfy TypeScript - Remove unused @ts-expect-error directive in colors tests - All tests passing, TypeScript compilation successful
- Add heatGaugeColors field to WidgetItemSchema (defaults to true) - Add contextWindow field to RenderContext interface - Port heat gauge color logic, toggle keybind, and editor display from ContextPercentage into ContextPercentageUsable - Support custom thresholds from settings (standard/extended) - Update tests: existing calculation tests use heatGaugeColors:false, new tests verify color on/off behavior
All models now use a single default threshold set (cool=30/warm=40/
hot=55/veryHot=70). Removes the compressed 1M-model thresholds that
were added when 1M context models were less performant.
- Remove `is1MModel` param from `getHeatGaugeColor`
- Flatten `settings.heatGaugeThresholds` from `{ standard?, extended? }`
to a single optional `HeatGaugeThresholdSet` (power user customisation preserved)
- Remove model-detection branching from ContextPercentage and
ContextPercentageUsable widgets
- Update tests to reflect simplified schema
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
1 participant
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.
What
Adds dynamic color coding to the context percentage widget, giving users an at-a-glance visual signal of how critical their context usage is — from calm cyan when usage is low, escalating through green → yellow → orange → red as context fills up.
Why
A bare percentage number requires active interpretation. Color makes the urgency of context usage immediately obvious without needing to read the number, which matters most when you're deep in a session.
Approach
heatGaugeThresholdsfield to~/.config/ccstatusline/settings.json. Zod validates that values are between 0–100 and strictly ascending (cool < warm < hot < veryHot).heatGaugeColorsboolean field (defaults totrue). Toggle viahin the TUI items editor.modelfield in the status JSON can arrive as either a plain string or an object depending on the Claude Code version in use; both formats are now handled correctly across the schema and all widgets that read model info