You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The context window indicator likely misreports because getCurrentContextInfo or contextWindowFor in src/dataLoader.ts returns contextTokens equal to or greater than windowTokens for a fresh session. I need to see the full implementation of these two methods (the provided dataLoader.ts excerpt is truncated before they appear) to diagnose why contextTokens / windowTokens is always ≥ 1.
If every session—including a fresh, empty one—shows 100%, the likely causes in order of probability:
contextTokens defaults to windowTokens or a number that equals/exceeds the window size when no real data is available (e.g. a session file exists but has no usage line yet).
windowTokens is 0 or negative, and the if (info.windowTokens <= 0) → hide guard in statusBar.ts is either not hiding early enough (takes the Math.min(100, …) path) or the value is 1, making 1/1 = 100%.
getCurrentContextInfo infers context from the last log line, which for a fresh session might carry a stale or seeded context-token value that happens to match the model's window.
Suggested next step(s)
Please provide:
The full getCurrentContextInfo and contextWindowFor implementations from src/dataLoader.ts.
Any currentSessionId / session detection logic upstream that feeds these methods.
The likely cause is now addressed by the merged contributor PR #81 and is scheduled for v2.2.2: Claude Opus 5 is treated as a 1M-context model instead of falling through to the older 200K Opus window.
Please retest after v2.2.2 is published. If a fresh session still shows 100%, share the exact model identifier shown in the dashboard and the first context percentage after one response; no conversation text is needed. We will keep the issue open for confirmation.
v2.2.2 has now been released with the merged contributor fix from #81. Claude Opus 5 is recognized as a 1M-context model instead of falling back to the older 200K window, which addresses the fresh-session 100% reading described here.
I’m closing this as fixed in v2.2.2. If a fresh session still starts at 100% on v2.2.2, please reopen the issue with the exact model identifier and the first percentage after one response; no conversation text is needed.
Activity
github-actions commentedon Jul 30, 2026
🤖 Automated first-pass reply
TL;DR
The context window indicator likely misreports because
getCurrentContextInfoorcontextWindowForinsrc/dataLoader.tsreturnscontextTokensequal to or greater thanwindowTokensfor a fresh session. I need to see the full implementation of these two methods (the provideddataLoader.tsexcerpt is truncated before they appear) to diagnose whycontextTokens / windowTokensis always ≥ 1.Analysis
The percentage is computed in
src/statusBar.ts:If every session—including a fresh, empty one—shows 100%, the likely causes in order of probability:
contextTokensdefaults towindowTokensor a number that equals/exceeds the window size when no real data is available (e.g. a session file exists but has no usage line yet).windowTokensis 0 or negative, and theif (info.windowTokens <= 0) → hideguard instatusBar.tsis either not hiding early enough (takes theMath.min(100, …)path) or the value is 1, making 1/1 = 100%.getCurrentContextInfoinfers context from the last log line, which for a fresh session might carry a stale or seeded context-token value that happens to match the model's window.Suggested next step(s)
Please provide:
getCurrentContextInfoandcontextWindowForimplementations fromsrc/dataLoader.ts.currentSessionId/ session detection logic upstream that feeds these methods.TL;DR(中文)
上下文窗口指示器可能一直显示 100%,是因为
getCurrentContextInfo或contextWindowFor在新会话中返回的contextTokens等于或大于windowTokens。需要看到这两个方法的完整实现才能定位具体原因。分析
百分比计算为
info.contextTokens / info.windowTokens。如果所有会话(包括全新会话)都显示 100%,最可能的原因:contextTokens默认值等同于windowTokens(无实际数据时)。windowTokens为 0 或极小值,导致 1/1 = 100%。getCurrentContextInfo从最后一条日志行推断上下文,全新会话可能携带一条与模型窗口大小吻合的陈旧或种子记录。建议的下一步
请提供
src/dataLoader.ts中getCurrentContextInfo和contextWindowFor的完整实现。🤖 Generated by DeepSeek as an automated first pass — not a maintainer decision.
Carl723000 commentedon Aug 1, 2026
The likely cause is now addressed by the merged contributor PR #81 and is scheduled for v2.2.2: Claude Opus 5 is treated as a 1M-context model instead of falling through to the older 200K Opus window.
Please retest after v2.2.2 is published. If a fresh session still shows 100%, share the exact model identifier shown in the dashboard and the first context percentage after one response; no conversation text is needed. We will keep the issue open for confirmation.
🤖 Generated with OpenAI Codex
Carl723000 commentedon Aug 7, 2026
v2.2.2 has now been released with the merged contributor fix from #81. Claude Opus 5 is recognized as a 1M-context model instead of falling back to the older 200K window, which addresses the fresh-session 100% reading described here.
I’m closing this as fixed in v2.2.2. If a fresh session still starts at 100% on v2.2.2, please reopen the issue with the exact model identifier and the first percentage after one response; no conversation text is needed.
🤖 Generated with OpenAI Codex