Skip to content

todo.txt, Taskwarrior, Beancount

If you already keep a task list or a ledger, Nota reads it as it is. Set "format" on a list in probe.json:

"lists": [
{ "name": "duties", "path": "/home/me/todo.txt", "format": "todo.txt" },
{ "name": "tasks", "path": "/home/me/tasks.json", "format": "taskwarrior" },
{ "name": "books", "path": "/home/me/books.beancount", "format": "beancount" }
]

The source stays the place of record. A completed task is simply no longer reported, and resolves; a payment booked in the ledger settles what was outstanding.

A todo.txt file.

  • Open tasks with a due date are read: due:2026-11-20.
  • The first +project is the thing.
  • Priority (A) makes an overdue task critical.

The output of task export.

  • Pending and waiting tasks with a due date are read.
  • The project is the thing.
  • Priority H makes an overdue task critical.

The probe reads files and starts no program. The export is written by your own cron job:

Terminal window
task export > tasks.json

Nota is not a to-do list. Of a task list, only what has a due date is read; how many tasks have none is said in the list’s check file.

A Beancount ledger.

In the ledgerIn Nota
postings to Expenses:…cost, per month (the last 13 months)
postings to Income:…revenue, per month
the balance of Assets:Receivable…owed to you
the balance of Liabilities:Payable…owed by you
a posting’s due: metadatathe due date
a link on the transaction (^inv-2026-038)one outstanding amount per link, so invoices stay apart and a payment settles the one it names
accountsthings, each part of its parent
the metadata nota: "brandt" on a transaction or postingputs it on that thing instead — that is how a client gets revenue and cost on one line

Plain transactions only: cost and price annotations are ignored, includes are not followed, and what was not read is named.

Nota is not accounting. The ledger stays the book; Nota reads from it. See money.