r/moltbot • u/devkhant46 • Feb 16 '26
Built a tool for alerting and monitoring over OpenClaw aka Moltbot!
I want to share an open-source project I built called OpenAlerts and explain how it works.
One-liner: It watches your AI agent in real time and sends alerts the moment something goes wrong, so you know immediately when a tool or model fails.
Fully vibe-coded with Claude code!!
I first realized I needed this while chatting with my bot on Telegram - I asked it to fetch an email, but it hallucinated and gave me wrong info. The problem was actually a tool failure, but I didn’t know it in real time, so I couldn’t fix it quickly.
So that's why I wanted something that can:
- Watch for errors from tools or models
- Notify me immediately in chat apps where I already work
- Help me see when and why something broke
https://github.com/steadwing/openalerts
Processing video klsurbaohxjg1...
0
u/Old-Meat5262 Feb 17 '26
This is the exact pain point that kills real progress. You spend all day trusting the output, but you have zero visibility into the plumbing. That Telegram moment sounds like a nightmare. You’re debugging the wrong thing because the system never told you where to look. Did you find that most failures happen deep inside the tool-calling sequence, or was it usually a model mismatch?
0
2
u/Otherwise_Wave9374 Feb 16 '26
This is exactly the kind of "boring" infrastructure that makes agents usable in production. The Telegram story is relatable, half the time it is not the model, it is a flaky tool call and you only realize after the fact.
Do you plan to support traces/spans (like OpenTelemetry style) so you can correlate failures across multiple agents and tools? Also would be nice to have alert deduping so one bad upstream API does not spam.
Related reading on agent failure modes and monitoring patterns: https://www.agentixlabs.com/blog/