GoogleDima Melnyk, Elia SecchiAnnouncement
The Outer Loop, Insights First: An Ambient Quality Agent That Diagnoses Your Production Agent
Summary
AI agents in production often pass health checks while silently failing at real tasks, such as confirming a seat without checking availability. Google and ADK released AQuA (Ambient Quality Agent), a sidecar system that continuously sweeps production agent trajectories from Cloud Trace, Cloud Logging, or BigQuery outside the request path. AQuA samples up to 1,000 recent sessions, grades each against a developer-defined goal and a nine-point breakdown checklist using a single-pass judge (or optional Gemini AutoRaters), clusters failures by mechanism, verifies clusters with a second model, and tracks them in BigQuery. Developers can trigger root-cause analysis that reads failing trajectories alongside the immutable deploy-time source snapshot, citing exact code lines without auto-applying edits. The system runs unattended, sweeps after each deploy or on demand, and produces verified failure clusters to feed back into the inner development loop, solving quality degradation that standard health checks miss.
Context
Post-launch quality degradation of AI agents that standard health checks fail to detect, where the failure is silent and happens inside the conversation.
Approach / What changed
A five-stage pipeline: sample recent sessions from telemetry (Cloud Trace, Cloud Logging, or BigQuery), grade each against a nine-point checklist and optional developer goal using a single-pass judge or Gemini AutoRaters, cluster failures by mechanism, verify clusters with a separate model, and track as insights in BigQuery. Root-cause analysis reads failing trajectories alongside the deploy-time source snapshot to cite exact code lines without auto-applying edits.
Takeaways
Production AI agents can silently fail (e.g., recommending a steakhouse to a vegan traveler) even when all infrastructure health checks pass; the failure happens inside the conversation.
AQuA’s five-stage pipeline (sample, review, cluster, verify, track) turns raw production trajectories into verified failure clusters without human-in-the-loop at scale.
Root-cause diagnosis in AQuA reads failing trajectories alongside the exact code revision captured at deploy time, enabling code-anchored fixes without auto-applying edits.
FAQ
How does AQuA protect data privacy?
AQuA reads trajectories from Cloud Trace, Cloud Logging, or BigQuery and keeps all data within the project boundary under the user's service account. It never sits in the request path or writes back to the agent, ensuring data isolation.
Can AQuA be attached to any agent stack?
The current reference implementation is scaffolded 1:1 beside a single ADK agent and requires three CLI commands to attach. For teams running dozens of agents, the post mentions exploring 1:N attachment from project telemetry without per-agent sidecar deployments.
What happens after AQuA identifies a failure cluster?
Developers trigger root-cause analysis that reads failing trajectories alongside the source snapshot, citing file paths and line numbers for defects in the repository. If the fault lies outside the code, it attributes the failure without a code diff. AQuA never auto-applies edits or opens pull requests.
Source and freshness
- Source
- developers.googleblog.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.