I'm glad they're doing this also and that more people are adopting it. Event sourcing [0] is the right way to represent informaiton like tool calls, user interactions, etc. --- it makes it easy to fork conversations and maintain a cohesive conversation stream and stable message history that does not break the cache.
Quoting it in full so you don't stealth-edit your comment:
<quote>
I'm glad they're doing this also and that more people are adopting it. Event sourcing [0] is the right way to represent informaiton like tool calls, user interactions, etc. --- it makes it easy to fork conversations and maintain a cohesive conversation stream and stable message history that does not break the cache.
</quote>
why dont you mention that its your site instead of prenteding like something you discovered?
[0] https://www.dreamcoder.ai -> scroll down to the event graph.