$ tsk · a task board in your terminal · herdr plugin, runs standalone
One board where you both plan, pick up work, and move it through ready, started, blocked, review, done. Agents move tasks. Only a human marks them done.
Two real layouts. Beside an agent, tsk is the 78-column board herdr opens by default, and → peeks. Give it the whole terminal, or drag the divider past 110 columns, and the same board becomes the four-stage slider: → slides the task page in. The demo takes bare s d b o because browsers keep the control chords. In the app, every mutating verb needs Ctrl.
Five states shared by everyone on the board. Today you set them from the board, and agents capture and step work from the CLI; pick-up and hand-off are next. done is the one verb reserved for a human, and checking every step never flips it.
tsk is the shared surface between a developer and the agents working beside them. It lives in the pane you already have open. No browser tab, no sync service, no form takeover.
+ opens one line on the status row. Enter saves, Shift+Enter keeps the line open, Tab expands onto the task page. Two tokens set project and thread from inside the title.
+ Fix the flaky bench !p tsk !t ci enter save · shift+enter stay · tab page · esc close
Every mutating verb needs Ctrl. Bare letters do nothing, so a stray keystroke in a focused board cannot finish or delete work. Undo is one chord away.
enter open · ctrl+d done · ctrl+b block · : palette ctrl+x delete · ctrl+u undo · ? help · + capture
You, herdr's quick-capture overlay, and your agents edit the same
~/.tsk. An agent drops a plan in as JSON and the board shows it on
the next tick.
$ cat plan.json | tsk add { "created": [T33, T34, T35], "existing": [], "failed": [] } $ herdr plugin action invoke quick-capture --plugin herdr-tsk
Sections are computed, never navigated. Home is three tabs. desk is your own space for planning, loose ends, and future projects. projects holds the repos you and your agents work in. threads follows work that crosses them. Give the board 110 columns and it becomes a slider.
T-number you can click to copy, the title, then project and age.#name headers with a count. Unthreaded rows follow.At 110 columns and up, focus and geometry are the same thing. One rule, one footer, no colour.
→ one stage right ← one stage left Enter jump to the page and remember where you were Esc go back there
Navigation is bare. Anything that changes a task takes Ctrl. Esc always closes one layer.
Full chord tables for the board, task page, and capture form live in the keys reference.
Headless add, list, and steps against the
same store. An agent drops a plan in as JSON and it lands as ready tasks. It
can check off steps and report progress. It cannot mark anything done.
$ tsk add -t "Draft release notes" -p tsk --thread release --json {"outcome":"created","id":"5c1e…","number":32,"title":"Draft release notes","project":"tsk"} $ tsk steps T32 add "Write the failing test" added 9f Write the failing test $ tsk list T32 READY - 32 Draft release notes #release [ ] 9f Write the failing test $ cat plan.json | tsk add { "created": [...], "existing": [...], "failed": [] }
| 0 | listed, created, existed, or applied |
|---|---|
| 1 | one or more item refusals. Retry the failed subset. |
| 2 | usage or parse error. Nothing persisted. |
| 3 | store I/O. Indeterminate. tsk list before retrying. |
Adds are idempotent on title, project, and thread. --json is flat
and stable. CLI reference →
One binary, built from source. State lives in ~/.tsk whether you run it
bare or inside herdr.
$ git clone git@github.com:smarzban/herdr-tsk.git $ cd herdr-tsk $ cargo build --release $ ./target/release/tsk
Add target/release to your PATH and tsk add -t "First task"
from anywhere. The board reads it on the next tick.
$ cargo build --release $ herdr plugin link "$PWD" $ herdr plugin action invoke open-board --plugin herdr-tsk
The pane runs ./target/release/tsk, so build before you link. A running
board keeps the old binary until you quit it.