Building redaction-first tracing for coding agents, and why unknowns must never read as zero

The author found that existing LLM observability tools like MLflow, Langfuse and LangSmith record spans well but do not fit long-running coding-agent sessions, which generate tree-structured tool calls and sensitive transcripts. Instead of adopting one of those stacks, they extended their own harness, code-copilot-team, with an analytics layer built on a session, turn and tool-call data model. The store holds 65 real sessions and excludes 32 noise sessions, a count shown on every page so the denominator stays honest. Redaction is applied at ingest through three modes (none, code, metadata-only), and the judge path uses the stricter of the recorded and current modes. A review finding showed that truncating before redacting let a secret straddling a code fence leak, so the fix redacts the full input first and a test now covers that boundary case.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in