Don't YOLO your file system

Summary

This is not hypothetical. People are already reporting lost files, emptied working trees, and wiped home directories after giving AI tools ordinary machine access.There's a gap between giving an agent your real account and stopping everything to build a container or VM. jai fills that gap. One command, no images, no Dockerfiles — just a light-weight boundary for the workflows you're already running: quick coding help, one-off local tasks, running installer scripts you didn't write.Your files, your rulesUse AI agents without handing over your whole account. jai gives your working directory full access and keeps the rest of your home behind a copy-on-write overlay — or hidden entirely.Stop trusting blindlyOne-line installer scripts, AI-generated shell commands, unfamiliar CLIs — stop running them against your real home directory. Drop jai in front and the worst case gets a lot smaller.Containment shouldn't be hardNo images to build, no Dockerfiles to maintain, no 40-flag bwrap invocations. Just jai your-agent. If containment isn't easier than YOLO mode, nobody will bother.How it works One command. No setup required.1Prefix your commandjai codex, jai claude, or just jai for a shell.2CWD stays writableYour working directory keeps full read/write access inside the jail.3Home is an overlayChanges to your home directory are captured copy-on-write. Originals are untouched.4Rest is locked down/tmp and /var/tmp are private. All other files are read-only.Three modes Pick the level of isolation that fits your workflow.CasualStrictBareHome directoryCopy-on-write overlayEmpty private homeEmpty private homeProcess runs asYour userUnprivileged jai userYour userConfidentialityWeak — most files readableStrong — separate UIDMedium — your UID, but home hiddenIntegrityOverlay protects originalsFull isolationFull isolationNFS home supportYesNoYesVersus the alternatives jai is not trying to replace containers. It fills a different niche.DockerGreat for reproducible, image-based environmen...