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

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

0 reposts9 likes

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

historically have been using the magic aws bedrock “log all inference calls to s3” checkbox but finally deployed an agent gateway to sit between all inference providers and all consumers (which also logs everything to s3)

oh right I remember you said this. our enterprise hosts on bedrock too but no one has access to the infrastructure, so I end up looking for clientside solutions