diff --git a/docs/product/ai-in-sentry/seer/autofix/index.mdx b/docs/product/ai-in-sentry/seer/autofix/index.mdx index c8907b2fd95add..3dfe7378a4be47 100644 --- a/docs/product/ai-in-sentry/seer/autofix/index.mdx +++ b/docs/product/ai-in-sentry/seer/autofix/index.mdx @@ -111,7 +111,7 @@ snippets and examples, and does not affect workflows involving your own coding a After Seer opens a PR, it can update that same PR to address failing CI checks and your feedback. PR iteration is supported on GitHub only. -- **Automatic CI iteration:** When CI checks fail, Seer investigates the failures and attempts to fix them by pushing follow-up changes to the PR. Automated attempts are limited to prevent an endless loop; you can provide feedback to continue iterating. +- **Automatic CI iteration:** When **Auto-Iterate on PRs** is enabled and CI checks fail, Seer investigates the failures and attempts to fix them by pushing follow-up changes to the PR. Automated attempts are limited to prevent an endless loop; you can provide feedback to continue iterating. - **Feedback in Sentry:** Open the Autofix panel on the Issue Details page, enter instructions in the feedback field, and select **Submit**. For example, ask Seer to add a regression test or handle an edge case. - **Feedback on GitHub:** Add a PR comment starting with `@sentry`, such as `@sentry Add a regression test for this fix`. You need write access to the repository to trigger iteration through GitHub comments. - **Human and bot reviews:** Seer addresses feedback from both human reviewers and review bots, including review summaries and inline comments, without requiring an `@sentry` mention. Human reviewers need write access to the repository. Bot reviews must include inline comments. @@ -120,6 +120,24 @@ If Seer posts a comment requesting additional GitHub permissions, follow the lin During PR iteration, Seer does not respond to broader questions; it can only make changes to a PR. For broader questions, use [Seer Agent](/product/ai-in-sentry/seer/#seer-agent). +#### Enable or Disable Automatic PR Iteration + +Control automatic CI iteration for each project in [Seer Autofix settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/projects/): + +1. In Sentry, go to **Settings > Seer** and select **Autofix**. +2. Find your project in the table. Use **Search** to filter by project name. +3. Turn **Auto-Iterate on PRs** on or off in the project's row. The change saves automatically. + +The screenshots below show an earlier version of the UI, where **Auto-Iterate on PRs** was labeled **Iterate on PRs**. The current setting controls automatic CI iteration. + +![Seer Autofix project table with the PR iteration toggle highlighted =800x](../img/pr-iteration-project-toggle.png) + +When adding a project, select **Add Project**, configure the project and repository, set **Auto-Iterate on PRs**, and select **Save Project**. + +![Add Project to Autofix dialog with the PR iteration toggle highlighted =800x](../img/pr-iteration-add-project.png) + +Turning this setting off stops Seer from automatically pushing fixes in response to failing CI checks. It does not disable PR creation, and you can still ask Seer to iterate using feedback in Sentry or an `@sentry` comment on GitHub. + ### 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. @@ -172,7 +190,8 @@ Autofix's default behavior can be customized in several ways: 1. You can manually customize the repositories it has access to 2. You can set an override for the default branch in each repository -3. You can prevent Seer from creating PRs, or pushing them to your codebase for your organization (under **Advanced Settings** in [Seer settings - Enable Code Generation](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/advanced/#enableSeerCoding)) +3. You can [enable or disable automatic PR iteration](#enable-or-disable-automatic-pr-iteration) for each project +4. You can prevent Seer from creating PRs, or pushing them to your codebase for your organization (under **Advanced Settings** in [Seer settings - Enable Code Generation](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/advanced/#enableSeerCoding)) Seer already automatically parses rules files from [Cursor](https://docs.cursor.com/context/rules), [Windsurf](https://windsurf.com/editor/directory), [Cline](https://docs.cline.bot/features/cline-rules), and [Claude Code](https://docs.anthropic.com/en/docs/claude-code/tutorials#create-an-effective-claude-md-file) diff --git a/docs/product/ai-in-sentry/seer/img/pr-iteration-add-project.png b/docs/product/ai-in-sentry/seer/img/pr-iteration-add-project.png new file mode 100644 index 00000000000000..4bed897f6be155 Binary files /dev/null and b/docs/product/ai-in-sentry/seer/img/pr-iteration-add-project.png differ diff --git a/docs/product/ai-in-sentry/seer/img/pr-iteration-project-toggle.png b/docs/product/ai-in-sentry/seer/img/pr-iteration-project-toggle.png new file mode 100644 index 00000000000000..3c849af396417d Binary files /dev/null and b/docs/product/ai-in-sentry/seer/img/pr-iteration-project-toggle.png differ