It is not running in the T3 app currently open on Dennis.
The T3 app is open, but it is the installed official Alpha build. The scheduled-task feature is in our separate fork, so the open app does not contain that code yet.
The running application is /Applications/T3 Code (Alpha).app, version 0.0.33. Our source branch is feat/scheduled-threads in the fork. The source branch and the installed app happen to have the same version number, but that does not mean they contain the same code.
Why the code is not active yet
There are two separate things:
A packaged application in /Applications. This is what is currently open and what you use day to day.
A development copy of T3 Code containing the scheduled-task changes. Editing this source does not change the already-installed app.
Think of it like editing a recipe after a cake has already been baked. The recipe changed, but the cake does not change until we bake and install a new version.
Would we need to reinstall?
To use the feature in the normal macOS app, yes, we need to build the fork and install that custom build, or run the fork in development mode. We do not need to reinstall just because the branch exists.
- Development mode: run T3 Code from the fork. Good for testing; not the normal everyday app.
- Custom app build: build a new macOS app from the fork and install it. Good for actually using the feature in the desktop UI.
- Official release: wait until the feature is merged upstream and shipped by the official T3 project. Good for staying fully standard, but it may take time or may not happen.
Are we now out of sync with official T3?
Yes, temporarily, if we install our custom fork. That is normal for a feature branch, but it creates maintenance work.
Official T3 can continue releasing updates while our fork has additional changes. We would need to periodically bring official changes into our fork, resolve conflicts if both versions edit the same files, rebuild the app, and retest the scheduled-task feature.
The safest workflow is to keep the official app untouched while testing. We can use a clearly labelled custom build, such as T3 Code — Scheduled Tasks, so it is obvious which app is which.
What works once the fork is installed?
- The scheduler runs inside T3’s backend process.
- The macOS desktop app already starts and manages that backend.
- Scheduled prompts create ordinary T3 threads.
- Threads appear in the native app like normal conversations.
- Schedules currently run only while the T3 backend is running.
Important: if T3 is completely quit, the current implementation does not wake the Mac and run the task. A later macOS LaunchAgent or independent scheduler could solve that.
Recommended next step
Do not replace the official app yet. First build and test a separate custom fork app, create a test schedule for a few minutes in the future, confirm that one new conversation appears, and confirm the run history. Once that works, decide whether to keep the custom build, add an always-on helper, or wait for upstream adoption.