> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sentry

> Connect Sentry to CloudThinker for error triage, issue search, trace inspection, and release investigation across your projects

Connect your Sentry organization to let CloudThinker agents search issues, events, and traces, review projects and teams, and pull root-cause signals during incident response and release triage.

Sentry uses **OAuth**, so you do not need to create a Sentry token or paste credentials into CloudThinker. Agents only read your error data — investigation leaves it unchanged.

## Prerequisites

* A **Sentry account** with access to the organization you want CloudThinker to investigate.
* Permission to authorize CloudThinker through Sentry's OAuth flow.

## Setup

<Steps>
  <Step title="Open CloudThinker">
    Navigate to **Connections → Sentry** in your CloudThinker workspace.
  </Step>

  <Step title="Start the OAuth flow">
    Click **Connect** to open Sentry's authorization page.
  </Step>

  <Step title="Authorize CloudThinker">
    Sign in to the Sentry account that can access the organization you want agents to investigate, then approve access.
  </Step>

  <Step title="Return to CloudThinker">
    After authorization, CloudThinker stores the OAuth tokens and shows a **Connected** status.
  </Step>
</Steps>

## Connection details

Sentry uses OAuth — there are no connection fields to enter manually.

| Field            | Description                                                         |
| ---------------- | ------------------------------------------------------------------- |
| **OAuth tokens** | Issued by Sentry and stored automatically; no manual entry required |

## Required permissions

CloudThinker inherits the Sentry access granted during OAuth — agents see the organizations and projects the authorizing account can see.

<Tip>
  Authorize with an account scoped to the organization you want investigated. Agents read issues, events, and traces; they do not change your Sentry data.
</Tip>

## Agent capabilities

Once connected, agents can:

| Capability                     | Description                                                                     |
| ------------------------------ | ------------------------------------------------------------------------------- |
| **Issue search**               | Search and inspect issues across projects, ranked by what matters most          |
| **Event and trace inspection** | Read individual events and distributed traces behind an issue                   |
| **Root-cause signals**         | Pull the evidence Sentry attaches to an issue — stack traces, tags, and context |
| **Project and team review**    | List projects and teams to scope an investigation                               |
| **Release triage**             | Correlate new errors with recent releases                                       |

### Verify the connection

```text theme={null}
@alex list my Sentry projects and summarize the top unresolved issues
```

### Example prompts

```text theme={null}
@alex #report which of the highest-impact Sentry issues in the payments project need attention first
@alex #report new Sentry errors since the last release, ranked by affected users
@alex #recommend where to look next based on the trace behind the checkout timeout issue
```

## Troubleshooting

<Accordion title="OAuth flow does not complete">
  Your browser may be signed in to the wrong Sentry account, or not signed in at all. Sign in to the intended Sentry account and retry the connection flow from **Connections → Sentry**.
</Accordion>

<Accordion title="Agent cannot find expected projects">
  The OAuth flow was completed with an account that lacks access to those projects. Reconnect using a Sentry account that belongs to the right organization and teams.
</Accordion>

<Accordion title="Connection worked, then stopped">
  The authorization may have been revoked in Sentry. Remove the connection in CloudThinker and run the OAuth flow again.
</Accordion>

## Security

* **Least privilege** — grant only the permissions the agents need for your use case; start read-only and widen later.
* **Read-only by default** — use read-only credentials unless you want agents to make changes through this connection.
* **Rotate credentials** — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
* **Revoke on offboarding** — remove the credential at the provider when you delete a connection or a teammate leaves.

- **Read-focused investigation** — agents search and read error data; your Sentry issues and events stay unchanged.
- **Scope by account** — the connection sees exactly what the authorizing Sentry account sees, so authorize with an appropriately scoped account.

## Related

<CardGroup cols={2}>
  <Card title="Rollbar Connection" icon="https://mintcdn.com/cloudthinker/nVesu4UXaGtxkRRZ/images/icons/rollbar.svg?fit=max&auto=format&n=nVesu4UXaGtxkRRZ&q=85&s=f20a4604702abafd89e705b2b40dd027" href="/guide/connections/rollbar" width="24" height="24" data-path="images/icons/rollbar.svg">
    Error tracking and deployment correlation
  </Card>

  <Card title="Datadog Connection" icon="https://mintcdn.com/cloudthinker/aLd-ttc-SCW-aFky/images/icons/datadog.svg?fit=max&auto=format&n=aLd-ttc-SCW-aFky&q=85&s=e8382167f2a1eb1e00971b5f4d703d48" href="/guide/connections/datadog" width="24" height="24" data-path="images/icons/datadog.svg">
    Log search, metrics, and monitoring
  </Card>
</CardGroup>