-2
You really should disclose this as AI slop
it seems it has already been
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.. Thank you for taking the time to look at this.
Why did you use Claude to write this comment
😆
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
It'll be abandoned in 6 months
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.
@runwisp_com @lime Psst... it's not a "him", it's a piece of software. 😏
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.
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.
I generally like some things that syatemd gives, but is there an easier way to create timed automations with systemd timers?
with cron, its just a single line with the recurrence pattern and the command. with systemd, you have to create a timer unit file with several lines, a service unit file with several lines, put them in the right directory, reload systemd, enable the timer. timers are not difficult, but much more convoluted than the crontab. if you have to make multiple pairs, or update something in them, it gets old fast.
single line
here's a single line for you which creates a one-shot service+timer in one go, suspending the system in 4 hours:
systemd-run --on-active=4h --unit=suspend-after-4h /usr/bin/systemctl suspend
If you want it to run repeatedly, simply replace --on-active with --on-calendar="*-*-* 04:00:00" for example.
thank you. this creates it, but is there a way to view or edit its current configuration in a similar format? and this is not persisted, is it?
If you inspect the generated timer you see the same format in the OnCalendar line.
What do you mean by persisted? The service and timer will both be there as long as the timer doesn't end. Which it won't in my example.
If you want to copy it for later reference, you can simply copy the files.
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?
is systemd available for windows and mac?
windows, yes: https://learn.microsoft.com/windows/wsl/systemd
for Mac you should probably use macOS's launchd services: https://www.launchd.info/
@WhyJiffie @selfhosted @helix
Just what those systems need to blow themselves away!!!!
Potty please!!
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.
How much of this is written by AI?
See disclosure at the bottom - Implementation lists pair.
Thats 50/50 per our rules here.
this post was submitted on 29 Aug 2026
-2 points (48.2% liked)
Selfhosted
61808 readers
619 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS