fix: support xhigh thinking effort level - #314
Merged
Merged
Conversation
- Add xhigh to TranscriptThinkingEffort, ThinkingEffortLevel, and ClaudeSettings.effortLevel unions - Accept xhigh and xHigh casings from /model stdout and settings.json - Pass unknown-but-word-shaped effort values through with a trailing "?" marker (e.g. "super-max?"), so future Claude Code effort levels render gracefully without code changes - Display "Thinking: default" when no effort signal is available from the transcript or Claude settings, replacing the prior silent medium fallback Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Owner
|
Thanks, will publish this in the next release. |
pcvelz
added a commit
to pcvelz/ccstatusline-usage
that referenced
this pull request
Apr 17, 2026
Bring in upstream changes: - feat: add refreshInterval configuration for Claude Code status line (sirmalloc#297) - feat: support xhigh thinking effort level (sirmalloc#314) - chore(deps-dev): bump the dev-dependencies group (sirmalloc#301, sirmalloc#316) - chore(deps-dev): bump https-proxy-agent from 7.0.6 to 8.0.0 (sirmalloc#302)
pcvelz
added a commit
to pcvelz/ccstatusline-usage
that referenced
this pull request
Apr 17, 2026
…2.3.16) When session usage hit 100% but weekly was still below 100%, the Reset Timer widget incorrectly showed the weekly reset time (hours/days away) instead of the session reset countdown (5-hour window). Session and weekly limits reset independently — session filling up on its own shouldn't swap the timer to the weekly reset. Extra usage only kicks in when weekly itself hits 100% (or on a charged [1m] model). Also folds in: - Opus 4.6 → 4.7 model references throughout docs, examples, tests - Upstream sync (5 commits): refreshInterval (sirmalloc#297), xhigh thinking effort (sirmalloc#314), dev-dep bumps
This was referenced Apr 21, 2026
This was referenced Apr 27, 2026
3 tasks
huangguang1999
added a commit
to huangguang1999/ccstatusline-zh
that referenced
this pull request
Apr 27, 2026
* fix: 思考力度组件支持 xhigh 等级 Opus 4.7 引入了 xhigh 思考力度档位，原实现仅识别 low/medium/high/max， 导致状态栏显示回退到 medium。同步上游 sirmalloc/ccstatusline#314： - 白名单扩展为 low/medium/high/xhigh/max - 引入 ResolvedThinkingEffort，未知但合法的 effort（如 super-max） 以 "xxx?" 形式展示 - 没有 effort 时回退到 "default" 而非误导性的 "medium" 修复 #10。 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * chore: bump version to 2.2.11 --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
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
2 participants
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.
Summary
xhighthinking effort level. Accepts bothxhighandxHighcasings from/modeltranscript output and fromeffortLevelinsettings.json.ThinkingEffortwidget up to future effort levels: any unknown but word-shaped effort name (2–20 chars,[a-z0-9-], case-insensitive) is rendered verbatim with a trailing?(e.g.super-max?) instead of being silently dropped.ThinkingEffortwidget's fallback display from a silentmediumassumption to an explicitdefaultwhen no effort signal is available from either the transcript or Claude Code settings. This avoids showing a misleading effort label when ccstatusline genuinely can't determine the current value (fresh session, noeffortLevelset, no/modelcommand run yet).Test plan
bun test— all 742 tests pass, including 11 new cases coveringxhigh/xHigh,super-max/Super-Maxunknown-but-valid values, and rejected shapes (oversized, single char, contains whitespace).bun run lint— clean.defaultfallback.dist/ccstatusline.js.