Five tabs to triage one Sentry error: the email, the Sentry web UI, the GitHub repo for the offending release, the deploy dashboard for the timeline, Slack to ping whoever shipped it. The Sentry integration shipped May 11, and Annie reads Sentry directly now. The first question we asked her returned 67 unresolved errors across four services.

The plumbing

A Sentry user-auth token, stored KMS-encrypted, behind agent-gateway. Annie has the full Sentry surface and every operation Sentry exposes to integrations, find_issues, get_event, get_release, everything Sentry ships. We didn't write a custom subset.

Same day the integration went GA, we instrumented the rest of the stack: anyshift-frontend, anyshift-backend, agent-gateway, agent-runtimes, ai-workbench, the infra Terraform. Every component emits into one Sentry org now, and Annie has read access to all of it.

The first investigation

We asked one question:

List the most recent critical Sentry errors across our stack. Group them by service, show me the stack trace of the most recent one, and tell me which release introduced it if you can.

Eighty-four seconds later:

List recent critical Sentry errors across our stack
louis.fradin · May 11, 2026, 02:18 PM
List the most recent critical Sentry errors across our stack. Group them by service, show the stack trace of the most recent one, and tell me which release introduced it if you can.
May 11, 2026, 02:19 PM · Thought for 84 seconds

67 unresolved errors across four services, grouped:

api (Backend)
5 issues
API-B82Error validating payload
221 events · release v0.84.1 · 3 users impacted
API-AWSFailed AWS extraction
141 events
API-GCPFailed GCP extraction
47 events
API-S3S3 upload failure
33 events
API-CLUCluster migration failure
12 events
graph-connector
grouped
GRAPH-CONNECTOR-QW8Worker failed to process message
120 events · 5 sibling variants grouped (QWV, QWW, QWX, QWY, QWZ)
annie-intelligence
2 issues
ANNIE-INT-AIntegration connection failures at startup
23 events
ANNIE-INT-SUBSubagent variant
8 events
agent-gateway
2 issues
AGENT-GATEWAY-Ajson.MarshalerError · unexpected end of JSON input
55 events · culprit (*fanoutHandler).Handle
AGENT-GATEWAY-INTIntegration startup failures
18 events

Stack trace, most recent (AGENT-GATEWAY-A):

at (*fanoutHandler).Handle · agent-gateway/handler/fanout.go:142
at (*Server).serveHTTP · agent-gateway/server.go:88
at http.HandlerFunc.ServeHTTP · net/http/server.go:2122

Would you like me to:

  • · Dig into the agent-gateway MarshalerError to find which release introduced it?
  • · Pull the 5 sibling variants under graph-connector and confirm the common root cause?
  • · Open Linear tickets for the four hottest issues, one per service?
Your chats aren't used to train models.

The highlights.

api (Backend): five issues. The most active is API-B82, "Error validating payload," 221 events, last seen seconds before we hit submit, tagged release v0.84.1, three users impacted. Plus failed AWS extraction (141 events), failed GCP extraction, S3 upload failure, cluster migration failure.

graph-connector: GRAPH-CONNECTOR-QW8, "Worker failed to process message," 120 events. Annie grouped five sibling variants (QWV, QWW, QWX, QWY, QWZ) into the same finding rather than listing each as a separate one. They share a root cause; she said so without being asked.

annie-intelligence: integration connection failures at startup, 23 events. Plus a subagent variant.

agent-gateway: AGENT-GATEWAY-A, json.MarshalerError: unexpected end of JSON input, 55 events, culprit (*fanoutHandler).Handle. Plus integration startup failures, 18 events.

Then a detail card on the most recent issue, then three follow-up questions Annie suggested. The first:

Dig into the agent-gateway MarshalerError to find which release introduced it?

That was the next question we would have asked. We did.

What changed

The triage loop got shorter. An error is now one question away from a grouped, prioritized, release-attributed answer instead of five tabs deep. The (*fanoutHandler).Handle stack frame Annie surfaced in her opening answer is the same one we'd have found by clicking through the Sentry UI. We didn't have to click.

The bigger thing is what we didn't have to do. We didn't write a custom Sentry integration with the handful of API calls we thought we'd need. Annie has Sentry's full surface and stays current as Sentry ships. The next time Sentry adds a feature, Annie has it.

Five tabs became one question.

Setup: docs.anyshift.io/integration/sentry