Building a safe playground for non-developers and AI to work with files

My first taste of no-code/low-code tools was something called Homestead, back when I was in eighth grade, a simple drag-and-drop website builder that probably had basic database support. I remember using multiple email addresses to reset free trials because I couldn't pay for it. That was the beginning of something.

By 2009, working out of my room in Bangalore, I was stringing together PHP Runner, Appery (formerly Tiggzi), and whatever else could get me a working product without writing much code. The appeal was never about avoiding code. It was about finding the lazier path to the same outcome, which I've come to believe is often the smarter path, though I'm not entirely sure those are the same thing.

After trying a whole lot of other tools, a few years back I found what I now think of as the best no-code/low-code tool available: AI-powered development. I've tried GPT, Gemini, and a whole lot of others, but Claude models fit how I think, so that's what I use. The speed at which I can build something real has changed completely.

All the tools I used to use came with safety nets. Most apps had an undo button. Later, everything lived in version control. Even the simplest IDE integrates with Git now, and I've taken it for granted that any file I touch can be rolled back, branched, forked, or duplicated. That's the developer experience. You can try things freely because you can always get back to where you were.

When I started working with AI on ordinary files, not code, just documents and spreadsheets and notes, the safety nets weren't there.

Take something as simple as generating an invoice. The way my setup works, I talk to my assistant, it calls the right skill, and the invoice gets created. But that invoice isn't a single file. It's a CSV that acts like a database, a markdown file with the invoice details, and a Word document that gets converted into a PDF. Three or four files change in one shot. The AI made those changes, and I can see the edits if I look closely, but if something went wrong or I need to go back to how things were ten minutes ago, where do I even start?

The same problem shows up in most of my non-code workflows. Strategy documents, presentations, folder structures that consultants duplicate for every new engagement. Or a consultant duplicating last quarter's strategy deck for a new client, then realizing the AI overwrote something in the original. Tools like PowerPoint have version history built in, but they're all siloed. If the AI edits three files at once and something breaks, you'd have to go into each one and undo the changes separately.

I'm not arguing that everyone needs to learn Git. That's not the answer. But the features that developers have taken for granted for decades are becoming necessary for everyone who works with AI on their local files. Version control. Checkpoints. The ability to save the state of a folder and come back to it. The ability to see what changed between two points in time. The ability to duplicate a whole folder and try things on the copy without worrying about breaking the original.

What I've been building is essentially that, a layer that watches over a folder of files while the user and the AI work inside it. Every time something changes, a snapshot gets saved automatically. You can annotate what was changed. If you need to go back, you pick a point in time from a list and restore it. No special tools to learn, no technical setup.

For people who work on the same structure repeatedly, like consultants with a standard project folder or agencies with a repeatable process, there's also a way to duplicate a folder, start fresh, and build from there without touching the original.

I know this is going to be useful to the kinds of people I'm building for, the non-developers working with AI on everyday tasks. I know the problem is real because I felt it myself.

Seventeen years after resetting Homestead trials, I'm still chasing the same thing: the lazier and smarter path that actually works.

Still figuring out the edges. But for the first time, I can let the AI loose on a folder without worrying about what it changed.