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

• banner:
  • navigation "Session hierarchy":
    • button "Ask a research subagent to"
    • text: /
    • button "event-sourcing researcher" [disabled]
  • img
  • text: Standard mode
  • button "1 subagent":
    • text: 1 subagent
    • img
  • button "Session log":
    • text: Session log
    • 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 "Good response":
  • img
• button "Bad response":
  • 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 "Good response":
  • img
• button "Bad response":
  • 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: 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