actually not harsh

this is exactly the kind of concrete feedback I was hoping for. You’re right that the quick-start paragraph explains the actual value better than the current pitch… I should lead with that, then treat the binary size and platform support as supporting details rather than the headline.

Thank you for taking the time to look at this.

Thank you for the kind words.

yeah, thats fair, systemd + cockpit with alerts can cover pretty much the same ground. What RunWisp brings is the integrated cross-platform package and UX. Nobody is claiming that those underlying capabilities are impossible to assemble elsewhere.

if cron + logger covers your needs, you should keep that going. RunWisp is for cases where you also want searchable run history with retention and rotation, failure alerts, manual triggering and service supervision, all in one place without assembling those pieces yourself.

If systemd timers, journald and cockpit already cover your needs, RunWisp probably isnt for you. RunWisp is aimed at people who want portable TOML-defined tasks and services with unified history, logs and alerts. you’re right that ACLs are currently missing, but access is protected by password authentication and the UI can only trigger commands already defined on the host.

Copilot was listed as a contributor on an early commit because I used it to help draft that commit. that attribution overstates its role in the overall project. The disclosure in the post is the more accurate summary of how AI was used.

no. I am an experienced engineer that has been writing code for more than 10 years, way before AI. While AI definitely has been used to write code, the code architecture is actively designed and reviewed by me, a human.