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

• 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.Your parent agent id is "session-{{uuid}}". Before you finish, send your result to that agent with send_message({ agent_id: "session-{{uuid}}", message: "" }). The parent shares your workspace but does not automatically receive your transcript, tool output, or reasoning. Send earlier messages as well when a finding changes what the parent should do next; sending a message does not end your turn. {{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