Live data from Hacker News

GPT-4o with scheduled tasks (jawbone) is available in beta

chatgpt.com

51–60 of 141 posts

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#51

The beta is inconsistently showing (required a few refreshes to get something to show up), but my limited usage of it showed a plethora of issues: - Assumed UTC instead of EST. Corrected it and it still continued to bork - Added random time deltas to my asked times (+2, -10 min). - Couple notifications didn't go off at all - The one that did go off didn't provide a push notification. --- On top of that, only usable w…

You'd think Open AI's dev velocity and quality would be off the charts since they live and breathe "AI." If a company building ChatGPT itself often delivers buggy features then it doesn't bode well for this whole 'AI will eat the world' notion.

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#52
post #27

Earlier quoted context omitted.

Sure but do they have a moat here? Anyone that can connect to an LLM could make that app.

Yes, they have the name "ChatGPT". For non-technical people this appears to be the most important thing.

Is it a household name? Anecdotally, only two of my five millennial/gen-z siblings use an AI app at all, and one of them calls her's "Gary" instead of ChatGPT. I'd be interested in seeing some actual data showing how much ChatGPT is an actual household name versus one that us technical people assume is a household name due to its ubiquity in our space.

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#53

Where are the release notes? Edit: I suppose they'll be here at some point: https://help.openai.com/en/articles/9624314-model-release-no... These seem like extremely shitty release notes. I have no clue why anybody pays for this model.

You might want this? It's more technical than the one you linked to:

https://platform.openai.com/docs/changelog

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#54
This is the prompt describing the function call parameters:

When calling the automation, you need to provide three main parameters: 1. Title (title): A brief descriptive name for the automation. This helps identify it at a glance. For example, "Check for recent news headlines". 2. Prompt (prompt): The detailed instruction or request you want the automation to follow. For example: "Search for the top 10 headlines from multiple sources, ensuring they are published within the last 48 hours, and provide a summary of any recent Russian military strikes in the Lviv Oblast." 3. Schedule (schedule): This uses the iCalendar (iCal) VEVENT format to specify when the automation should run. For example, if you want it to run every day at 8:30 AM, you might provide:

BEGIN:VEVENT RRULE:FREQ=DAILY;BYHOUR=8;BYMINUTE=30;BYSECOND=0 END:VEVENT

Optionally, you can also include: • DTSTART (start time): If you have a specific starting point, you can include it. For example:

BEGIN:VEVENT DTSTART:20250115T083000 RRULE:FREQ=DAILY;BYHOUR=8;BYMINUTE=30;BYSECOND=0 END:VEVENT

In summary, the call typically includes: • title (string): A short name. • prompt (string): What you want the automation to do. • schedule (string): The iCal VEVENT defining when it should run.

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#55
The UI is different in the desktop app for macOS. The ability to edit the schedule task is only available in the web UI for me.

I got the best results by not enabling Search the Web when I was trying to create tasks. It confuses the model. But scheduled tasks can successfully search the web.

It's flaky, but looks promising!

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#56

The beta is inconsistently showing (required a few refreshes to get something to show up), but my limited usage of it showed a plethora of issues: - Assumed UTC instead of EST. Corrected it and it still continued to bork - Added random time deltas to my asked times (+2, -10 min). - Couple notifications didn't go off at all - The one that did go off didn't provide a push notification. --- On top of that, only usable w…

i posted the system prompt part describing the function call; if you read it and adjust your prompt for creating the task it works way better.

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#57

Where are the release notes? Edit: I suppose they'll be here at some point: https://help.openai.com/en/articles/9624314-model-release-no... These seem like extremely shitty release notes. I have no clue why anybody pays for this model.

The docs for the beta seem to already be up: https://help.openai.com/en/articles/10291617-scheduled-tasks...

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#58
post #47

Earlier quoted context omitted.

Its inevitable. You can argue about what's possible right now, but I'm not looking at it from that angle. I think these issues will be solved with time

That belief is at odds with the mechanics of how LLMs work. It's not a question of more effort/investment/compute/whatever, it's just a reality of how the underlying systems work (non-deterministic). If you can find a way to make the context window on the scale of the human brain, you may be able to mostly mitigate this. People want us to be at "Her" levels of AI, but we're at a far earlier stage. We can fake certain…

Have you tried o1 pro? I find people that are making these assertions are not deeply using the models on a daily basis. With each new release, I can see the increase of capability, and can do things. I have written software in the last year that is at a level of complexity beyond my skill set. I have 15 years of SWE experience, most at FAANG. You just arent close enough to the metal to see what's coming. It's not about what we have now, its about scaling and a reliable march of model improvements. The code has been cracked, given sufficient data, anything can be learned. Neural networks are generalized learners

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#59
post #27

Earlier quoted context omitted.

Yes, they have the name "ChatGPT". For non-technical people this appears to be the most important thing.

Is it a household name? Anecdotally, only two of my five millennial/gen-z siblings use an AI app at all, and one of them calls her's "Gary" instead of ChatGPT. I'd be interested in seeing some actual data showing how much ChatGPT is an actual household name versus one that us technical people assume is a household name due to its ubiquity in our space.

> Is it a household name?

I think it is, yes.

It was interviewed under that name on one of the UK's main news broadcasts almost immediately after it came out. Few hundred million users. Anecdotes about teachers whose students use it to cheat.

But who knows. I was surprising people about the existence of Wikipedia as late as 2004, and Google Translate's augmented reality mode some time around the start of the pandemic.

Re: GPT-4o with scheduled tasks (jawbone) is available in beta

#60
post #47

Earlier quoted context omitted.

That belief is at odds with the mechanics of how LLMs work. It's not a question of more effort/investment/compute/whatever, it's just a reality of how the underlying systems work (non-deterministic). If you can find a way to make the context window on the scale of the human brain, you may be able to mostly mitigate this. People want us to be at "Her" levels of AI, but we're at a far earlier stage. We can fake certain…

Have you tried o1 pro? I find people that are making these assertions are not deeply using the models on a daily basis. With each new release, I can see the increase of capability, and can do things. I have written software in the last year that is at a level of complexity beyond my skill set. I have 15 years of SWE experience, most at FAANG. You just arent close enough to the metal to see what's coming. It's not abo…

Yes, I use LLMs every day. Primarily for coding (a mix of Claude and OAI). I was trying to implement a simple CSS optimization step to my JS framework's build system last night and both kept hallucinating to the point (literally inventing non-existent APIs and config patterns) where I gave up and just did it by hand w/ Google and browsing docs.

The problem with your "close to the metal" assertion is that this has been parroted about every iteration of LLMs thus far. They've certainly gotten better (impressively so), but again, it doesn't matter. By their very nature (whether today or ten years from now), they're a big risk at the business level which is ultimately where the rubber has to hit the road.

Post reply on HN