6 comments

  • IntelliAvatar 10 minutes 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.

  • 1shooner 3 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 3 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.
  • jutter 34 minutes 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?

  • Tade0 4 hours ago
    Not to be confused with Tasker for Android:

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

    • schnetzlerjoe 4 hours ago
      No! It's not!!!!
      • netsharc 1 minute 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...

      • farmerbb 2 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)
  • yodon 4 hours ago
    HN hug of death? Can't open the site