Live data from Hacker News

Schedule tasks on the web

code.claude.com

151–160 of 261 posts

Re: Schedule tasks on the web

#151
post #107

Earlier quoted context omitted.

Funnily, Anthropic's pricing etc. why I'm using GLM-5 a bunch more outside of work. Definitely not Opus level, but surprisingly decent. Though I got lucky and got the Alibaba Coding Model lite plan, which is so cheap they got rid of it

Does GLM-5 have multimodality or are they still wanting you to load an MCP for vision support?

Text only still, sadly, though qwen3.5-plus on the same provider (Model Studio) is

Re: Schedule tasks on the web

#152

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.

“A programmer is going to the store and his wife tells him to buy a gallon of milk, and if there are eggs, buy a dozen. So the programmer goes shopping, does as she says, and returns home to show his wife what he bought. But she gets angry and asks, ‘Why’d you buy 13 gallons of milk?’ The programmer replies, ‘There were eggs!’” You need to write a clearer prompt.

Did GP edit their comment? Or did you read the prompt they used somewhere else?

Re: Schedule tasks on the web

#153

Earlier quoted context omitted.

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 h…

> Or, in short: we need Tasker but for web (and without some of the legacy baggage around UI and variable handling). n8n, node-RED and others already exist. There are many tools for automations, and I guess most of them can also do cron-like jobs.

Node RED is still unwieldy for the masses, as easy as it is for a consumer to install, it’s not necessarily as easy to use.

Consumer grade automations built on node-RED? I suppose it depends on the market, but most people aren’t going to want to fiddle with it, I suspect.

A plugin for Chrome might be able to take off though, or some killer mobile app, but it needs to run on a cheap phone and control things without having to keep track of loops and logic and variables and all the fun stuff.

Re: Schedule tasks on the web

#154

Earlier quoted context omitted.

> Or, in short: we need Tasker but for web (and without some of the legacy baggage around UI and variable handling). n8n, node-RED and others already exist. There are many tools for automations, and I guess most of them can also do cron-like jobs.

Node RED is still unwieldy for the masses, as easy as it is for a consumer to install, it’s not necessarily as easy to use. Consumer grade automations built on node-RED? I suppose it depends on the market, but most people aren’t going to want to fiddle with it, I suspect. A plugin for Chrome might be able to take off though, or some killer mobile app, but it needs to run on a cheap phone and control things without ha…

None of the tools here are for the masses. Automation in itself is already hard to grasp for the average user, and while some of those are simpler to start than others, they all are wall to climb.

Re: Schedule tasks on the web

#155

Oh my, did Anthropic invent Cron jobs as a service? It's a game changer. Edit: my mistake. It's inferior to a Cron job. If my repos happen to be self hosted with Forgejo or codeberg, then it won't even work. If I concede to use GitHub though I don't have to set up any env variables. Schedules lock-in, all over the web.

I built this last year because I thought it was overdue back then already.

https://imgur.com/a/apero-TWHSKmJ

Cron triggers (or specific triggers per connector like new email in Gmail, new linear issue, etc for built in connectors).

Then you can just ask in natural language when (whatever trigger+condition) happens do x,y and z with any configuration of connectors.

It creates an agentic chain to handle the events. Parent orchestrator with limited tools invoking workers who had access to only their specific MCP servers.

Official connectors are just custom MCP servers and you could add your own MCP servers.

I definitely had the most advanced MCP client on the planet at that point, supporting every single feature of the protocol.

I think that's why I wasn't blown away by OpenClaw, I had been doing my own form of it for a while.

I need to release more stuff for people to play around with.

My friends had use cases like "I get too many emails from my kids school I can't stay on top of everything".

So the automation was just asking "when I get an email from my kids school, let me know if there's anything actionable for me in it"

Re: Schedule tasks on the web

#156
post #120

Earlier quoted context omitted.

I just don’t see it coming. I was full on that camp 3 months ago, but I just realize every step makes more mistakes. It leads into a deadlock and when no human has the mental model anymore. Don’t you guys have hard business problems where AI just cant solve it or just very slowly and it’s presenting you 17 ideas till it found the right one. I’m using the most expensive models. I think the nature of AI might block tha…

I think this sounds like a true yet short sighted take. Keep in mind these features are immature but they exist to obtain a flywheel and corner the market. I don’t know why but people seem to consistently miss two points and their implications - performance is continuing to increase incredibly quickly, even if you rightfully don’t trust a particular evaluation. Scaling laws like chinchilla and RL scaling laws (both t…

Scaling laws vs combinatorial explosion, who wins? In personal experience claude does exceedingly well on mundane code (do a migration, add a field, wire up this UI) and quite poorly on code that has likely never been written (even if it is logically simple for a human). The question is whether this is a quantitative or qualitative barrier.

Of course it's still valuable. A real app has plenty of mundane code despite our field's best efforts.

Re: Schedule tasks on the web

#157

Earlier quoted context omitted.

I think this sounds like a true yet short sighted take. Keep in mind these features are immature but they exist to obtain a flywheel and corner the market. I don’t know why but people seem to consistently miss two points and their implications - performance is continuing to increase incredibly quickly, even if you rightfully don’t trust a particular evaluation. Scaling laws like chinchilla and RL scaling laws (both t…

Scaling laws vs combinatorial explosion, who wins? In personal experience claude does exceedingly well on mundane code (do a migration, add a field, wire up this UI) and quite poorly on code that has likely never been written (even if it is logically simple for a human). The question is whether this is a quantitative or qualitative barrier. Of course it's still valuable. A real app has plenty of mundane code despite…

Combinatorial explosion? What do you mean? Again, your experiences are true, but they are improving with each release. The error rate on tasks continues to go down, even novel tasks (as far as we can measure them). Again this is where verifiable domains come in -- whatever problems you can specify the model will improve on them, and this improvement will result in better generalization, and improvements on unseen tasks. This is what I mean by taking your observations of today, ignoring the rate of progress that got us here and the known scaling laws, and then just asserting there will be some fundamental limitation. My point is while this idea may be common, it is not at all supported by literature and the mathematics.

Re: Schedule tasks on the web

#158

Earlier quoted context omitted.

> - coding is a verifiable domain You're missing the point though. "1 + 1" vs "one.add(1)" might both be "passable" and correct, but it's missing the forest for the trees, how do you know which one is "long-term the right choice, given what we know?", which is the engineering part of building software, and less about "coding" which tends to be the easy part. How do you evaluate, score and/or benchmark something like…

because it has business context and better reasoning, and can ask humans for clarification and take direction. You don't need to benchmark this, although it's important. We have clear scaling laws on true statistical performance that is monotonically related to any notion of what performance means. I do benchmarks for a living and can attest: benchmarks are bad, but it doesn't matter for the point I'm trying to make.

> because it has business context

It doesn't because it doesn't learn. Every time you run it, it's a new dawn with no knowledge of your business or your business context

> better reasoning

It doesn't have better reasoning beyond very localized decisions.

> and can ask humans for clarification and take direction.

And yet it doesn't, no matter how many .md file you throw at it, at crucial places in code.

> We have clear scaling laws on true statistical performance that is monotonically related to any notion of what performance means.

This is just a bunch of words stringed together, isn't it?

Re: Schedule tasks on the web

#159

Earlier quoted context omitted.

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.

Honestly, you just need cron (and Ruby/Python/bash/whatever) on an EC2. It's not very fashionable, but it works, will continue to work forever, and costs hardly anything.

To use an example in the article, what does

> Analyzing CI failures overnight and surfacing summaries

Look like on ec2 with python? Because with Claude, it’s that prompt, and with your solution it’s infra + security groups + multiple APIs + whatever code you actually write

Post reply on HN