Telebugs Error Tracking

Telebugs 1.14.4 released.

Improved the error report view in @TelebugsHQ. This was long overdue. Nested errors (the actual cause) now live inside the backtrace: ✅ grouped together ✅ full stack trace (wasn’t available before) As a side effect: ✅ fewer queries across Reports & Notes ✅ fully cached

Telebugs 1.14.3 released.

Telebugs 1.14.2 released.

📣 The next version of @TelebugsHQ will support displaying local variables for each stack frame (when available).

Self-hosted, minimal complexity, maximum signal for AI dev agents. More tools should aim here.

"Telebugs never misses anything, the web UI is delightfully efficient and the whole setup took less than an hour from purchase to production." Just published this heartfelt testimonial for @TelebugsHQ 🥹

"After more than 10 years running production systems, I’ve tried countless error tracking tools. Telebugs is the first one that finally feels like a sensible self-hosted solution without unnecessary complexity." This @TelebugsHQ testimonial makes me so proud 🥹

Telebugs 1.14.1 released.

“We switched from Sentry… Being in control of our data and removing a US company from our GDPR subprocessor list was critical.” Just got this testimonial for @TelebugsHQ. Telebugs is a great fit if you want full control over your error tracking, without relying on big corporations 😎

“Tested Sentry and GlitchTip… then stumbled upon Telebugs by chance - and it paid off!” Just got this testimonial for @TelebugsHQ and it made my day 😊 I’m not building it for everyone. I’m building it for teams that want real simplicity, self-hosted maintainability, and zero overcomplicated setups. That’s the whole point.

Claude can now investigate your @TelebugsHQ errors automatically! ✅ Fetch error reports ✅ Spot patterns ✅ Run root cause analysis ✅ Create tickets in your tracker A power user just built unofficial Claude Code skills for it. Huge shoutout to @BohdanZhuravel! Link below 👇

“It’s fast, simple to use, and does exactly what you need without overcomplicating things.” Just got this testimonial for @TelebugsHQ and it made my day 😊 I’m not building it for everyone. I’m building it for the ones who value simplicity and speed. That’s the whole point.

Telebugs 1.14.0 is live! Big usability wins: ✅ Extended filters: last 3/7/28/91 days ✅ Automatic sensitive data scrubbing (passwords, tokens, credit cards) ✅ Sparklines next to every error group ✅ “Notify on every occurrence” rule ✅ Dual timezone timestamps ✅ Auto-refresh checkbox 👇👇👇

Full changelog: #1.14.0" target="_blank" rel="nofollow noopener">telebugs.com/changelog#1.14…

Telebugs 1.14.0 released.

Filtering sensitive information in @TelebugsHQ. The upcoming update will automatically scrub passwords, tokens, API keys, credit cards, and other secrets from error reports (server-side, before they ever hit your database).

I'm really close to shipping a new @TelebugsHQ version. There are just a few more bugs to iron out before it is ready. The upcoming version will get a lot of bug fixes, more polish and beautiful sparklines per group 😍

Exciting update for @TelebugsHQ users! A community member has built an unofficial MCP server (telebugs-mcp) that lets AI agents query and retrieve error reports from your Telebugs instance. Super useful for AI-powered debugging. Give it a try! 👇

🚨 PSA for all @TelebugsHQ users If you installed Telebugs using the default installer, manually truncate your Docker logs. Due to an oversight, the log file is never truncated. A future Telebugs release will cap the log size. Commands: du -h docker inspect --format='{{.LogPath}}' telebugs truncate -s 0 $(docker inspect --format='{{.LogPath}}' telebugs)