Production Debugging
This example gives an agent access to approved observability and repository sources during a production investigation.
Allowed Sources
Section titled “Allowed Sources”sentry://sentry_prodcloudflare_workers_observability://cloudflare_workersgithub://github_mainPrompt
Section titled “Prompt”Investigate the failing scheduled job. Use OneQuery for production evidence.Allowed sources are sentry://sentry_prod, cloudflare_workers_observability://cloudflare_workers, and github://github_main.Use narrow time windows. Summarize evidence before editing code.Start With Open Errors
Section titled “Start With Open Errors”onequery api \ --source sentry://sentry_prod \ /organizations/acme/issues/ \ -f 'params[query]=is:unresolved' \ --jsonInspect Recent Commits
Section titled “Inspect Recent Commits”onequery api \ --source github://github_main \ /repos/acme/web/commits?sha=main \ --jsonEvidence Summary
Section titled “Evidence Summary”Ask the agent to produce a summary like:
Evidence:- sentry://sentry_prod shows issue WEB-123 started after 2026-05-30 09:10 UTC.- github://github_main shows commit abc123 changed the retry window in the scheduled job.- cloudflare_workers_observability://cloudflare_workers shows failures only on scheduled runs, not manual runs.Next step: inspect scheduler retry policy in src/jobs.The summary should name the sources so a reviewer can match the claim to audit history.