Tracing a Google ADK agent in Opik takes two lines of code.
But, Google's ADK has a footgun: when one ADK agent hands off to another, ADK starts a new run, so one user message shows up as two traces.
We put together a little guide to fixing this with a single Opik call. We stood up a two-agent support bot with ADK and Gemini, traced it in Opik, then ran 23 hard support cases on Gemini 3.8 Flash and 3.5 Flash-Lite:
- neither tried a forbidden refund, even with a fake "refund pre-approved" note
- Flash-Lite was 5× cheaper and ~6× faster
- the LLM judge scored a correct refusal 0.50, so the policy check reads tool-call arguments in code
comet.com/site/blog/trac…
But, Google's ADK has a footgun: when one ADK agent hands off to another, ADK starts a new run, so one user message shows up as two traces.
We put together a little guide to fixing this with a single Opik call. We stood up a two-agent support bot with ADK and Gemini, traced it in Opik, then ran 23 hard support cases on Gemini 3.8 Flash and 3.5 Flash-Lite:
- neither tried a forbidden refund, even with a fake "refund pre-approved" note
- Flash-Lite was 5× cheaper and ~6× faster
- the LLM judge scored a correct refusal 0.50, so the policy check reads tool-call arguments in code
comet.com/site/blog/trac…