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"