v3.17.0: A Notification System Built on Respect 🎯
5
Publication Date: 23/02/2026
Author: Anas Chakroun
6-7 minutes
v3.17.0 adds context-aware timing to Turbo's notification system. It's the latest layer in our multi-year effort to balance helpful communication with respect for your workflow.
Before diving into what's new, let's walk through what makes this notification system different from typical extension spam.
Three Reasons You See Notifications
Turbo's notification system serves three core purposes:
- Onboarding new users: Help first-time users discover core features and get familiar with Turbo
- Sharing insights: Share useful tips, workflow improvements, and hidden features when timing is right
- Communicating updates: Announce new releases, bug fixes, and improvements
Pro mentions appear when they should. Hit 50 log inserts? That's the moment to discover features that could save you even more time. We believe every user deserves to know what Pro offers, and showing you at the right moment is part of respecting and promoting your workflow, not interrupting it with random promotions.
Built-In Respect: How We Protect Your Attention
From day one, we've designed strict safeguards to ensure notifications feel helpful, not intrusive:
📅 Bi-Weekly Release Notifications
Every ~2 weeks, you'll get a release announcement. It's our duty to communicate what's changed in software running in your editor.
⏱️ 48-Hour Cooldown Window
Most notifications respect a 48-hour cooldown. Two exceptions can bypass this window: release announcements (you need to know about updates) and PHP workspace notifications (time-sensitive feature access). Everything else waits its turn.
🔢 Maximum 6 Notifications Per Month
2 bi-weekly releases plus up to 4 contextual notifications when timing is right. That's it. Even if perfect conditions align, we cap it at 6 total.
🛡️ Server-Side Enforcement
All checks happen server-side using your anonymous user ID (no personal data). Running multiple VS Code windows? You get one notification per event, not duplicates in each instance. This also protects against corrupted local storage, migrations, and reinstalls.
🚫 Three-Strike Pause System
Dismiss 3 notifications in a row? The system pauses all non-release notifications until the next month. We take the hint.
Turbo is free and open source. You can verify the cooldowns and caps logic in the codebase: https://github.com/Chakroun-Anas/turbo-console-log
v3.17.0: Smarter Timing
We've gone beyond these foundational mechanics. After analyzing tens of thousands of notification interactions, we discovered that even respectful frequency isn't enough. Timing matters just as much.
Picture this: Saturday evening, you're exploring a side project with a couple of files open. A tip about a workflow improvement pops up. You click through, read the article, maybe even apply it. Perfect timing.
Now imagine: Monday morning, you're racing toward a deadline with 8 editors open, unsaved changes everywhere. The same tip appears. You dismiss it instantly. Terrible timing.
v3.17.0 introduces context-aware scheduling that considers your workspace state, time of day, and day of week before showing notifications. We're not showing more notifications. We're showing them at better moments.
✨ Zero Configuration Required
The system adapts automatically. You don't configure anything, set preferences, or adjust sliders. It just works. Quietly, respectfully, intelligently.
For Users Who Complained
We heard your feedback about notification timing. We read every GitHub issue, every Reddit comment, every email. Some of you were frustrated, and rightfully so.
This release is our response. We've invested significant effort into building a system that respects your workflow, respects your attention, and delivers value at the right moments.
If notifications still feel intrusive, reach out. This is continuous work. We're committed to keep improving based on your feedback.
Thank You 🙏
Your feedback shapes Turbo Console Log. Thank you for being part of this journey and helping us build something truly respectful of your workflow.