Module 06 · Integrations
Sentry
Coming soon
Let the Coder list unresolved errors and read one issue in detail. Coming soon: it is read only, so nothing in Sentry changes.
On this page
Sentry catches the errors your app throws. Connect it and the Coder can list what is unresolved, then read one issue with where it happened, how often, and how many people it hit. That turns "something is broken" into a place to start.
At a glance#
| Category | Errors and support |
| Status | Coming soon |
| Used by | Coder, Product owner (only the Coder is available now) |
What assistants can do#
| Ability | How it runs |
|---|---|
| List unresolved errors | Reads on its own |
| Read one issue in detail | Reads on its own |
Setup (when it opens)#
- In Sentry, open your user settings, then personal tokens, and create a token with the permissions listed below.
- Open Integrations and pick Sentry.
- Paste the token and press Connect.
- If your token can see several organisations, tell the Coder which one to use.
Permissions#
In plain words, the token needs to:
- Read the organisation.
- Read its projects.
- Read events and issues.
An organisation-level token cannot read issues, so use a personal token or an internal integration token instead.
Good to know#
- Nothing in Sentry is resolved, assigned, ignored, or deleted. It is strictly read only, so nothing here waits for an Approve.
- Ask for an issue by its short id, for example "WEB-1A3".
- Sentry details can go into a ticket in PostHog when both are connected.
- Your token stays with your StellarFirm workspace and is never shown back to you. The page shows only that it is connected.
Prompts#
PromptWhat is hurting most Coder, list the unresolved Sentry issues from the last two weeks and tell me which one hits the most people.
PromptDig into one issue Coder, read Sentry issue [short id], explain where it happens, and propose the smallest fix. Do not change any code yet.
PromptFix an error Coder, fix Sentry issue [short id] and open a pull request for review once I Approve.