had fun building this deck in ChatGPT Sites for a talk on dots today… or rather, working with my dot to build it 🙂
demoing dots is hard. A lot of the personal and work context is private, and you can’t exactly schedule a proactive heads-up for the middle of a live demo.
so I picked a few stories about how my dots have helped me. I basically asked my dot to recount what happened in our chats, then recreated those conversations on the slides one message at a time.
from finding me two last-minute seats on an earlier train, to chasing for various refunds, to spotting an invoice that was higher than the quote.
And on the point of proactivity, my dot gave me a heads-up just before the talk to keep a backup demo handy
@hwchase17 At Vybe we treat it as both. Agents write what they learn into plain notes and skills that the team can read and edit, and every correction gets saved with the reason behind it. The hard part is still invalidation: last month's rule can be wrong after this month's product change.
@gabrielchua This is so cool! Replay is what makes browser agents usable for real work: you can actually see what happened instead of hoping it went right. Can't wait to try it.
@gregisenberg Same shift here. I walk home from work now and turn it into 30-minute working sessions with Codex over chat. Some of my best work of the day happens on that walk.
@hwchase17 Matches what we see. One trace failing is easy to catch. What's useful is grouping thousands of traces by use case and spotting the failure that keeps coming back. That's analytics, not alerting.
@gabrielchua The interesting part is deciding what deserves to wake you up. Does dot have a clear boundary between 'keep going', 'leave a morning note' and 'stop until I approve'? That's the bit I'd want to understand before leaving it overnight.
@bradneuberg The missing cost in the 15-agent setup is the human attention bill. I'd rather measure useful work per interruption than output per hour. What would you stop delegating even if the agents got twice as fast?