Investigate and fix issues with Seer Agent

Seer Agent is currently in beta and available to all users at no charge. To get started, just click the 'Ask Seer' button in your navigation bar.

The fastest way to your team access to the Sentry Agent though is to use the Slack integration. Using this, you can communicate with Seer Agent through direct messages, easily share issue and application diagnostics, and integrate the Seer agent into automated debugging workflows.

To enable Seer agent in Slack, go to Settings → Integrations → Slack and install/update the app.

Click Ask Seer on any page in Sentry to start a conversation. You don't need to pre-build a Discover query or pick the right explorer—describe what you're seeing in plain language.

Good first prompts look like:

• Error spike — "Why did checkout errors jump in the last hour?"
• Latency — "What's causing p95 on /api/orders to climb since the last release?"
• User impact — "Which issues are affecting enterprise customers today?"
• Correlation — "Are these frontend timeouts related to a backend span failure?"

Seer Agent connects the dots across everything you've sent to Sentry: issue context, traces and spans, logs, profiles, and linked code when your SCM integration is set up.

Use it for investigations you'd otherwise bounce between explorers for:

• Root-cause hunting — ask it to walk from a failing transaction to the span, log line, or stack frame that explains it
• Release diffs — ask what changed after a deploy when error rates or latency moved
• Cross-service debugging — ask whether a frontend symptom has a backend or dependency cause
• Follow-ups — keep the same thread going as Seer reasons through evidence in real time

Sometimes know who can help with an issue is just as important as knowing what exactly went wrong. You can use the Seer Agent to identify which of your teammates is best equipped to handle the fix based on previous commits. Seer agent will inspect the code history to find out when an issue started to emerge and then can assign the Sentry issue to that specific user.

Looking to keep track of who's handling what? Here's an example flow you could create:

• Create an Issue — Use the Linear integration to automatically open Linear issues
• Identify an issue owner - Have the Seer Agent in Slack look at commit histories and identify the right user
• Assign them to the issue — Use the Linear agent or use the new Sentry Agent for Linear to have Seer generate a fix for you

Once you know what the issue is and who the right person to assign the issue to is, it's time to fix it. Fortunately, it's never been easier to automate code fixes by using agents and the Seer agent works with a bunch of different agents.

• Seer Autofix - You can trigger the Seer autofix workflow directly from the Seer agent in Slack with a single click.
• Agent Automations - If you use tools like Claude routines or Cursor automations, you can instruct agents to interact with the Seer agent in Slack to gather information about an issues and your application.