upvote
Nothing in there is innovative or unattainable, Clop uses open source tools behind the scenes anyway so obviously you can replicate it with scripts.

But this is for people that already use the app, researchers, writers, students, people that aren't necessarily comfortable with a terminal. And given Clop already implements the basics: an efficient file events watcher, tuned encoders for the Mac silicon, fail safe backups and UI for seeing the result and interacting with it in real time, it has advantages over trying to do it yourself.

reply
I'm not intending to denigrate your tool. I'm just commenting on the "look at how we go full circle" aspect.

I will point out that the shell script way uses less resources than an LLM making a tool call. But I understand that these scenarios are not necessarily meant for the same user.

reply
No offense taken, I can see the irony myself :)

Oh for sure, I would prefer to have the automations as invisible things running at the system level, doing exactly what I want and nothing else, not wasting resources on UIs and event watchers I might not need. I would get rid of my own apps if that was easy to do.

But it seems we need to waste some resources to get some usability in return.

reply
This is how engineers end up justifying why my doorbell needs to contact the cloud to confirm it should run when someone is at my door.
reply
I used to do that using the macOS builtin Folder Actions. People forget these exist. Pure GUI.
reply
I had no idea this was a thing: https://developer.apple.com/library/archive/documentation/Ap...

Definitely saving it for further use, I sometimes need to have small invisible watchers and I don't want a full fledged app or shell scripts for that.

reply
That guide seems like an extremely roundabout way of doing things. Just open Automator and use the GUI.
reply