diff --git a/docs/product/ai-in-sentry/index.mdx b/docs/product/ai-in-sentry/index.mdx index d9bfcffba48a0c..254b28091d62ba 100644 --- a/docs/product/ai-in-sentry/index.mdx +++ b/docs/product/ai-in-sentry/index.mdx @@ -20,7 +20,7 @@ Sentry leverages artificial intelligence (AI) and machine learning (ML) to enhan Use Seer to: -- **[Fix Issues](/product/ai-in-sentry/seer/autofix/)**: Use Autofix to find root causes and generate suggested code fixes for errors and performance issues, or hand off to a [coding agent](/product/ai-in-sentry/seer/autofix/#handoff-to-claude-code-or-cursor-cloud-agents). +- **[Fix Issues](/product/ai-in-sentry/seer/autofix/)**: Use Autofix to find root causes and generate suggested code fixes for errors and performance issues, or hand off to a [coding agent](/product/ai-in-sentry/seer/autofix/#handoff-to-coding-agents). - **[Investigate Problems](/product/ai-in-sentry/seer/#seer-agent)**: Ask Seer Agent questions about your application and Seer Agent will do the digging. Walk through complex production problems with Seer Agent reasoning through evidence in real time. - **[Review Code Changes](/product/ai-in-sentry/seer/code-review/)**: Have Seer review your code changes in GitHub or GitLab, catching bugs before merging. diff --git a/docs/product/ai-in-sentry/seer/autofix/index.mdx b/docs/product/ai-in-sentry/seer/autofix/index.mdx index 479254e914f6d9..72c383d998a96c 100644 --- a/docs/product/ai-in-sentry/seer/autofix/index.mdx +++ b/docs/product/ai-in-sentry/seer/autofix/index.mdx @@ -38,7 +38,7 @@ Seer's Issue Autofix flow follows a three step process: 1. [Root Cause Analysis](#root-cause-analysis): Analyze the issue using Sentry's context and your codebases and determine the root cause 2. [Solution Identification](#solution-identification): Identify a solution based on the analysis -3. [Code Generation](#code-generation): Generate a code fix and (optionally) open a PR, or hand off to a coding agent +3. [Code Generation](#code-generation): Generate a code fix and (optionally) open a PR, or [hand off to a coding agent](#handoff-to-coding-agents) You can always manually trigger the Autofix flow from the Issue Details page. @@ -106,16 +106,17 @@ snippets and examples, and does not affect workflows involving your own coding a ![Screenshot of Seer showing code it generated =800x](../img/coding-step.png) -### Handoff to Claude Code or Cursor Cloud Agents +### Handoff to Coding Agents Seer always performs root cause analysis and solution planning using its own internal tools and Sentry context. At the final code generation step, instead of having Seer generate the code fix directly, you can hand off to an external coding agent for implementation. Seer passes along the root cause and solution plan so the coding agent can act on them. This lets you leverage the strengths of specialized code generation tools while still benefiting from Seer's debugging and analysis. -When your codebase is connected via GitLab, Seer will open a merge request instead of a pull request. Coding agent handoff (Claude Code, Cursor) works the same way regardless of SCM provider. +Coding agent handoff only works with GitHub. Supported coding agents for handoff: -- **Claude Code** — Seer passes the root cause and solution as a structured prompt that Claude Code can act on directly in your terminal or CI environment. -- **Cursor Cloud Agents** — Seer triggers a Cursor Cloud Agent to implement the fix asynchronously, without requiring your local IDE to be open. +- **Claude Code** — Seer passes the root cause and solution as a structured prompt that [Claude Code](/integrations/coding-agents/claude/) can act on directly in your terminal or CI environment. +- **Cursor Cloud Agents** — Seer triggers a [Cursor Cloud Agent](/integrations/coding-agents/cursor/) to implement the fix asynchronously, without requiring your local IDE to be open. +- **GitHub Copilot** — Seer sends its root cause analysis to a [GitHub Copilot cloud agent](/integrations/coding-agents/copilot/), which runs in GitHub Actions to generate a fix and open a pull request. To enable coding agent handoff, connect a coding agent integration in [Integrations settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/integrations/?category=coding%20agent). Once connected, the handoff option will appear at the Code Generation step of the Autofix flow, alongside the standard "Create PR" and "Checkout locally" options. diff --git a/docs/product/ai-in-sentry/seer/index.mdx b/docs/product/ai-in-sentry/seer/index.mdx index 1c1fd42c347def..21f4246e8da8f9 100644 --- a/docs/product/ai-in-sentry/seer/index.mdx +++ b/docs/product/ai-in-sentry/seer/index.mdx @@ -59,7 +59,7 @@ You can prompt Seer to generate PRs, or merge requests on GitLab, to fix your is Seer always performs root cause analysis and solution planning using its own internal tools and Sentry context. At the final code generation step of Autofix, instead of having Seer generate the code fix directly, you can hand off to an external coding agent for implementation. -Supported coding agents for handoff are: Claude Code and Cursor Cloud Agents. Learn more about how to set up each coding agent [here](/integrations/coding-agents/). [Read more](/product/ai-in-sentry/seer/autofix/#handoff-to-claude-code-or-cursor-cloud-agents) about using them with Autofix. +Supported coding agents for handoff are: Claude Code, Cursor Cloud Agents, and GitHub Copilot. Learn more about how to set up each coding agent [here](/integrations/coding-agents/). [Read more](/product/ai-in-sentry/seer/autofix/#handoff-to-coding-agents) about using them with Autofix. ### Seer Agent