Repository navigation
Give agn's spans a listener again - #200
Merged
Merged
Conversation
dda0ff6 moved the CLIs to a transcript the trace hook reads and dropped the OTLP proxy. That fits codex and claude, whose telemetry reports that a model call happened and not what was in it. agn is not one of those: it reports its own turns, sets the response text and tool calls on them, and keeps no transcript for the hook to read. So agn was left exporting to 127.0.0.1:4317 with nothing bound to it, and the daemon only exports the invocation message -- Turns is reached from the hook alone. Its llm.call and tool.execution spans went nowhere, and a trace held the message with no call under it. The proxy is restored for the agn path only and given the endpoint explicitly, so what the workload was handed cannot point agn somewhere nothing is listening.
This was referenced Sep 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
dda0ff6moved the CLIs to a transcript the trace hook reads, and dropped the OTLP proxy. That reasoning fits codex and claude — their telemetry reports that a model call happened and not what was in it.agn is not one of those. It reports its own turns, and sets
agyn.llm.response_textand the tool calls on them itself (agn-cli/internal/loop/agent.go). It keeps no transcript for the hook to read, so nothing runs the hook for it.That left agn exporting to
127.0.0.1:4317with nothing bound to it — the orchestrator still injects that endpoint (assembler.go:1127) — while the daemon exports only the invocation message, sinceExporter.Turnsis reached fromcmd/agynd-trace-hookalone. agn'sllm.callandtool.executionspans went nowhere.The trace therefore holds the message with no call under it, which is what the two agn-runtime E2E tests report:
Both reproduced on three CI runs, on 4-core and 8-core runners alike, with the workload healthy and every upstream LLM call returning 200 — the calls happen, only their spans are lost. They still pass on a local VM because it runs cached older images.
internal/tracingproxyis restored fromdda0ff6^and started on the agn path only; codex and claude keep the hook. The endpoint is passed to agn explicitly from the proxy's own address, so whatever the workload was handed cannot point it somewhere nothing is listening.go build,go vetandgo test ./...pass, including the restored package's own tests.