The Better Stack plugin puts our AI SRE in Claude, with its skills and every Better Stack tool. It runs on your Claude subscription with the latest Claude models, and it's free on every Better Stack plan.
Once it's connected, ask Claude to:
Investigate an incident, find its root cause in your logs, metrics, traces, errors, and code, and open a pull request with the fix.
Explain why a service got slow or started failing, and what changed around that time.
Set up monitors, heartbeats, dashboards, and alerts for a new service, or post a status page update.
On the plugin's Connectors tab, connect Better Stack and sign in with your Better Stack account.
Start a new chat.
Using Claude Team or Enterprise?
An Owner adds the Better Stack connector in Organization settings β Connectors before members can connect it.
Fix errors on a schedule with Claude
Add a Claude scheduled task that checks your errors in Better Stack every 4 hours and fixes the obvious ones with pull requests. It runs in Anthropic's cloud, so you can close your laptop and merge the pull requests later from your phone.
Set up a cloud scheduled task that fixes new errors Better Stack catches in this repository's app. It has to run in Anthropic's cloud, so it keeps working while my computer is off.
- Name: Fix new Better Stack errors
- Schedule: every 4 hours
- Repository: this repository
- Connectors: only Better Stack
- Prompt for each run:
Fix the obvious new errors Better Stack caught in this repository's app.
1. With the Better Stack tools, list the unresolved errors of this repository's Better Stack error tracking application seen in the last 4 hours, most occurrences first.
2. Skip errors that already have an open pull request in this repository: look for the error's Better Stack link in the descriptions of open pull requests.
3. Pick at most 3 errors whose root cause is in this repository's code and that a small, safe change fixes. Skip errors caused by outages, configuration or third-party services, and any fix you aren't confident about.
4. Install the project's dependencies. For each error, start a new branch from the latest default branch, read the error's stack trace with the Better Stack tools, fix the root cause, add a test that fails without the fix, and run the tests.
5. Push each fix and open a pull request. In the description, link the Better Stack error and say what caused it and how you tested the fix.
6. End with one line per error you looked at: its pull request, or why you skipped it.
If you can use the Better Stack tools here, look up which error tracking application this repository belongs to and name it in the task's prompt. Otherwise ask me. Before you create the task, check that the Better Stack connector is connected to my Claude account. If it isn't, tell me to connect it at https://claude.com/connectors/betterstack.
Claude creates the task and gives you its link. To try it right away, ask Claude to run it now.
What will the task change?
It only opens pull requests, and each one links the Better Stack error it fixes. Nothing is merged until you review it. Errors that already have an open pull request are skipped, and so are outages and configuration problems.