Send alerts to Teams and open backtraces where you work
- Kyrylo Silin
- Telebugs founder
Telebugs 1.13.0 is here with three major workflow upgrades that make debugging faster and more seamless: Microsoft Teams notifications, one-click opening of backtrace frames in your favorite local editor, and direct links to view or edit code right on your repository host. On top of that, I’ve made the dashboard cleaner by default, showing only unresolved errors, and added a bunch of polish across the app.
Microsoft Teams notifications
Many teams live in Microsoft Teams, so getting error alerts there has been a frequent request. With this release, Telebugs now supports sending richly formatted error notifications directly to your Teams channels, right alongside Slack, email, and other integrations.
Configuring an error notifications in Microsoft Teams.
Microsoft Teams Telebugs notification.
Open in your preferred local editor
Nothing beats jumping straight from an error report to the exact line in your local codebase. You can now configure a preferred local editor (VS Code, Cursor, Zed, etc.) in project settings. Once set, clicking any backtrace frame opens it instantly in that editor using a custom protocol handler, just like “Edit in…” shortcuts you know from other tools.
Clicking a backtrace frame and opening the file in your configured local editor.
Direct repository links
When you’re reviewing an error and want to see the surrounding code on your repo host, Telebugs can now take you there with one click. Configure your project’s repository URL (GitHub, GitLab, or Bitbucket) and you’ll get “View on…” buttons for each frame. For GitHub projects, there’s an extra treat: an “Edit on GitHub” option that opens the file directly in the web version of VS Code.
“View on…” and “Edit on…” actions for backtrace frames.
Clicking “Edit on GitHub” to open the file in GitHub’s web VS Code.
Unresolved errors by default
One of the most noticeable changes: error lists now default to showing only unresolved errors. This keeps your dashboard focused on what actually needs attention, without the clutter of old resolved issues. You can still toggle to see everything whenever you want.
Cleaner error tables showing only unresolved issues by default.
Other improvements & fixes
New pills highlight key report details.
A round of polish and reliability updates that make the app feel sharper:
- Improved empty states for error tables, so they’re clearer when there’s nothing to show.
- Moved several report details into compact pills for better readability.
- Fixed-height Dependencies card to handle long lists gracefully.
- Replaced text labels with icons for “Jump to” and “View as” actions, saving space and cleaning up the layout.
- Updated Slack integration to modern block-based payloads (the old attachment style is deprecated).
- Added release information as a pill when available.
- All documentation links now point to the new docs.telebugs.com.
- Fixed duplicate notifications, unescaped Slack payloads, merged group cleanup, notification cooldowns, and a handful of other bugs.
- Behind the scenes: upgraded to Ruby 4.0.0 and Rails 8.1.2.
Wrapping up
This release shortens the path from a notification to the exact line that needs attention. Teams alerts, local editor links, and repository links each remove a small handoff from the debugging loop, while the unresolved-only default keeps the next problem in view.