deepseek-harness/apps/web/tests/snapshots/code-mode-round/ui.expected.md at 8a8c1965d7538b356b906e16112f53ba2d4993e0

0 Fork 0

Files

T

Hypatia May 8a8c1965d7 feat(web): show durable token usage and context occupancy in the stats line

The chat stats line took its token totals from the loaded conversation nodes,
so paging changed them and compaction erased the billing behind replaced
content. It also had no way to show context occupancy: the numerator and
capacity never reached the browser.

Both now come from token-meter session projections read through the standard
useProjection seat. Window nodes keep supplying turn and step counts plus LLM
and tool wall times, which are correctly window-scoped facts about what is on
screen; accounting no longer comes from there.

`tokenUsage` supplies billing and cache hit. `contextPressure` supplies
occupancy, pairing the newest provider-reported prompt size with the newest
capacity recorded by `request/context`. Deployments without token-meter drop
the token groups; a route whose adapter advertises no capacity drops the
occupancy group rather than rendering a placeholder.

Occupancy is deliberately approximate: the numerator and capacity are
independent last-wins fields, not one atomic request observation, so switching
models pairs a fresh capacity with the prior route's pressure until the next
request reports usage. It is a user-facing reference figure that nothing in the
harness makes decisions from, and it matches how the TUI status line has always
computed occupancy. The Agent Note and token-meter README state this as a
decision, including why the atomic alternative was implemented and rejected, so
it is not re-litigated as a defect.

Snapshot delta is one added `Context N% of 128K` segment across eight web
goldens; the preceding commit absorbed master's pre-existing golden drift.

2026-07-30 14:48:19 +08:00

1.5 KiB

Raw Blame History

banner:
- navigation "Session hierarchy":
  - 'button "Using ONE run_code program: run" [disabled]'
- tablist:
  - tab "Chat" [selected]
  - tab "Trajectory"
text: "Using ONE run_code program: run bash echo CODE_ROUND_OK, then read the file missing.txt catching its error in the program. Return an object with both outcomes. Then reply DONE and stop. {{clock}}"
button "复制":
- img
button "在新对话中分支":
- img
button "编辑":
- img
button "▸ 上下文注入"
'button "Think The user wants me to write a single run_code program that:"':
- img
- img
- text: "Think The user wants me to write a single run_code program that:"
button:
- img
- img
text: Code Run bash echo and catch missing file read
img
text: Bash Echo CODE_ROUND_OK Read
button "missing.txt"
button "Think The program ran successfully. Let me now reply DONE as instructed.":
- img
- img
- text: Think The program ran successfully. Let me now reply DONE as instructed.
paragraph: DONE
button "复制":
- img
button "在新对话中分支":
- img
text: {{clock}}
textbox "给智能体发消息"
button "Add attachment":
- img
'button "Access mode, current: Danger Full Access"': Danger Full Access
button "选择模型，当前 DeepSeek-V4-Flash":
- text: DeepSeek-V4-Flash
- img
button "Send message" [disabled]
text: 1 turns · 2 steps Tool call {{duration}} Context 7% of 128K Cache hit 52% Input 17.2K tok · Output 252 tok

1.5 KiB Raw Blame History

1.5 KiB

Raw Blame History