catanadj/taskwarrior-tnt — explained in plain English
Analysis updated 2026-05-18
Get Android notifications for Taskwarrior tasks due within a configurable time window.
Start, stop, complete, or snooze tasks directly from a phone notification.
Track task time with optional jot timelog integration triggered by notification actions.
| catanadj/taskwarrior-tnt | 100/dotfiles | adams549659584/my-openwrt-actions | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | Shell | Shell | Shell |
| Last pushed | — | 2016-11-18 | 2020-06-06 |
| Maintenance | — | Dormant | Dormant |
| Setup difficulty | moderate | easy | hard |
| Complexity | 3/5 | 1/5 | 3/5 |
| Audience | developer | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires Termux, Termux:API, and a Tasker profile configured to run the notification script on a schedule.
Taskwarrior TNT brings Android notifications to Taskwarrior, the command line task manager, by connecting it to Termux and Tasker on your phone. The name stands for Termux Notifications through Tasker. It is a set of shell scripts that scan your pending Taskwarrior tasks and post a notification for each one that is due around the current time, by default anything due from two hours ago through two hours from now. Each notification includes buttons right in the notification itself: you can start or stop time tracking on a task, mark it done, or push it to tomorrow, all without opening a terminal. Notifications are labeled OVERDUE, SOON, NOW, DUE, or ACTIVE depending on timing, and show the task's time window along with its project and tags. Setting it up means installing a few Termux packages, including Taskwarrior itself and the Termux:API app for posting notifications, then running the included install script, which copies the scripts into place and checks that everything works. From there, you create a Tasker profile that runs on a schedule, such as every 15 or 30 minutes, and points at the notification script, the script talks to Android directly, so no separate Tasker notification action is needed. Behavior is controlled through a configuration file covering things like the notification time window, quiet hours where the scan still runs but stays silent, notification icons and priority, and how snoozing or marking a task for tomorrow behaves. There is also optional integration with a time-logging tool called jot, and an optional graphical dashboard through Termux:GUI for people who want a visual view alongside the notifications. A built in doctor mode and dry run option help troubleshoot setups where notifications are not appearing as expected.
Shell scripts that connect Taskwarrior to Android via Termux and Tasker, posting due-task notifications with start, stop, done, and snooze actions.
Mainly Shell. The stack also includes Shell, Termux, Tasker.
License terms are not stated in the README.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.