Context window indicator shows higher fill immediately after compacting conversation than actual

Open

#321,648 opened on Jun 16, 2026 0 comments 0 reactions 1 assignee View on GitHub

@lramos15 is already working on this.

Since Jun 22, 2026.

Assessment

This issue has not been assessed yet.

Description

Version: 1.124.2 (Universal)
Commit: 6928394f91b684055b873eecb8bc281365131f1c
Date: 2026-06-12T00:12:36Z
Electron: 42.2.0
ElectronBuildId: 14159160
Chromium: 148.0.7778.97
Node.js: 24.15.0
V8: 14.8.178.14-electron.0
OS: Darwin arm64 25.1.0

Steps to Reproduce

Have an ongoing session that fills a noticeable portion of the context window
Trigger a compact of the conversation (button or /compact)
Observe the context window indicator immediately after compacting completes.

Expected Behavior

Immediately after a compact, the indicator should reflect the reduced context size, showing a lower fill level than before compacting.

Actual Behavior

Immediately after compacting, the indicator shows a 2x higher fill level than before the operation. The value is only corrected after the conversation continues, at which point the indicator updates to the correct, lower size.

Impact

Misleading context-usage feedback right after a compact, which is precisely when the user expects to see freed-up space. This can cause users to believe the compact had no effect or made things worse.

Video:
https://github.com/user-attachments/assets/6c29f74d-a3ef-4d53-8f5b-b9260b542ea9

Dominant language: TypeScript
Stars: 193k
Forks: 42.9k
PR merge metrics: PR metrics pending

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug]: Session row status indicator sits flush against the selection pill's rounded corner Open

clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

openclaw/openclaw#154145 · 2 comments · 1 reaction · Opened Sep 20, 2026
[good first issue] 🀄 Add new Grammar Point 265 (good-first-issue) Open

community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs

Difficulty 1/5 Under an hour Newbie friendliness 76/100

lingdojo/kana-dojo#30632 · 1 comment · 5 reactions · Opened Sep 20, 2026
[Duplicate Code] Repeated filtered model-alias assembly in proxy server Open

code-quality refactoring

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

github/gh-aw-firewall#8816 · Opened Sep 20, 2026
quickjs: support `timeout=None` (no per-call deadline) in `CodeInterpreterMiddleware` Open

integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

langchain-ai/deepagents#6450 · Opened Sep 20, 2026
`QuotedTweet.self_thread` is optional in syndication responses Open

Difficulty 1/5 Under an hour Newbie friendliness 88/100

vercel/react-tweet#225 · Opened Sep 20, 2026

More TypeScript issues