History and undo
Every change to your data is one line in one log. So you can undo any change to your data, or bring back an older version of an entry, even days later.
Something that already left Kaizendex (a sent email, a post) cannot be unsent. That is why, by default, it waits in the outbox for your Approve tap first, unless it is part of an automation you approved.
Who writes lines
Every change, from anywhere, is a line: your taps, the AI, a script, an import, an automation, and an edit to a file in your folder. They all go through one path, so they all undo the same way.
Each line names who made it:
| Who | Example line |
|---|---|
| You, in the app | You · Morning run · Distance 5.2 → 5.4 |
| The AI in the app | Coach agent · Workouts · new entry “Push day” |
kzx, the command line |
kzx · Reading list · Status → Done |
| An MCP program (Claude Code, Codex) | Claude Code · Morning run · Notes changed |
| Your folder | Folder · Workouts/Morning run.md · Distance changed |
| An import | Import · 27,435 changes from the old app |
| An automation | “Weekly review” · Tasks · 3 entries moved |
The app treats kzx and MCP programs as an AI. So the AI rules below apply to them too.
Undo
- Remove something, and a toast offers Undo. The app does not ask “Are you sure?” for things that are cheap to bring back.
- Undo works later too. Each line can be reversed, even days later.
- Undo works across devices on Pro. Undo on your phone a change you made on your laptop.
- Undo works on a whole change. One change can touch many things. A bulk import, one run of an automation, or an AI answer that logs three workouts is one step to undo.
- One click is one change. Making a workout from its preset (the workout and all its sets), dragging properties into a new order, or swapping what a link points to is one change, so one Undo takes all of it back.
- Undo keeps your later edits. Say the AI renamed “Push day” at 9:00, and you changed its date at 9:05. Undo the AI’s change, and only the name goes back. Your new date stays.
- Undo can be undone. An undo is a change too, with its own line.
History
An entry’s lines are its past versions. Open its history and restore any of them.
Example: on 20 Oct you rewrote the notes of “Push day”. On 27 Oct you want the old notes. Open the history of “Push day” and restore the version from 19 Oct.
How long the app keeps each entry’s history is set later, together with sync. Old lines are folded into snapshots, so the log stays small.
What an AI cannot touch
The AI, kzx and MCP programs obey each collection’s and entry’s AI setting. When they are
refused, they get a plain reason and what to do instead.
| Setting | What the AI gets |
|---|---|
| No AI | Refused. It cannot read or change it. |
| Hidden | Refused. It cannot read or change it. |
| Ask me first | It waits. Nothing is read or changed until you say yes in the app. |
| Only my local AI | Refused, unless a model on your own computer does the work. |
Some settings are yours alone: the AI setting, Hidden, and the folder choice. Only you change them, in the app. The AI, the folder and automations cannot. See What AI may read and Changes only you can make.
Delete for good
Deleting moves an entry to the Trash. After 30 days it is deleted for good, and the toast says so: “Moved to Trash · deleted for good after 30 days”.
An entry deleted for good is gone from every copy within 30 days:
- At once, it leaves your devices (each one as soon as it next connects) and the cloud copy.
- Within 30 days, older copies expire too: old restore points and old file versions in the cloud, and the desktop app’s own backups.
What we cannot reach, said plainly:
- your own Git history, if you use “Version this folder with Git”;
- copies in a cloud drive (OneDrive, iCloud Drive, Dropbox, Google Drive) that holds your folder;
- exports you made;
- what people you shared with already copied.
The AI receipt
Everything the AI wrote is a line you can undo. The AI also leaves “read” lines that say what it read and where its question went. Together they form the AI receipt. See Chats.
When the database itself breaks
History lives in the database. For a broken database, the app keeps backups and offers Go back in time. See Backups, export and recovery.