Re:If you don't run your own LLM proxy, how do you even know...
by JustFinishedBSG on Monday October 19, 2026 @12:42PM
(#50154600)
Well if you own the harness ( and you should ) you see everything you want.
But I’ve seen approaches using eBPF to collect telemetry to OTEL
Re:If you don't run your own LLM proxy, how do you even know...
by dinm on Monday October 19, 2026 @01:17PM
(#50155121)
Sometimes, it gets to very hacky solutions, such as what we did at Laminar with Claude Agent SDK. Basically we spin up a tiny in-process proxy that intercepts requests and responses and emits the telemetry as OTEL traces. We repoint the Python / JS SDK to convince the harness that our proxy is the anthropic URL, and the proxy then forward the request downstream. I wrote about it some time ago [1]. This is definitely not elegant, but it generally works.
[1] https://laminar.sh/blog/2025-12-03-claude-agent-sdk-instrume...
There have been numerous scandals of AI companies offering CC/cursor alternatives, then indexing data they never should have; specifically Z.ai [0], ByteDance Trae [1] and Alibaba Qwen [2]. Maybe the argument should be that all harnesses should be sandboxed and monitored for all networking.
If it were me, all AI harnesses would be running on a VM with network logging enabled. Beyond not being able to trust what data they send via the harness, you should audit what data they access.
[0] https://www.chosun.com/english/industry-en/2026/09/22/ABYLC3...
[1] https://github.com/segmentationf4u1t/trae_telemetry_research
[2] https://github.com/QwenLM/qwen-code/issues/11198