Your data
Command line
The window is the way in. The tisty command stays for two things: it is the door your assistant comes through, and it is where maintenance lives.
The window is the way in. The tisty command stays for two things: it is the door your assistant comes through, and it is where maintenance lives.
Warning The task and document commands (
tisty add,tisty ls,tisty done…) are being retired in stages. What they still do keeps working, but no new feature reaches them, and they go away in the next major version. If you script againsttisty ls --jsonortisty add, plan to move: the MCP door is how a program reaches Tisty.
The commands that stay
| Command | What it does |
|---|---|
tisty mcp | Speak MCP over standard input and output, so an assistant can file work here. See Assistants and MCP |
tisty agent --on / --off | Let an assistant in, or stop it. --on asks you on the terminal first |
tisty doctor | Check that the read cache agrees with the log |
tisty doctor --repair | Throw the read cache away so it is rebuilt from the log |
tisty sync | Run a sync round now |
tisty sync --confirm <machine> | Confirm another machine of yours, after comparing its key |
tisty sync --again | Copy everything of this machine’s to the folder again |
tisty export | Print your tasks as JSON — open and archived, filtered if you pass a filter |
tisty export --markdown | The same, as Markdown |
tisty leave | Take Tisty’s settings, cache and command line off this machine. Your documents, tasks and attachments stay |
$ tisty doctor
$ tisty sync
$ tisty export --markdown
Who is at the keyboard
tisty refuses every command but tisty mcp when a coding assistant is driving it, so an assistant cannot use the terminal to act as you or let itself in. See Assistants and MCP.