After the release
The morning after a release the engineering lead asks what broke. Memtro reads the latest release and lists the three errors it introduced, the busiest affecting 214 users, with the stack frame where each one starts.
BugSnag + Memtro
Ask BugSnag which errors appeared since the last release, and how many users they hit.
Connect BugSnag with your API host and a personal Auth Token and Memtro reads the projects you can see with their open error counts, errors by users affected or events, an error's recent events with app version and first in-project stack frame, comments and releases. Event user data and request data are never read. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can comment as you, fix, ignore, snooze, assign or relink errors, discard future events, and permanently delete an error or a comment.
In Memtro
What you can do with BugSnag in Memtro
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right BugSnag tool, reads what it needs, and answers with the source cited.
What it does
- 01Projects with type, language, release stages and how many errors are open or for review
- 02Errors sorted by last seen, first seen, users affected or events, with class, message, severity and status
- 03One error's recent events: when, app version and stage, handled or not, and the first in-project stack frame
- 04Comments on an error and releases newest first with version, stage, errors introduced and unhandled sessions
- 05When asked and granted, comments as you, and fixes, reopens, ignores, snoozes, assigns or changes the severity of up to 25 named errors, or links or creates an issue in your tracker
- 06When asked and granted, discards an error's future events for good, and permanently deletes an error with its events or a comment
Acts when asked
When you ask it to
These tools change something in BugSnag. 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.
- 01Add a comment to an error, written as the token's user
- 02Fix, reopen, ignore or snooze an error
- 03Assign an error to a person or team, or unassign it
- 04Change an error's severity
- 05Link an error to an external issue, unlink it, or create one in the configured tracker
- 06Apply one of those changes to up to 25 named errors
- 07Discard future events for an error
- 08Permanently delete an error and its events
- 09Edit a comment written as the token's user
- 10Permanently delete a comment
In practice
Ask it like you would a colleague
Once BugSnag 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.
BugSnag + Memtro
What new errors appeared since the last release?
Which errors affected the most users this week?
Show me the recent events for the checkout timeout error
Mark the login crash as fixed and assign the payment webhook error to Priya
Add a comment to the login crash saying the fix ships in 4.12
Closing out a fix
Priya Sharma asks Memtro to close the Brightwave Ltd import error now that 4.12 is out. Memtro adds her approved comment as her and marks the error fixed, so BugSnag reopens it if it happens again, and collaborators may be notified of the comment.
Teams
Where it fits
The teams that lean on BugSnag most, a question each of them asks, and what they connect beside it.
- EngineeringKeep decisions from evaporatingEngineer, Tech lead, On call, New joiner“Who owns the billing migration, and what did we decide about retries?”Used alongside GitHub, Linear, Jira, Confluence, Slack and 5 more.
- ProductHear what customers actually ask forProduct manager, Researcher, Designer, Head of product“Which customers asked for SSO this quarter, and what is their combined ARR?”Used alongside Help Scout, HubSpot, Linear, Jira, Slack and 6 more.
- Agent buildersMemory and tools for the agents you buildSolo builder, Platform team, Automation engineer, Whoever signs it off“Search memtro for what we know about Acme before drafting the proposal”Used alongside GitHub, Linear and Slack.
Better together
Works with
A record in BugSnag 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.
- Work managementBugSnag with JiraJQL search, issue details and projects from Jira Cloud.
- Work managementBugSnag with Clio ManageAsk the matter: its client, its fee earner, the time on it and what is still unbilled.
- Work managementBugSnag with LinearIssues, projects and teams, synced hourly into memory.
- SupportBugSnag with Help ScoutAI that reads your support conversations and cross-references the customer everywhere else.
- SupportBugSnag with ZendeskEvery ticket, reply and internal note, ready to be asked about.
- SupportBugSnag with IntercomCustomer conversations and the people behind them, in your company memory.
- Documents and wikisBugSnag with NotionSearch pages and query databases, and write to them when you ask.
- Documents and wikisBugSnag with Google DriveSearch Drive and read Docs, Sheets and Slides as text, and write a Doc when you ask.
- Documents and wikisBugSnag with ConfluenceSearch and read wiki pages, and write them when you ask.
Also in Engineering and operations
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
- GitHub
- AWS CloudWatch
- Sentry
- ServiceNow
- Okta
- Twilio
- AWS CloudTrail
- GitLab
- Bitbucket
- Vercel
- PagerDuty
- Datadog
- Grafana
- incident.io
- Azure DevOps
- CircleCI
- Cloudflare
- LaunchDarkly
- New Relic
- Rollbar
- Snyk
- Better Stack
- Buildkite
- DigitalOcean
- Heroku
- Netlify
- SonarQube Cloud
- Statuspage
UptimeRobot- Axiom
- Checkly
- Hetzner Cloud
Honeycomb- Pingdom
- Render
- Statsig
- Sumo Logic
- Supabase
- HCP Terraform
- Vultr
- Airbrake
- Codecov
Cronitor- Dynatrace
FireHydrant- Fly.io
- Honeybadger
- Akamai Linode
- Octopus Deploy
- Pulumi
- Rootly
- Semgrep
- Splunk
StatusCake- Tailscale
- Argo CD
- authentik
- Coolify
- Gitea
GlitchTip
GLPI- Jenkins
Langfuse
LibreNMS- n8n
NetBox- Portainer
- Prefect
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone- OpenAI (usage and cost)
- Anthropic (usage and cost)
- Algolia
- Flagsmith
- Unleash
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert- KnowBe4
JumpCloud
ConfigCat- Railway
- Fastly
- Postman
- Make
- Braintrust
- OpenRouter
- ElevenLabs
Split- Scaleway
Aikido Security- AssemblyAI
Astronomer- Bamboo
- Baseten
- Bitrise
- Bitwarden
- BrowserStack
- bunny.net
- Cachet
- Checkmk
- Civo
- Cloudsmith
- Codacy
- Codemagic
Comet Opik- Coralogix
CrowdStrike Falcon- Dagster+
- DeepSource
Detectify- Docker Hub
Domotz- Grafana OnCall
- Harness
- Hugging Face
- Instatus
- Koyeb
- Lambda Cloud
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary- Mezmo
NinjaOne- Nomad
Northflank- Oh Dear
- OVHcloud
Portkey- Probely (Snyk API & Web)
PromptLayer- Proxmox VE
PRTG Network Monitor- Qase
Raygun
Retell AI- Retool
Runpod- SecurityScorecard
- Semaphore CI
Shodan- SigNoz
- Socket
Spike.sh
Squadcast- SwaggerHub
- TeamCity
Tenable- Together AI
- Travis CI
UpGuard
Uptime.com
Vanta- Vapi
- Windmill
Zenduty- OpsLevel
Cortex- Auth0
- Clerk
WorkOS
Kandji
Automox
Huntress- HackerOne
SimpleMDM- AppSignal
Healthchecks.io
Rapid7 InsightVM- 1Password Events
- JFrog Artifactory
- Sauce Labs
Zenhub- Deepgram
- Replicate
Setup
How to connect
Connect withAPI host and Personal Auth Token
- 1
In BugSnag open your own user settings, not the project's, and create a Personal Auth Token. A project or organisation API key will not work
- 2
The token acts as you: Memtro sees the organisations and projects you can, and anything it changes or comments is done as you
- 3
In Memtro open Connections → BugSnag, set API host to api.bugsnag.com if you sign in at app.bugsnag.com, or api.bugsnag.smartbear.com if at app.bugsnag.smartbear.com, paste the Personal Auth Token and connect
- 4
Ask what new errors appeared since the last release
Also works from
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The BugSnag tools are the same everywhere.
FAQ
Questions
Can Memtro change anything in BugSnag?+
Only when you ask, and only what it has been granted: add a comment to an error, written as the token's user; fix, reopen, ignore or snooze an error; assign an error to a person or team, or unassign it; change an error's severity; link an error to an external issue, unlink it, or create one in the configured tracker; apply one of those changes to up to 25 named errors; discard future events for an error; permanently delete an error and its events; edit a comment written as the token's user; permanently delete a comment. 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.
Who can use a BugSnag connection?+
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.
Does Memtro store my BugSnag data?+
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.
How do I connect BugSnag?+
API host and Personal Auth Token. In BugSnag open your own user settings, not the project's, and create a Personal Auth Token. A project or organisation API key will not work.
Connect BugSnag in a few minutes
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.