diff --git a/docs/mission-control/integrations/sentry.mdx b/docs/mission-control/integrations/sentry.mdx
index 2b5f0ec6b79..a02df609826 100644
--- a/docs/mission-control/integrations/sentry.mdx
+++ b/docs/mission-control/integrations/sentry.mdx
@@ -67,122 +67,6 @@ Connect Sentry to Continue Mission Control to enable agents to automatically det
-## Use Cases
-
-### Automatic Error Resolution
-
-Create agents that fix errors as they occur:
-
-
-
- **Task Example**: "Monitor new Sentry errors and create PRs with fixes for straightforward issues"
-
- **What the Agent Does**:
- - Receives notifications when new errors occur
- - Analyzes the stack trace and error context
- - Identifies the root cause in your codebase
- - Generates a fix and creates a pull request
- - Links the PR back to the Sentry issue
-
- **Run in Mission Control**: Set up as an automation triggered by Sentry webhooks
-
-
-
-### Error Pattern Analysis
-
-Identify and resolve systemic issues:
-
-
-
- **Task Example**: "Analyze error patterns from the last 7 days and identify common root causes"
-
- **What the Agent Does**:
- - Groups similar errors together
- - Identifies patterns in stack traces and user actions
- - Determines if errors are related to specific releases or features
- - Creates comprehensive reports with recommendations
- - Opens issues for systemic problems requiring architectural changes
-
- **Run in Mission Control**: Schedule to run weekly or after major releases
-
-
-
-### Priority Triage
-
-Automatically prioritize critical errors:
-
-
-
- **Task Example**: "Triage new Sentry issues by impact, assign severity levels, and notify the appropriate team"
-
- **What the Agent Does**:
- - Evaluates error frequency and user impact
- - Assigns priority levels (critical, high, medium, low)
- - Tags errors by component and team
- - Creates GitHub issues for high-priority errors
- - Notifies relevant team members
-
- **Run in Mission Control**: Create as an automation triggered on new Sentry issues
-
-
-
-### Release Quality Monitoring
-
-Track error rates across deployments:
-
-
-
- **Task Example**: "Compare error rates before and after the latest release and flag any regressions"
-
- **What the Agent Does**:
- - Compares error metrics between releases
- - Identifies new errors introduced in the latest release
- - Calculates error rate changes by percentage
- - Generates release quality reports
- - Creates rollback recommendations if error rates spike
-
- **Run in Mission Control**: Trigger after each deployment or on a schedule
-
-
-
-### Performance Issue Detection
-
-Monitor and resolve performance degradation:
-
-
-
- **Task Example**: "Identify performance regressions from Sentry performance monitoring and suggest optimizations"
-
- **What the Agent Does**:
- - Analyzes transaction duration trends
- - Identifies slow database queries or API calls
- - Detects N+1 query problems
- - Suggests code optimizations
- - Creates PRs with performance improvements
-
- **Run in Mission Control**: Schedule daily or trigger on performance alerts
-
-
-
-### User Impact Analysis
-
-Understand how errors affect your users:
-
-
-
- **Task Example**: "Generate a report on which users are most affected by current errors and prioritize fixes accordingly"
-
- **What the Agent Does**:
- - Identifies users experiencing multiple errors
- - Analyzes error distribution across user segments
- - Correlates errors with user churn or frustration signals
- - Creates prioritized fix lists based on user impact
- - Generates customer communication templates
-
- **Run in Mission Control**: Run weekly or before customer check-ins
-
-
-
## Running Sentry Agents in Mission Control
You can run Sentry-connected agents in two ways:
@@ -249,10 +133,10 @@ Combine Sentry with GitHub integration for a complete workflow:
Track your agent's error resolution performance:
-1. **View in Inbox**: Navigate to the [Sentry view](https://hub.continue.dev/inbox?view=sentry) to see all Sentry-related agent activity
-2. **Check Sentry Dashboard**: Verify that issues are being resolved in your Sentry account
-3. **Review PRs**: Ensure quality of generated fixes in GitHub
-4. **Monitor Metrics**: Track mean time to resolution (MTTR) and intervention rates
+1. **View in Mission Control**: See all agent runs and their outcomes
+2. **Check Sentry**: Verify that issues are being resolved
+3. **Review PRs**: Ensure quality of generated fixes
+4. **Monitor Metrics**: Track resolution time and success rate
## Troubleshooting