Add notifications for completed tasks and approval-required turns. #7046
Replies: 18 comments 2 replies
|
I’d like to work on a small, focused version of this. I reviewed #976, #1657, #1780, and the notification-sound foundation in #2373. My proposed scope would be limited to native OS notifications when T3 Code is not focused:
No sounds, overlays, pets, tray UI, or broader lifecycle-hook system. Would this scope be welcome if built on the newer thread-state foundation, or would you prefer to wait for #2373 first? |
|
@obrunogonzaga Is there any movement on your PR? I was looking to file a similar issue and came across this. |
|
The irony of theo constantly bragging about how fast T3 Code is being developed meanwhile users are waiting for basic system notifications for 5+ months bruh 😭 |
|
So there's NO notifications at all and no plan to add any? |
|
Adding a comment to bump this. Feels like an important but missing feature to me. Any chance this is getting merged? |
|
this app is so good except for this one glaringly missing workflow feature. at least add hooks for the thread lifecycle |
|
Theo says they are an anti-pattern so no notifications for us I guess at least vibe island added support for t3 code like a week ago so I guess you could use that for notifications on macos (I don't think you even need the paid version) |
|
lol what does "notifications are an anti-pattern" even mean. if anything me doing manual polling by switching back to T3 Code every 30 seconds to see if one of the threads needs my input is an anti-pattern. glaring hole in this app IMO. |
|
#6934 adds the Windows-specific acceptance case: native completion notifications with the thread title, click-through and an on/off setting. Notifications must wait for the overall run, not fire on individual subagent completions. Keeping those requirements linked here as the proposals are consolidated. |
|
I think it would be nice to have the option to have notifications, but my interpretation of being an anti-pattern is that notifications have the potential to distract you from your existing task and make you tempted to resume work on the other task abandoning your current thought process half way through, instead of naturally finishing of your review or prompt for one thread then seeing in the left hand side which threads are now waiting for you. I think this works so long as you are working within T3 code, but sometime I will be reviewing something that I can be distracted from and would rather keep the other thread making progress as the priority. |
|
As much as the "on-the-go" T3 code mobile app is pushed, I don't see why you wouldn't want at least a phone notification when your thread is finished |
|
@juliusmarminge please either build this or let me build it, happy to contribute if no one is workign on this |
|
Hi all! If you are waiting for this to be implemented in t3 code I made a small Menu bar application that will give you native notifications in MacOS along with inline replies and a count in the Menu Bar. You just have to connect it to your T3 Code instance the same way you would any other 3rd party client. Any feedback or feature requests would be appreciated! |
|
This is really easy with #10708 because you can have native notifcations and you could even be able to customise what type of notifications you get since it would just be a martter of the web ui communicating though the web channel that something has happened and you choose what you want to happen. Whether it's a dancing cat or sms message through an external service. |
|
This gist is a demonstration of how this feature could be built or customized with the Qt/QML branch. It is an example to try and adapt, not a complete implementation of the discussion request or a feature shipped in upstream T3 Code. I added an opt-in Qt notification module for Linux. It covers completed turns and supervised approvals, plus configurable input/error/start events. It stays quiet while this window is active by default. This gist uses the repository's existing Rosé dashboard example, with the controls above the page. Controls cover event types, foreground delivery, silent mode and timeout. The desktop notification service decides whether to honor silent mode and timeout hints. Clicks open the originating thread. Titles, body text and filtering are editable QML functions. The current backend requires a Linux desktop notification service; macOS and Windows delivery are not implemented. The full-desktop screenshot shows a real Linux notification from the native backend on workspace 5. It is labelled TEST ONLY and was triggered directly to check delivery, not by a provider completing a turn. The app uses demo data. Code and checks assisted by Codex. |
|
this was suggested in march '26 , are there any working updates on this? I wish there's an extensions gallery in future, so devs could ship extensions & people could add up any features they like without any hassle of building and without affecting the rest of the users!! |
|
That is what I'm trying to do with the QML version #10708. It's really easy to add extensions without going through the current issue -> PR process, because it's hard to know whether things make sense for everyone. It's a lot easier to see what customizations people are using and then integrate them into the main project |


Uh oh!
There was an error while loading. Please reload this page.
Right now if a task finishes in a chat while the user is in another app, they get no signal. Same for approval-required turns in supervised mode.
We should notify users when:
All reactions