Am I misreading your docs that Tasker actually does not support running local, and in fact requires using either a Google, Anthropic, or OpenAI service?
One thing I’ve been bitten by with desktop agents is execution-time safety: the plan is correct, but a single malformed path or OS call causes real damage.
Do you enforce any guardrails at the tool boundary (e.g. path sandboxing, network allowlists, dry-run / replay)?
Curious how you’re thinking about this.
The replay feature is similar to the record feature. It's not a "guardrail" I would say though.
All stuff that definitely would be great idea.
I mostly worry about the gap between a correct plan and execution-time behavior — especially when tools touch the filesystem or OS APIs. Even a single malformed argument can have irreversible effects.
Totally agree these guardrails are non-trivial, but it’s great to see the project thinking in this direction.
I'm on Big Sur 11.7.10, which I know is pretty old at this point. The app launches, but it only shows an empty window.
I was also a bit concerned about privacy while running it :)
> I wanna get a job naming kitchen appliances. Seems like the easiest job ever. You know, refrigerator, toaster, blender... You just say what the thing does and then you add '-er'. Kitchen Appliance Naming Institute. "What's this do?" "It keeps shit fresh." "Well, that's a 'fresher'. I'm going on break."
Mitch Hedberg
Appreciate it!
Your post made me think Tasker had branched out to automating actions on desktop computers...
If your app gets popular, good luck sifting through the questions of confused people asking about tasks on Android, and realize that many many Tasker (the original one, see I already have to write in parantheses which Tasker I'm referring too) forum users will be cursing you for naming your app the same as theirs.
Why Tasker is a good name Instantly understandable “Tasker” clearly communicates automation, jobs, actions, workflows Zero explanation needed — huge plus for a consumer + SMB product Broad enough to scale Works for: Desktop agent Cloud cron jobs HTTP-triggered automations AI agents running tasks for sales, ops, HVAC estimates, etc. Doesn’t lock you into just AI or just workflows Matches your positioning Given what you’ve built: non-technical, consumer-friendly automation powered by AI Tasker fits that perfectly — especially compared to over-clever AI names.
I think that answers your question lmao
Plus what I said about the potential confusion of users?
In another reply above you said "...if I were to take it seriously".. God fucking damnit, add this to my 2026 resolutions: ignore people putting up vibe-coded slop onto Show HN.
It's New Years Day. You seem to have a lot of anger.
I'm here for you if you need to talk. I support you!!!
It is opening for me, maybe DNS stuff although its been up for a month. https://automatewithtasker.com or https://github.com/pitalco/tasker if that does not work.
Are you willing to expand more on the meltdown? Coming to terms with being a grown up? Did your marriage survive?
Unless they got a trademark, he’s good to go.
Lmfaooooo on the meltdown. No probably not considering I have been one for longer. And so far it has. Time will be the real tell so I've heard.