Show HN: Tasker – An open-source desktop agent for browser and OS automation

21 pointsposted 11 hours ago
by schnetzlerjoe
(automatewithtasker.com)

24 Comments

conception

an hour ago

I want this but it runs in its own session- like screen or terminal server- so i can keep using the computer and just check in on the automation from time to time.

Agent_Builder

2 hours ago

We ran into similar issues while building GTWY. Once agents can touch real systems, the main challenge becomes limiting what they’re allowed to do per step. Clear boundaries mattered more than adding more automation.

1shooner

9 hours ago

>Your data never leaves your computer. Tasker runs entirely on your machine for maximum privacy.

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?

schnetzlerjoe

9 hours ago

Technically it can run any OpenAI schema open source LLM through Fireworks or Groq or whatever. But you are right I should probably make that clearer.

IntelliAvatar

6 hours ago

This looks great.

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.

schnetzlerjoe

5 hours ago

Phenomenal questions. Sandboxing would be a PHENOMENAL idea. And allowlist it currently is capable of this but does require code changes so configuration based would probably be more what you are referring to?

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.

IntelliAvatar

3 hours ago

Makes sense, thanks for the clarification.

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.

Tade0

10 hours ago

Not to be confused with Tasker for Android:

https://tasker.joaoapps.com/index.html

schnetzlerjoe

9 hours ago

No! It's not!!!!

farmerbb

8 hours ago

I'd recommend you change the name of your project sooner rather than later, Tasker is a well established app in the Android power user community for automating various tasks (albeit without AI)

schnetzlerjoe

5 hours ago

Yeah probably if I were to take it seriously! Thanks for the rec

blackqueeriroh

5 hours ago

You’re fine, trust me. Mac and android apps that do different things often have the same names.

schnetzlerjoe

4 hours ago

Yeah I know and agree. I use like dozens of tools with same names, many very similar products. But those that are genuinely confused and provide feedback I appreciate. Those that are hostile that just seem to follow "misery loves company", I like to be sarcastic with. Seems to be a win win with both sides (I can be a smart ass).

Appreciate it!

netsharc

5 hours ago

I guess you didn't ask your AI if "Tasker" is a good name, or your AI doesn't know enough to answer that Tasker is a very well-known app that does what you describe, on Android.

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.

schnetzlerjoe

5 hours ago

No I guess not. I just asked it. Your answer:

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

blackqueeriroh

5 hours ago

It’s great and I love it and don’t change the name!

netsharc

4 hours ago

OK, since you've apparently delegated all thinking to AI ("lmao"), can you ask it this: "What if there's already an established app called Tasker for Android"

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.

schnetzlerjoe

4 hours ago

I asked it if people still understand sarcasm and humor in 2026 since it's doing all my "thinking" for me! You would not like the answer.

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!!!

jutter

6 hours ago

How on earth did you manage to get this far before learning of the Android app by the same name? You can't call this Tasker.

Are you willing to expand more on the meltdown? Coming to terms with being a grown up? Did your marriage survive?

blackqueeriroh

5 hours ago

He can absolutely call this Tasker. There are a bunch of apps with the same name. Tasker on Android doesn’t have a macOS version.

Unless they got a trademark, he’s good to go.

schnetzlerjoe

5 hours ago

I knew about it. I just did it for fun and me and my father so did not care enough. You can name it whatever you would like.

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.