I created a tool that’s easy to set up and gives you fast and beautiful web UI and TUI from a single Go binary.
It can serve both as a cron replacement, or just as a cron supplement - let’s say, to version control your cron tasks in a small team. It also has an alert system that allows you to send slack/discord/telegram/email when something bad happens.
I want your feedback. You can help me shape this product into something people will find pleasant to use.
This daemon is copyleft GPL-3.0-or-later - completely free to use.
RunWisp is currently in pre-release phase but is slowly approaching its v1.0 stable release.
Website: https://runwisp.com/
GitHub repo: https://github.com/runwisp/runwisp - feel free to open an issue!
Quick start: https://docs.runwisp.com/getting-started/quick-start/
AI Disclosure
- Design - Hint
- Implementation - Pair
- Testing - Assisted
- Documentation - Pair
- Review - Hint
I hope this doesn’t come off as too harsh, but the text reads as very AI generated, and I think if you rewrote the main text you could do a much better job.
It’s not clear to me why to use it, the pitch today is that it makes failures loud, which is nice, but very poorly described.
The tool itself looks good, but the website looks very “Claude”, especially the text at the top saying “ONE BINARY · LINUX · MACOS · WSL · 25 MB RAM IDLE”
Those are great pros, but are they the guest thing the user should see?
Honestly the first paragraph of the quick start is a much better pitch:
RunWisp is one small Go binary. You list the shell commands you want to run in a runwisp.toml, and RunWisp takes care of the rest — firing jobs on cron, restarting services when they crash, and capturing every line of stdout and stderr so you can go back and look at what happened. There’s a TUI in your terminal and a Web UI in your browser for poking around. No external database, no agent, no sidecar
This tool looks decent, but for me I find nix helps manage the complexity of systemd well
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.
No problem.
The other thing with AI stuff is it conveys very little trust. It’s easy-come easy-go, so it’s hard to tell how much maintenance the owner will has put in or will put into the project.
Scheduling is high risk, so it’s important that it feels safe
Is this vibe-coded?
AGENTS.md, CLAUDE.md, copilot as contributor, an insanely long readme full of tables and emoji for a project that is just a couple of months old, solving a problem nobody who can read a man page has, posted by an account named after the project, with explicit disclosures in the post.
idk it’s unclear
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.
I don’t think so. He has been a developer for at least a decade. I did not find code smell or bad habits. He does cover his code with plenty of tests. Sonarcloud shows very little issues with the code. That is with all original measures and rules in place.
The dev seems to do all the right things including disclaiming the use of AI.
Thank you for the kind words.
Vibe coding would mean writing no lines of code, just words to an LLM. In the disculosure here, that would be generated.
They have Pair in the disclosure, which is about a 50/50 split in code.
@runwisp_com@lemmy.world you have some formatting issues in the disosure, its all on the same line.
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.
How much of this is written by AI?
See disclosure at the bottom - Implementation lists pair.
Thats 50/50 per our rules here.
Looks good, but kind of superfluous if you just use systemd timers, lol
Systemd timers are the modern way of doing it which gives you everything you coded this tool for, logs and whatnot, in the journal.
And you can run them in a web UI like cockpit aswell.
This might be interesting in a business setting but lacks ACLs and user management in general.
It’s probably also quite easy to hack the system with it if you can inject some malicious scripts.
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.
Yes but… Systemd timers are INI-defined tasks and services with unified history and logs, the alerts can be easily added with any alerting system.
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.
But why does it need a cross platform package when systemd is available everywhere? What UX is better than the already existing cockpit?
Or just cron that calls a logger works well enough
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.
