deepseek-harness/apps/web/tests/snapshots/subagent-conversation/ui.expected.md at ded7f8ffd1e9decab2a4d11fa62bdcdc8ee03f38

mirror of https://github.com/deepseek-ai/deepseek-harness synced 2026-08-15 21:04:50 +00:00

Files

creatixchu 84a6bae1c7 fix(web): drop the branch action from user and steering bubbles

The branch control on user and consumed-steering bubbles could enable
only when a completed turn ended with no node after the message at all,
so readers saw a permanently unavailable control whose tooltip promised
a state it could not reach. An enabled one would mislead anyway: a fork
at a message seq cuts at the containing turn/end and takes the answer
along, the opposite of the branch-to-re-ask reading a control on one's
own bubble suggests.

MessageItem loses its fork props, PendingSteeringBubble loses the
showBranch special case, and messageBranchSeqs narrows to
assistantBranchSeqs: only a completed turn's transcript tail that is
the turn's own content-text assistant may fork. A steered turn keeps
its fork point under the settled answer, because fork is a log-prefix
cut and the steer is model-visible history the child inherits.

Web aria goldens drop the user-bubble disabled-branch row and its
hidden explanation text; the nested-subagent golden also loses the one
enabled user-tail fork handle, a loss the decision note accepts.

2026-08-06 17:46:18 +08:00

2.5 KiB

Raw Blame History

banner:
- navigation "Session hierarchy":
  - button "Ask a research subagent to"
  - text: /
  - button "event-sourcing researcher" [disabled]
- button "1 subagent":
  - text: 1 subagent
  - img
- tablist:
  - tab "Chat" [selected]
  - tab "Trajectory"
text: Explain event sourcing in one sentence. {{clock}}
button "Copy":
- img
button "Context injection @deepseek-ai/dsh-system-prompt":
- img
- img
- text: Context injection @deepseek-ai/dsh-system-prompt
button "Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.":
- img
- img
- text: Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.
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 "Branch into a new conversation":
- img
text: {{clock}} Ran for {{duration}} TTFT {{duration}} {{throughput}} tok/s Now give the same explanation to a human reader. {{clock}}
button "Copy":
- img
button "Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.":
- img
- img
- text: Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.
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 "Branch into a new conversation":
- img
text: {{clock}} Ran for {{duration}} TTFT {{duration}} {{throughput}} tok/s
textbox "Message the agent"
button "Commands":
- img
'button "Access mode, current: Workspace Write"': Workspace Write
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.5 KiB Raw Blame History

2.5 KiB

Raw Blame History