ScriptKittyThe first minute after install
This page covers what ScriptKitty does on its own once it is installed, and what the first-minute scan will do when it exists. Today there is the first part only.
What happens today
Running the installer starts the service. The disks it watches are covered from that moment, with no setup. It holds an old copy of a file, or a second name for it, before the file is deleted or changed.
Not everything is watched, and ScriptKitty says so. Run sk status and it lists every place that is left out, and why. It also shows what is watched and how much room the held copies take.
sudo ./install.sh # installs and starts the service
sk status # what is watched, what is left out, room held
Some places are left out on purpose, such as /var/log, /var/cache and package lists, and you can bring a folder back in. USB sticks, SD cards and disks mounted by hand are watched only if you ask with sudo sk watch DISK. Memory disks, which usually means /tmp, FAT, exFAT, NTFS, network disks and ZFS are not watched at all.
The first-minute scan
Coming The scan is not built.
This is the plan, and none of it exists yet. The scan would find the AI agents on a machine, show what each can reach, and show what would be gone forever if something went wrong. It would be one button.
What exists today is sk status, described above. The list of what ScriptKitty cannot bring back is on what it cannot undo, and it is worth reading before you rely on the tool.
Next: the morning after a bad overnight run, or install.