r/taskwarrior

Hey folks, been a while since my last update (literally the initial release), but 0.9.0 is out and I thought it was good timing for sharing the latest features.

brings

• contexts v2: contexts got a lot smarter: you can now build richer expressions with multiple filters, negative terms, parentheses, and virtual tags. Both guided selection and direct expression editing are supported

• taskrc import (initial support): paste in your taskwarrior config and fatto will import it. It'll add/update contexts and start-of-week day, and give you a report of what was imported, changed, skipped, or unsupported. More settings support coming later :)

• S3 sync backend: fatto now supports AWS S3 and S3-compatible sync in addition to taskchampion sync server.

• settings reorganized into tabs, splitting things up (sync, etc.) so it's easier to navigate as the app grows

• auto waiting: optional auto-wait can hide due or scheduled tasks until one week before their target date, without overwriting explicit wait dates

and from my last post we supported a lot of other things:

• urgency, priority

• dark theme

• better and clickable notifications

• quick "is active" filter

• remember sort setting

• annotations support

• uida visualization

Let me know if you hit any issues, enjoy!

Is anyone else running Taskwarrior on Android/Termux and wants their phone to become slightly more annoying in a productive way? Then look no further and check project.

It watches for pending tasks due around now and turns them into Android notifications, one per task, with buttons for:

- Start / Stop

- Done

- Tomorrow (snooze for 1 day)

It also handles overdue tasks, quiet hours, active-task promotion, local snooze, optional timelog integration, and has a small Termux:GUI dashboard.

Basically: Taskwarrior stays the source of truth, Android does the nagging.

The project is functional but not polished, if you need a feature/modification/improvement then feel free to post here or raise an issue in the repo.

Repo:

P.S.

If you are using recurrence then you will have to use the because this project is completing tasks with the hooks=off.

Deus vult.

Now that WingTask is back in town with support for TW V3+ the issue that I've been dealing with was how to make Nautical which is a hook system work alongside a hookless system.

Normally, Nautical uses Taskwarrior hooks to spawn the next recurrence task when you complete a cp chain or anchor task. On a hookless client, the task can be marked complete, but the next link will not be created because the hooks never ran.

There are two ways to handle this:

1. The manual solution

Update to Nautical v4.7.1+ and then run the Nautical recovery tools after syncing:

python3 nautical_core/tools/nautical_chain_repair.py --apply

python3 nautical_core/tools/nautical_reconcile.py --apply

chain_repair fixes safe lineage metadata issues like prevLink, nextLink, and link. This should be the case only if you used Nautical < v4.0.0.

reconcile handles hookless completions. It can backfill a missing nextLink if the child already exists, or spawn the missing next task when Nautical can compute it safely.

2. Automatic and elegant solution:

Use this helper script instead of calling task sync directly:

alias ty="bash task_sync.sh"

The helper checks whether sync is actually needed, runs task sync only when useful, and can automatically run Nautical chain repair/reconcile afterward. This makes it practical to complete Nautical recurring tasks from hookless clients and let a hooked system repair/spawn the recurrence after sync.

Repo:

Nautical: