"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 @telebugs.com 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 @telebugs.com.
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 @telebugs.com 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
Claude can now investigate your @telebugs.com 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.
Give them a spin:
github.com/zhuravel/tel...
“It’s fast, simple to use, and does exactly what you need without overcomplicating things.”
Just got this testimonial for @telebugs.com 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
👇👇👇
Telebugs 1.14.0 released.
Filtering sensitive information in @telebugs.com.
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 @telebugs.com 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 @telebugs.com 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! 👇
github.com/jilio/telebu...
🚨 PSA for all @telebugs.com 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.
Improved timestamp handling in @telebugs.com.
Projects each have their own timezone, but cross-project views use UTC timestamps.
This was confusing: project views showed local time, while others showed UTC.
Now we display relative time everywhere, and on hover the tooltip shows both (local+UTC).
A few weeks ago, a @telebugs.com user shared a really insightful request that hit home for anyone running critical applications.
Today I added support for sentry-cli v3. In @telebugs.com, it’s used to upload source maps.
I still have ~10 support requests pending, and I’m sorry to everyone who’s been waiting. Bad timing: I took a few weeks off, and a lot of tickets came in at once.
Normally, I address issues the same day.
Coming soon to @telebugs.com: sparklines for every error.
Each error has its own occurrence pattern. You can already see that on the error page, but until now, there was no quick way to compare errors side by side and spot what needs attention first.
Coming soon to @telebugs.com:
Sparklines beyond the last 24 hours.
Some users don’t check the dashboard daily and want to compare error volume over a few days (Friday sign-off → Monday return).
Now you can filter project sparklines by timeframe.
New in the upcoming @telebugs.com: auto-refreshing errors.
I noticed some Telebugs users don’t use notifications at all. They just keep the dashboard open and rely on it to stay on top of errors.
So the next release adds a simple checkbox: auto-refresh, to make the dashboard feel a bit more alive.
While I was away for a few weeks, @telebugs.com accumulated a ridiculous backlog of support requests.
There's a pile to go through before I can proceed with @telesink.com.
I’ve just set up a private @telebugs.com demo instance for the first time in a while (for a potential client). I’ve been deploying them with Kamal.
Usually it’s smooth, but this time I hit a snag:
Telebugs 1.13.0 is here with 3 major features:
1️⃣ Microsoft Teams notifications
2️⃣ One-click opening of backtrace frames in your favorite local editor
3️⃣ Direct links to view or edit code right on your repository host.
Bonus point: lots of bug fixes 🐞🔨
Read more:
telebugs.com/blog/telebug...
Telebugs 1.13.0 released.
Preparing the changelog for @telebugs.com 👀
New in the upcoming @telebugs.com release:
Edit files directly on GitHub via the web version of VS Code.
How it works:
1️⃣ Set up GitHub as your project's repository
2️⃣ Click "Edit on GitHub" next to "View on GitHub"
3️⃣ YOLO your fix!
Shipping soon.
New in the upcoming @telebugs.com release:
Open files directly from the backtrace
How it works:
1️⃣Set your preferred text editor in Account Settings
2️⃣Browse the backtrace of any error
3️⃣Click “Open in editor” to open the file at that exact frame locally
Supports all major text editors. Shipping soon
New in the upcoming @telebugs.com release:
Link errors directly to your source code.
How it works:
1️⃣ Set your repository and branch when creating a project
2️⃣ When an error arrives, Telebugs builds a direct link to the exact code
No repository access required.
Supports GitHub, GitLab, and Bitbucket
The upcoming @telebugs.com version will have support for Microsoft Teams!
Closing the year on a high with an awesome @telebugs.com testimonial. Thank you for the kind words 🙇♂️
