tasu
A terminal todo list that ages.
Tasks go into today. Whatever you don't finish sinks — today's leftovers become this week's, and this week's become later. There are no due dates, projects or tags; the list organizes itself by how fresh each task is.
TODAY
──────────────────────────────────────
○ Nand2Tetris chapter 6
○ learn GPUI events
THIS WEEK 41/53
──────────────────────────────────────
○ write the README
LATER
──────────────────────────────────────
○ read the ratatui source
Install
Prebuilt binaries, no Rust toolchain needed.
macOS / Linux
Or without Homebrew:
|
Windows (x86_64) — in PowerShell:
powershell -ExecutionPolicy Bypass -c "irm https://github.com/mancuoj-collective/tasu/releases/latest/download/tasu-installer.ps1 | iex"
This installs tasu.exe into %USERPROFILE%\.cargo\bin and adds it to your
PATH; open a new terminal afterwards. Or download
tasu-x86_64-pc-windows-msvc.zip
and put tasu.exe somewhere on your PATH.
With Cargo (Rust 1.88 or newer)
Or build from a checkout:
Usage
The everyday commands have short aliases, shown in tasu --help: a (add),
ls (list), h (history), d (done), x (drop), mv (move).
Every command that changes something prints what it did, and list, history
and config take --json for scripting.
Tasks carry no id, so done, drop and move match an open task by its
exact title; if none or several match, they error rather than guess.
tasu update detects how tasu was installed and runs the matching upgrade —
brew upgrade mancuoj/tap/tasu, the official installer, or cargo install tasu
— so the binary and the package manager that owns it stay in agreement. For an
unknown install it prints the right command instead of guessing.
Keys
| Key | Action |
|---|---|
j k ↓ ↑ |
move the cursor |
h l ← → |
previous / next section |
g G Home End |
top / bottom |
space Enter |
complete |
a |
add (goes into today) |
e |
edit the title |
t |
move to today |
[ ] |
send to the nearer / farther bucket |
x |
drop (archive) |
c |
history |
? |
help |
q Esc |
quit |
Ctrl+c |
quit from anywhere |
Narrow terminals stack the buckets vertically; 100 columns or wider lays them out as three side-by-side columns.
c opens the history overlay. Enter restores a completed or dropped task to
its original bucket, Tab (or ←/→) switches between done and dropped,
and typing filters the list.
Sync between machines (optional)
tasu is local-first: with no remote it never invokes git. Point it at a private repository to sync, and it behaves like a single writer that commits as you go.
tasu remote accepts a full URL, an SSH address (git@…), a local path, or a
GitHub owner/repo shorthand. It verifies the remote before saving it; if
the check fails nothing is written (and any previous remote is cleared), so tasu
never gets stuck retrying an unreachable repository. With no argument it prints
the current remote, and tasu remote --clear turns syncing off.
- First run clones into an empty data directory. If the remote already has history (say a README), tasu adopts it and pushes the local board on top.
- If both sides already have a board, they are merged (union, exact duplicates dropped) — neither machine loses tasks.
- One branch everywhere: the remote's default branch if it has one,
otherwise
main. A machine'sinit.defaultBranchnever leaks into the data repo. - In the app, tasu pulls on start, pushes a few seconds after each change
(debounced), and pushes once more on exit. A failure shows
✗ sync failed · <reason>in the footer and a one-line reason in help;tasu syncprints the full git error. tasu addpulls before it reads and pushes after it writes, so a CLI-only machine stays in sync too.- Designed for one writer at a time (your work machine or your home machine, not both editing at once). There is no merge of conflicting edits.
To try it against a local bare repository:
TASU_DATA=/tmp/tasu-a TASU_REMOTE=/tmp/tasu-remote.git
TASU_DATA=/tmp/tasu-b TASU_REMOTE=/tmp/tasu-remote.git TASU_DATA=/tmp/tasu-a TASU_REMOTE=/tmp/tasu-remote.git
Configuration
Environment variables take precedence over the config file. With no remote,
tasu never invokes git.
| Setting | Default | Environment | Config file |
|---|---|---|---|
| Data directory | platform data dir /tasu |
TASU_DATA |
data_dir |
| Sync remote | none (local only) | TASU_REMOTE |
remote |
The config file lives in the platform config directory at tasu/config.json:
It is kept out of the data repository, so it never travels between machines.
Non-goals
On purpose, there is no: due dates, projects, tags, priorities, subtasks, notes, notifications, recurrence, global hotkey, or multi-writer merge.
Development
The pure layers (domain, update, store, sync) are covered by unit and end-to-end tests, including a real git round trip. To eyeball the layout without a terminal, render sample boards to text:
PRODUCT.md is the product contract and
ARCHITECTURE.md describes how it is built.
License
Licensed under the Apache License, Version 2.0. See LICENSE.