I promise this isn't meant to be snarky, but is that not just...logs?
replyIt's only logging if an obsolete human does it.
replyBut the future is here and thus it's called "Agentic causality's reified temporal traceability."
"Temporally Reified Agentic Causality Traceability Report" - TRACTR.
replyWhich are unavailable with the leading American models. You can't look at the complete traces of OpenAI or Anthropic model agents, as they are encrypted (there's been discussion of a couple of different ways to expose those, but that violates terms of service, and well, you shouldn't have to find complicated ways unencrypt your own usage logs).
replyIt's logs of activity the US models hide from you in fear of them being used by competitors.
replyIt's useful logs which i think is an important distinction.
replyLogs that aren't missing anything out of the box. I'd say it's pretty underused concept in time of 8TB consumer SSD drives.
replyDon't those cost 1-2k?
replyCloser to 1k, even pcie 5 versions.
replyI'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.
reply[0] https://www.dreamcoder.ai -> scroll down to the event graph.
is it just for coding? the docs don't mention code, just "agents"
replySeems like Agentsview, but built in and likely less features(at least, as of now): https://github.com/kenn-io/agentsview
reply