Repository navigation
v0.2.0
The first release meant to be used, not just built. A local, private task manager where finishing something leaves a record you can go back to — because the reason you did it is usually worth more than the tick.
No account, no server, no telemetry. It makes exactly one network request in its
life: to ask whether there is a newer version, once a day. Turn that off and it
makes none.
Tasks that read what you write. Type a sentence and Tisty pulls the date out
of it, leaves the sentence readable, and shows what it understood before
anything is saved — as chips you correct with one click. A deadline is a
different thing from a plan, and three words open one: before, due, until.
What it cannot read it leaves alone instead of guessing.
A task that opens beside the list, not on top of it. Dates, list, tags,
priority, a description and a journal in Markdown, steps you tick one at a time,
and whatever you dropped on it. Completing it puts none of that out of reach.
Documents. Markdown files that live beside the tasks, for reference material
that has no date and never gets ticked — tables, checklists, code, images.
Search reads them too. A task can point at a document; a document never creates
tasks.
Quick capture on a global shortcut, so a task that occurs to you
mid-something does not cost you the something.
Repeating tasks come back one occurrence at a time, so the archive shows you
did it twelve times. Reminders arrive as a system notification and a short
sound you can turn off.
A command line, if you want one. Same store, same tasks. tisty ls,
tisty add, and captures straight from the terminal.
Point Tisty at a folder both computers already reach — the one your Google
Drive, OneDrive or iCloud client keeps in step, a NAS, a disk you plug in on
Fridays — and the rest happens on its own. There is nothing of ours in the
middle.
Both machines can edit the same document at once, and Tisty merges it block by
block: you edit the introduction on one, someone edits the closing on the
other, and both arrive without a question. Only genuine overlap asks.
And a limit we would rather say out loud than hide. Tisty writes to that
folder and reads from it. What uploads it is your provider's own program, not
Tisty — so if that program is not running, Tisty will keep saving your work
perfectly and has no way to tell that nobody is picking it up. This release
makes that visible instead of pretending otherwise: the settings panel now shows
when something last arrived from another machine as a separate fact from
your own last round, says plainly where its reach ends, and asks after days of
silence. FAQ.md lists the causes worth checking, in order.
As important as the list above, and permanently out of scope: real-time
collaboration, kanban boards, Gantt charts, time tracking, productivity metrics,
databases with typed properties and formulas, and AI anywhere in the critical
path.
Two things are decided rather than pending: you cannot reorder by hand in the
window — HTML drag and drop does not survive the native file drop that
attachments need, and attachments were the better trade — and nothing has been
tested with a real screen reader, though the keyboard path has.
macOS and Windows. Linux is not planned.
| macOS | .dmg, universal, signed and notarised |
| Windows | .exe installer, signed |
| Command line only | the tisty binary on its own, both systems |
On macOS you can also install just the command with
brew install rgdevment/tap/tisty-cli and never open the window.
Everything lives in one folder on your machine, in plain files you can read
without Tisty: an append-only log of events, your documents as Markdown, your
attachments as themselves. Nothing is encrypted at rest, and that is a stated
decision rather than an oversight — PRIVACY.md explains what that
does and does not protect you from.
Released under the AGPL-3.0. Signed store builds carry their own
terms — DISTRIBUTION.md says which applies to what you
have, and why. Nothing is withheld from the source either way.
Full Changelog: v0.2.0-rc8...v0.2.0