Sentry’s Seer Agent lets you ask any questions about your data in Sentry, dive deep into that data, and fix issues faster.
One of its particularly cool abilities is letting you ask questions directly about what you’re looking at in Sentry. Questions like “What’s causing that latency spike?” or “What is the customer and region breakdown for this error?”
To answer these kinds of questions, the agent must see and understand what you are seeing inside Sentry at that moment. Getting that context right turns out to matter a lot: not just for answer quality, but for cost, conversation length, and the range of things the agent can eventually do on your behalf.
The straightforward approach: ASCII snapshots
Until recently, Seer understood the current page by taking what’s essentially a screenshot rendered in text by scraping the DOM elements. It captures a character-by-character ASCII grid of everything visible on screen. It’s crude, but it works. The agent can look at that grid and infer what’s on the page, the same way a person could squint at a pixelated image and recognize rough shapes.
