I'm surprised it took OpenAI this long to launch scheduled tasks, but as we've seen from our users[0], pure LLM-based responses are quite limited in utility.
For context: ~50% of our users use a time-triggered Loop, often with an LLM component.
Simple stuff I've used it for: baby name idea generator, reminder to pay housekeeper, pre-natal notifications, etc.
We're moving away from cron-esque automations as one of our core-value props (most new users use us for spinning up APIs really quickly), but the base functionality of LLM+code+cron will still be available (and migrated!) to the next version of our product.
> None of these require an LLM. It seems like you own this service yet can't find any valuable use for it.
Sorry? My point was that these are the only overlapping features I've personally found useful that could be replaced with the new scheduled tasks from ChatGPT.
Even these shouldn't require an LLM. A simple cron+email would suffice.
The web scraping component is neat, but for my personal use-cases (tide tracking) I've had to use LLM-generated code to get the proper results. Pure LLMs were lacking in following the rules I wanted (tide less than 1 ft, between sunrise and sunset). Sometimes the LLM would get it right, sometimes it would not.
For our customers, purely scheduling an LLM call isn't that useful. They require pairing multiple LLM and code execution steps to get repeatable and reliable results.
> ChatGPT tasks will become a powerful tool once incorporated into GPTs.
> Baby name generator: why would this be a scheduled task? Surely you aren't having that many children... :)
So far it's help name two children :) -- my wife and I like to see the same 10 ideas each day (via text), so that we can discuss what we like/don't like daily. We tried the sift through 1000 names thing and it didn't fit well with us.
> Reminder to pay, notifications: what value does OpenAI bring to the table here over other apps which provide calendar / reminder functionality?
That's exactly my point. Without further utility (i.e. custom code execution), I don't think this provides a ton of value at present.
For context: ~50% of our users use a time-triggered Loop, often with an LLM component.
Simple stuff I've used it for: baby name idea generator, reminder to pay housekeeper, pre-natal notifications, etc.
We're moving away from cron-esque automations as one of our core-value props (most new users use us for spinning up APIs really quickly), but the base functionality of LLM+code+cron will still be available (and migrated!) to the next version of our product.
[0]https://magicloops.dev/