Ask what new errors appeared since the last deploy, and which jobs missed a check-in.
Connect Honeybadger with your personal auth token and Memtro reads projects, errors with their class, message, environment, assignee and counts, recent occurrences with the request path and top backtrace frames, deploys, check-ins and uptime checks with their outages. Request parameters, sessions and cookies are never returned. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted the action by name, it can comment on, resolve, reopen, ignore, assign or pause errors, create and change check-ins, and permanently delete an error or comment, all done as you.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Honeybadger tool, reads what it needs, and answers with the source cited.
These tools change something in Honeybadger. 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.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Honeybadger, choosing the same kinds; the tab shows Honeybadger's own steps. Each event can start a job, with the event as its input. Honeybadger sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Honeybadger 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.
What new errors appeared since the last deploy?
How many open production errors does the Acme API have?
Did the nightly invoice job check in last night?
Add a comment to the billing NoMethodError saying Priya is looking at it
Resolve the Northwind import error on the next deploy
After the Thursday release, the engineering lead asks what has broken. Memtro lines up the deploy at 16:40 with two errors first seen minutes later, both in production, and shows the request path and top backtrace frames of the latest occurrences.
Priya Sharma asks Memtro to note on the Northwind import error that the fix is in review and to resolve it on the next deploy. Memtro adds the comment as her and marks the error to resolve itself when the project next deploys, and if it happens again Honeybadger reopens it and alerts the channels.
The teams that lean on Honeybadger most, a question each of them asks, and what they connect beside it.
A record in Honeybadger 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.
UptimeRobot
Honeycomb
Cronitor
FireHydrant
StatusCake
GlitchTip
GLPI
Langfuse
LibreNMS
NetBox
Snipe-IT
Woodpecker CI
Zabbix
LangSmith
Helicone
GrowthBook
Drata
Intruder
GitGuardian
Secureframe
ilert
JumpCloud
ConfigCat
Split
Aikido Security
Astronomer
Comet Opik
CrowdStrike Falcon
Detectify
Domotz
LambdaTest
LangWatch
LlamaCloud
Logz.io
Lunary
NinjaOne
Northflank
Portkey
PromptLayer
PRTG Network Monitor
Raygun
Retell AI
Runpod
Shodan
Spike.sh
Squadcast
Tenable
UpGuard
Uptime.com
Vanta
Zenduty
Cortex
WorkOS
Kandji
Automox
Huntress
SimpleMDM
Healthchecks.io
Rapid7 InsightVM
ZenhubIn Honeybadger open your avatar → Profile → Authentication Token and copy it. The token has your access, and anything Memtro changes is done as you, so a dedicated user with only the right projects is safest
In Memtro open Connections → Honeybadger, paste the Personal auth token, set Region to us for app.honeybadger.io or eu for eu-app.honeybadger.io, and connect
Honeybadger allows 360 API requests an hour per token, shared by everything that uses it
Ask what new errors appeared since the last deploy
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Honeybadger tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to an error (fault) in a Honeybadger project; resolve an error now or on the next deploy, or reopen it; ignore an error, or stop ignoring it; assign an error to a project member; pause an error's notifications for a time or a number of occurrences; unpause an error's notifications; delete an error (permanent); delete a comment on an error (permanent); create a check-in (the project's alert channels are notified when it goes missing); change a check-in's name, slug or schedule. 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 auth token. In Honeybadger open your avatar → Profile → Authentication Token and copy it. The token has your access, and anything Memtro changes is done as you, so a dedicated user with only the right projects is safest.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Honeybadger, choosing the same kinds; the tab shows Honeybadger's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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
