Post

im not kidding and im sure @cameron.stream can back me up from another direction: if you arent capturing/mining your team's agent session logs, you are leaving it all on the table. we have a service that lets you run RAG tool calls against vectorized agent session summaries and it is 🔥🔥🔥

the fact that ant/oai dont trivially expose a "download all my org's inference logs" button makes me think that they realize those logs are worth almost as much as the output of the agent sessions themselves

it is deeply unnerving that a tech demo that would have been impossible and/or worth billions of dollars a year ago is now a side-project

1 repost20 likes

That is super cool! Can you speak a little bit about how you're doing evals? Like is it measuring successful vs failed tool calls, or something like that?

for the agent sessions i’m chunking, summarizing with haiku, computing embeddings with msft harrier, storing in qdrant. transcripts themselves get run through an AGGRESSIVE redaction pass, stored in s3 with WORM semantics, static html renderer

Are you embedding json session logs from Claude’s file system? It took some work but a few hooks can log conversation turns into MLflow, then I backfill my embeds from there