diff --git a/docs/product/ai-in-sentry/index.mdx b/docs/product/ai-in-sentry/index.mdx index 786beea278ac0..be8c5a3d9d6da 100644 --- a/docs/product/ai-in-sentry/index.mdx +++ b/docs/product/ai-in-sentry/index.mdx @@ -40,4 +40,6 @@ You can get more details at [AI Privacy and Security](/product/ai-in-sentry/ai-p ## Disabling Generative AI Features -If you don't find Seer and other generative AI features useful and want to disable them for all users, you can do so in your organization's settings with the ["Show Generative AI Features" toggle](https://sentry.io/orgredirect/organizations/:orgslug/settings/#hideAiFeatures). +- If you want all generative AI features to be disabled for all users in your organization, you can do so in your organization's settings with the ["Show Generative AI Features" toggle](https://sentry.io/orgredirect/organizations/:orgslug/settings/#hideAiFeatures). + +- To disable specific AI settings, go to [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/#enableSeerCoding). For organizations that need to prevent code generation, or adding additional context in Alerts, you can find these configurations under **Advanced Settings** in Seer settings. \ No newline at end of file diff --git a/docs/product/ai-in-sentry/seer/root-cause-analysis/index.mdx b/docs/product/ai-in-sentry/seer/root-cause-analysis/index.mdx index 3efdec547396c..69b33bf1b130e 100644 --- a/docs/product/ai-in-sentry/seer/root-cause-analysis/index.mdx +++ b/docs/product/ai-in-sentry/seer/root-cause-analysis/index.mdx @@ -46,6 +46,10 @@ During the coding step, Seer will identify the code patch (or patches) needed to From here, you can choose to draft a PR, or checkout the code changes locally for further iteration. If you choose to checkout the code locally, Seer will make a new branch for you. + +You can disable code generation for your organization under **Advanced Settings** in [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/#enableSeerCoding). + + ![Screenshot of Seer showing code it generated =800x](../img/coding-step.png) ## What Root Cause Analysis Uses @@ -66,8 +70,9 @@ This context is crucial to Seer's capabilities, and it allows it to do things li Root Cause Analysis's default behavior can be customized in several ways: 1. You can manually customize the repositories it has access to -2. You can define the default branch it should use in each repository -3. You can set an override for the default branch in each repository +2. You can set an override for the default branch in each repository +3. You can add any additional custom context that may be useful within the scope of each individual repository +4. You can disable code generation for your organization (under **Advanced Settings** in [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/#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)