Connect Sentry to enable agents to:
- Analyze production errors as they occur
- Investigate stack traces and recent code changes
- Generate pull requests to resolve issues
- Create contextual GitHub issues
- Monitor error trends across releases
Official Workflow Templates
The following official workflow template is maintained by the Continue team and is available directly in the Mission Control Hub. This workflow is designed to work out of the box and represents the recommended way to automate Sentry-based remediation.Auto-fix Sentry Issues
Automatically analyze and fix production errors when Sentry detects new issues.
Advanced Use Cases
Advanced: Custom Sentry Workflow Ideas
Advanced: Custom Sentry Workflow Ideas
These examples are not officially maintained by the Continue team, but illustrate what’s possible with custom workflows.
- Trigger investigations only for high-impact or high-frequency errors
- Route specific error types to specialized agents
- Correlate Sentry issues with recent deploys or feature flags
- Generate weekly error trend summaries for engineering teams
- Combine Sentry signals with GitHub or analytics data
Access & Permissions
When connecting Sentry, you’ll authorize Continue to receive error events and access issue data.-
Project and issue access
Agents can access Sentry projects and issues you have permission to view within your organization. -
Permissions
Approved permissions allow Continue to analyze error events, read issue details, and create pull requests or GitHub issues on your behalf.
Connecting Sentry requires creating an internal integration in your Sentry organization.You’ll be asked for your organization slug and credentials that allow Continue to receive issue and event data via webhooks and API access.Full credential setup is handled in the Mission Control Hub.