deepseek-harness/snapshots/web/subagent-conversation/ui.expected.md at 9effa0c6b3ab5682b634df98092dd179cfa95ff3

0 Fork 0

Files

T

Yif 9effa0c6b3 feat(ui-chat): split turn stats into usage and time pills with dialogs

The turn tail's exposed meta line collapses into two icon pills — Usage
(database glyph, turn total) and Ran-for (clock glyph, wall time) — each
click-opening a details dialog; the calendar clock trails as plain text.
Cache hit, TPS, and TTFT move dialog-only, and narrow viewports collapse
the pills to bare icons. The TEMPORARY flat variant keeps the whole-line
trigger for the A/B test.

2026-08-28 01:34:18 +08:00

2.2 KiB

Raw Blame History

banner:
- navigation "Session hierarchy":
  - button "Ask a research subagent to"
  - text: /
  - 'button "Switch subagent: event-sourcing researcher"': event-sourcing researcher
  - button "1 subagent":
    - text: 1 subagent
    - img
- img
- text: Standard mode
- button "Session log":
  - text: Session log
  - img
- tablist:
  - tab "Chat" [selected]
  - tab "Trajectory"
navigation "Turn navigation":
- button "Jump to turn 1"
- button "Jump to turn 2"
button "System prompt":
- img
- img
- text: System prompt
text: Explain event sourcing in one sentence. {{clock}}
button "Copy":
- img
button "Thought for a while":
- text: Thought for a while
- img
paragraph: Event sourcing is a pattern where all changes to an application's state are stored as an immutable, append-only sequence of events, rather than persisting only the current state, enabling full auditability, temporal queries, and event-driven architectures.
button "Copy":
- img
button "Good response":
- img
button "Bad response":
- img
button "Branch into a new conversation":
- img
button "Ran for {{duration}}":
- img
- text: Ran for {{duration}}
text: {{clock}}
button "System prompt":
- img
- img
- text: System prompt
text: Now give the same explanation to a human reader. {{clock}}
button "Copy":
- img
button "Thought for a while":
- text: Thought for a while
- img
paragraph: Event sourcing is a pattern where all changes to an application's state are stored as an immutable, append-only sequence of events, rather than persisting only the current state, enabling full auditability, temporal queries, and event-driven architectures.
button "Copy":
- img
button "Good response":
- img
button "Bad response":
- img
button "Branch into a new conversation":
- img
button "Ran for {{duration}}":
- img
- text: Ran for {{duration}}
text: {{clock}}
textbox "Message or run a task... / commands, @ files or sessions"
button "Commands":
- img
'button "Access mode, current: Custom"': Custom
button "6% of context used"
button "Send message" [disabled]
text: 2 turns · 2 steps LLM {{duration}} TTFT avg {{duration}} · {{throughput}} tok/s Cache hit 99% Input 15.6K tok · Output 158 tok

2.2 KiB Raw Blame History

2.2 KiB

Raw Blame History