Live data from Hacker News

Schedule tasks on the web

code.claude.com

91–100 of 261 posts

Re: Schedule tasks on the web

#91

I do feel people will end up using this for things where a deterministic rule could be used - more effective, faster and cheaper. See this starting to happen at work...'We need AI to solve X....no you don't"

I'd say that's almost fine if they can start expressing intent correctly and thinking what good looks like. They (or some automated thing if you're building "think for them" type of products instead of "give them tools and teach them to think how to use them") can then freeze determism more and more were useful

I wrote this to help people (not just Devs) reason about agent skills

https://alexhans.github.io/posts/series/evals/building-agent...

And this one to address the drift of non determism (but depending on the audience it might not resonate as much)

https://alexhans.github.io/posts/series/evals/error-compound...

Re: Schedule tasks on the web

#92

I do feel people will end up using this for things where a deterministic rule could be used - more effective, faster and cheaper. See this starting to happen at work...'We need AI to solve X....no you don't"

AI will become this colleague who sucks at everything, but never says no, so he becomes the favorite go-to person.

Re: Schedule tasks on the web

#93

I remember when I tried to set something up with the ChatGPT equivalent like "notify me only if there are traffic disruptions in my route every morning at 8am" and it would notify me every morning even if there was no disruption.

Why not set your own evals and something like pi-mono for that? https://github.com/badlogic/pi-mono/

You'll define exactly what good looks like.

Re: Schedule tasks on the web

#94

Earlier quoted context omitted.

Maybe. The problem of "execute task on a cron" is something I've noticed the industry seems to refuse to solve in general, as if intentionally denying this capability for regular people. Even without AI, it's the most basic block of automation, and is always mysteriously absent from programs and frameworks (at least at the basic level). AI only makes it more useful on "then" side, but reliable cron on "if" side is al…

Agree. How would you solve this in general, what would be the ingredients? People use things like zapier, n8n, node-red to achieve this today but in many cases are overkill.

I'd start with solving the UX issues, specifically expectations and UI around scheduling jobs.

Expectations - the functionality of "do X on a timer" needs to be offered to users as a proper end-user feature[0], not treated as a sysadmin feature (Windows, Linux) or not provided at all (Android). People start seeing it on their own devices, they'll start using it, then expecting it, and the web will adjust too[1].

UI - somehow this escapes every existing solution, from `cron` through Windows timers to any web "on timer" event trigger in any platform ever. There already exists a very powerful UI paradigm for managing recurring tasks, that most normies know how to use, because they're already using it daily at work and privately: a calendar. Yes, that thing where we can set and manage recurring events, and see them at a glance, in context of everything else that's going on in our lives.

--

I know those are hard problems, but are hard mostly because everybody wants to be the fucking one platform owning users and the universe. This self-inflicted sickness in computing is precisely why people will jump at AI solutions for this. Why I too will jump on this: because it's easier than dealing with all the systems and platforms that don't want to cooperate.

After all, at this point, the easiest solution to the problems I listed above, and several others in this space, would be to get an AI agent that I can:

1) Run on a cron every 30 minutes or so (events are too complicated);

2) Give it read (at minimum) access to my calendar and todo lists (the ones I use, but I'm willing to compromise here);

3) Give it access to other useful tools

Which I guess brings us to the actual root problem here. "Run tasks on a cron" and "run tasks on trigger" are basically just another way of saying unattended/non-interactive usage. That is what is constantly being denied end users.

This is also the key to enabling most value of AI tools, too, and people understand it very well (see the popularity of that Open Claw thing as the most recent example), but the industry also lives in denial, believing that "lethal trifecta" is a thing that can be solved.

--

[0] - This extends to event triggers ("if X happens, then") automation, and end-user automation in all of every-day life. I mean, it's beyond ridiculous that the only things normal people are allowed to run automatically are dishwasher, and a laundry machine (and in the previous era, VCRs).

[1] - As a side effect, it would quickly debullshitify "smart home" / "internet of things" spaces a lot. The whole consumer side of the market revolves around selling people basic automation capabilities - except vendor-locked, and without the most useful parts.

Re: Schedule tasks on the web

#95
post #22
post #11

i'm missing something basic here .... what does it actually do? It executes a prompt against a git repository. Fine - but then what? Where does the output go? How does it actually persist whatever the outcome of this prompt is? Is this assuming you give it git commit permission and it just does that? Or it acts through MCP tools you enable?

MCP tools. We're doing some MCP bundling and giving it here, pretty cool stuff.

wasn't MCP a critical link in the recent litellm attack?

Re: Schedule tasks on the web

#96

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

Haha sure, let's just let every user add their feedback to the software.

Re: Schedule tasks on the web

#97

I feel like we are just inching closer and closer to a world where rapid iteration of software will be by default. Like for example a trusted user makes feedback -> feedback gets curated into a ticket by an AI agent, then turned into a PR by an Agent, then reviewed by an Agent, before being deployed by an Agent. We are maybe one or two steps from the flywheel being completed. Or maybe we are already there.

Users are often incorrect about what the software should actually be doing and don’t see the bigger picture.

Re: Schedule tasks on the web

#98

Earlier quoted context omitted.

Maybe. The problem of "execute task on a cron" is something I've noticed the industry seems to refuse to solve in general, as if intentionally denying this capability for regular people. Even without AI, it's the most basic block of automation, and is always mysteriously absent from programs and frameworks (at least at the basic level). AI only makes it more useful on "then" side, but reliable cron on "if" side is al…

I don’t recall if IFTTT had/has a basic cron or not, but it sure has/had put a lot of basic automations in the hands of the general public. Same for Apple Shortcuts, to some extent, or Zapier.

This is a larger topic that's worthy of a comparably large rant, which I really don't want to do right now, but to keep it short, in my subjective view:

- IFTTT was great when it started; at some point, it became... weird, in a "I don't even know what's going on on my screen, is this a poster or an app" kind of way.

- Zapier is an unpenetrable mess, evidently targets marketers and other business users; discovery is hard, and even though it seems like it has everything, it - like all tools in this space - is always missing the one feature you actually need.

- Yahoo Pipes, I heard they were great, but I only learned about them after they shut down.

- Apple Shortcuts - not sure what you can do with those, but over the years of reading about them in HN comments, I think they may be the exception here, in being both targeting regular users and actually useful.

- Samsung Modes and Routines - only recently becoming remotely useful, so that's nice, even if vendor-restricted.

- Tasker - an Android tool that actually manages to offer useful automation, despite the entire platform/OS and app ecosystem trying its best to prevent it. Which is great, if your main computer is a phone. It sucks in a world of cloud/SaaS, because it creates a silly situation where e.g. I could nicely automate some things involving e-mail and calendars from Tasker + FairEmail, but... well my mailboxes and calendars lives in the cloud so some of that would conflict with use of vendor (Fastmail) webapp or any other tool.

Or, in short: we need Tasker but for web (and without some of the legacy baggage around UI and variable handling).

The sorry state of automation is not entirely, or even mostly, the fault of the automation platforms. I may have issues with some UI and business choices some of these platforms made, but really, the main issue is that integrations are business deals and the integrated sides quickly learned to provide only a limited set of features - never enough to allow users to actually automate use of some product. There's always some features missing. You can read data but not write it. You can read files and create new files but not edit or delete them. You can add new tasks but can't get a list of existing ones. Etc.

It's another reason LLMs are such a great thing to happen - they make it easy (for now) to force interoperability between parties that desperately want to prevent it. After all, worst case, I can have the LLM operate the vendor site through a browser, pretending to be a human. Not very reliable, but much better than nothing at all.

Re: Schedule tasks on the web

#100

I do feel people will end up using this for things where a deterministic rule could be used - more effective, faster and cheaper. See this starting to happen at work...'We need AI to solve X....no you don't"

Standard pendulum swing. Most people want to disengage their thinking circuits most of the time, so problems can't be evaluated one by one. There is no such thing as "this is a good solution for some problems". It can only be "this is a good solution for all problems". When the pendulum swings this far, this hard, it will swing all the way back eventually.
Post reply on HN