After a release
Priya Sharma, engineering manager at Acme Ltd, asked whether errors rose after Tuesday's deployment. Memtro read the deployments and the hourly error counts, and listed the error groups first seen since that version.
Which errors are new since the last release, and how often are they happening?
Raygun shows you your applications and their error groups by status, with when each first and last occurred. It reads one group's recent occurrence times, error counts over time per application or group, and deployments with versions and commits. When asked and granted, it can resolve, reactivate, ignore or permanently ignore error groups, and comment on them. It can also record, edit or delete deployments, and invite people to the Raygun plan or revoke invitations. Occurrence details such as request data and affected users are not returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Raygun tool, reads what it needs, and answers with the source cited.
These tools change something in Raygun. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Raygun is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which errors are new since yesterday's deployment?
How many errors did the API record per hour today?
When did the checkout timeout error first appear?
What was deployed to the web app last week?
Resolve the null reference error in version 2.3.
Priya Sharma, engineering manager at Acme Ltd, asked whether errors rose after Tuesday's deployment. Memtro read the deployments and the hourly error counts, and listed the error groups first seen since that version.
Tom Reilly at Northwind asked Memtro to resolve the checkout timeout error in the version he had shipped. With the action granted, Memtro marked it resolved in that version, so it reactivates if it recurs later.
The teams that lean on Raygun most, a question each of them asks, and what they connect beside it.
A record in Raygun is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Raygun open My settings, then Personal Access Tokens, and create a token for one plan with an expiry. Tick the read scopes, plus the write scopes only for the actions you want.
In Memtro open Connections → Raygun and paste the Personal Access Token.
The token sees only the applications its user can. An administrator grants the error group, deployment and invitation actions by name.
Ask: which errors are new since yesterday's deployment?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Raygun tools are the same everywhere.
Only when you ask, and only what it has been granted: resolve an error group in a version; reactivate an error group; ignore an error group; permanently ignore an error group, optionally discarding new occurrences; comment on an error group; record a deployment; edit a deployment; delete a deployment; invite someone to the Raygun plan by email; revoke a pending invitation. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Personal Access Token. In Raygun open My settings, then Personal Access Tokens, and create a token for one plan with an expiry. Tick the read scopes, plus the write scopes only for the actions you want.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time