BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//sf26-agenda//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VEVENT
UID:SESS-218@sf26-agenda
DTSTAMP:20261020T151709Z
DTSTART:20261104T164500Z
DTEND:20261104T171500Z
SUMMARY:Event-driven Agents: Why your app shouldn't wait for the user to as
 k
LOCATION:Innovation Theater
DESCRIPTION:Adam Wagner\n\nMost agentic apps use the turn-based chat model.
  But a lot of the real value in agentic apps comes from something happenin
 g\, not from a user prompt: a flight gets delayed\, a new listing hits the
  market. Forcing that into a request/response loop means the agent can onl
 y ever react\, and it puts the burden of noticing on the user. This talk a
 rgues that chat is a UI\, not an architecture. The right pattern underneat
 h is event-driven: an agent that senses a change\, decides whether it's wo
 rth acting on\, and reaches out proactively. We'll walk through real examp
 les\, including an airline agent that rebooks a delayed flight before the 
 traveler notices and a real estate agent that surfaces a strong listing mi
 dweek instead of waiting for Saturday's open house. You'll walk away with 
 a concrete way to evaluate whether an event was worth surfacing at all\, u
 sing an LLM-as-judge on the decision itself\, not just the message and a m
 ap of what to build before you ship an agent that reaches out on its own. 
 By attending this session\, your contact information may be shared with th
 e sponsor for relevant follow up for this event only.
URL:https://sf26.rmoff.net/s/event-driven-agents-why-your-app-shouldnt-wait
 -for-the-user-218
END:VEVENT
END:VCALENDAR