ui-expanded.expected.md 3.7 KB

  • 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 "More actions":
    • img
    • button "Open right sidebar":
    • 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" [expanded]:
    • text: Thought for a while
    • 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
  • 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" [expanded]:
    • text: Thought for a while
    • 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
  • button "Ran for {{duration}}":
    • img
    • text: Ran for {{duration}}
  • text: {{clock}}
  • textbox "Message or run a task, / commands, @ files or sessions"
  • button "Add files or run commands":
    • img
  • 'button "Access mode, current: Custom"': Custom
  • button "6% of context used"
  • button "Send message" [disabled]
  • button "2 turns 2 steps · {{throughput}} tok/s":
    • img
    • text: 2 turns 2 steps{{throughput}} tok/s
  • button "15.7K tok · Cache hit 99%":
    • img
    • text: 15.7K tokCache hit 99%