Skip to main content
Stop context-switching between your IDE and Sentry. When agents connect to Sentry, they can view errors, analyze stack traces, and pull in monitoring context to help debug issues faster.

​
What agents can do with Sentry

Once connected, agents can:
  • View issues: Browse and search Sentry issues, including error messages, frequency, and affected users.
  • Analyze stack traces: Read stack traces and correlate errors with your codebase to identify root causes.
  • Search events: Find specific errors, filter by release or environment, and track regressions.
  • Add context: Reference Sentry issues in conversations and link errors to code changes.

​
Example workflows

"Show me the most frequent unresolved Sentry issues in production"

"What's the stack trace for issue SENTRY-1234?"

"Find any Sentry errors related to the payment processing module"

"Were there any new errors after the last deployment?"

​
Connect Sentry

​
Step 1: Organization setup

An admin needs to enable Sentry for your organization first.
  1. Go to Organization Settings > Integrations
  2. Find Sentry and click Enable
  3. Configure default project settings if needed
Organization integration settings

​
Step 2: Authenticate your account

Once enabled, connect your personal Sentry account:
  1. Go to User Settings > Integrations
  2. Click Connect next to Sentry
  3. Authorize Ona to access your Sentry organization
  4. Select which projects to connect
User authentication for Sentry

​
Verify it works

Start a conversation with an agent and try: 
Show me recent Sentry issues in production
If you see your issues, you’re connected. If not, verify both organization enablement and your personal authentication are complete.

​
Tips for effective use

Be specific about projects: If you have multiple Sentry projects, specify which one: “Show me errors in the api-server project.” Include environment context: Mention the environment when searching: “Find production errors from the last 24 hours.” Use with AGENTS.md: Add your Sentry project names and conventions to AGENTS.md so agents know your project structure and alerting conventions.

​
Troubleshooting

​
Cannot access a specific project

Ensure you authorized access to the correct organization and projects during the OAuth flow. You can disconnect and reconnect to update your project selection.

​
Next steps