Skip to main content

​
What Charlie can do

Charlie doesn’t just listen for Sentry webhooks—he actively digs into any Sentry trace he sees in Linear, GitHub, or Slack:
  • Inspect any Sentry trace in context. Mention @Charlie on a Linear issue, GitHub issue/PR, or Slack message with a Sentry link and he fetches the stack trace, culprit commits, and frequency data.
  • Enrich the bug report automatically. Charlie attaches that Sentry context back to the Linear ticket so the whole story sits in one place.
  • Generate a fix plan. @Charlie, draft a fix plan outlines code edits, tests, and rollout steps ready for review.
  • Open a PR and ship the patch. Approve the plan or say @Charlie, open the PR and he spins up a branch, commits the fix, and opens a PR linked to both Linear and Sentry.

​
Quick Setup

Follow these steps to connect your Sentry organization with Charlie:
1

Navigate to Integrations

Go to dash.charlielabs.ai and sign in. Select your organization, then open Integrations.sentry-dashboard
2

Enter your Sentry details

In the Sentry integration form, enter the following values:
  1. Organization slug: Enter the slug for the Sentry organization Charlie should connect.
  2. Sentry User Auth Token: Paste the actual Sentry User Auth Token with at least Read permissions. The dashboard labels this field Token reference, but it sends the value as the token itself; do not enter a secret name or reference. This value is hidden while you type.
  3. Connect Sentry: Click Connect Sentry to validate the token and connect the selected Sentry organization.
Get a Sentry User Auth Token from https://sentry.io/settings/account/api/auth-tokens if you do not already have one. Paste that token itself into the field, despite its Token reference label. The v2 dashboard validates the token against the organization slug in this form; it does not use a separate organization dropdown or Save step.
Your Sentry organization is connected when the dashboard confirms that Sentry was connected.

​
Troubleshooting

If you encounter issues during setup:
  • Token validation fails: Ensure your token is valid and has at least Read permissions
  • The organization is not visible for this token: Verify the organization slug and that the token can access that Sentry organization
  • Connection issues: Check that your Sentry organization is accessible