OpenAI launches scheduled tasks feature in ChatGPT
AI-assisted, source-derived brief produced by the Let's Data Science Automated News Desk. The source material used is linked on this page.
- Source event:
- first reported
- LDS brief:
- publication time is not available in the public LDS lifecycle record
The shift worth noting is architectural: ChatGPT is moving from a thing you talk to into a thing that runs work in the background, with guardrails that define what it is good for. On June 17, 2026, OpenAI launched scheduled tasks, adding a dedicated Scheduled page in the sidebar where users create, pause, edit, and delete one-off and recurring tasks, or set up monitoring that notifies them on meaningful changes. Per OpenAI's help article and 9to5Mac, scheduled checks are capped at once per hour, tasks created inside a project cannot access that project's files, and unattended tasks may auto-pause after inactivity; the system replaces Pulse within 14 days and rolls out to Go, Plus, Pro, Business, and Enterprise users on web and mobile. For builders, the hourly cap and project-file isolation are the load-bearing constraints that decide which workflows fit.
Why it matters for builders
The feature itself is straightforward; the design choices are the signal. By capping scheduled checks at once per hour, isolating tasks created in a project from that project's files, and auto-pausing unattended tasks, OpenAI is positioning scheduled tasks as a lightweight reminder-and-monitoring layer rather than a real-time polling or data-pipeline engine. That makes it a poor fit for latency-sensitive or high-frequency monitoring, and a reasonable fit for daily digests, periodic checks, and recurring reminders. For teams, the practical work is matching workflows to those guardrails and watching whether OpenAI later exposes task controls via an API.
What happened
OpenAI launched a scheduled tasks feature in ChatGPT on June 17, 2026, according to its help article and coverage by 9to5Mac. The product adds a dedicated Scheduled page in the sidebar where users can view active tasks and pause, resume, edit, or delete them, and can create one-off or recurring tasks either from the page or by asking ChatGPT directly. OpenAI's help article notes that tasks created within a project will not be able to access that project's files.
The constraints
OpenAI's documentation and 9to5Mac describe the operating limits: scheduled checks run at most once per hour, unattended tasks may automatically pause after a period of inactivity, and mobile push or desktop notifications require platform permissions that ChatGPT prompts for after the first task. 9to5Mac reports the new system replaces Pulse within 14 days and that the rollout covers Go, Plus, Pro, Business, and Enterprise users across web and mobile.
Context
Folding recurring actions and monitoring into a conversational assistant mirrors a broader product trend toward assistant-driven automation. Vendors adding this kind of background tasking typically pair it with frequency limits, permission prompts, and access controls to manage privacy, scale, and notification fatigue - which is exactly the shape of OpenAI's guardrails here.
What to watch
Watch for any API or developer surface for creating and auditing tasks, admin and enterprise controls for logging and data residency given the Business and Enterprise rollout, the Pulse removal timeline, and how reliably notifications behave across platforms as availability widens.
Key Points
- 1WHAT: OpenAI launched ChatGPT scheduled tasks (June 17, 2026) with a dedicated Scheduled page for one-off, recurring, and monitoring tasks, replacing Pulse.
- 2WHY: Hourly execution caps, project-file isolation, and auto-pause on inactivity define a low-frequency automation tool, not a polling engine.
- 3SO-WHAT: Teams should design around the once-per-hour limit and data-access boundaries, and watch for any API exposure of task controls.
Scoring Rationale
A notable product update that moves ChatGPT from conversational assistance toward background automation and monitoring, replacing Pulse. It matters to teams designing assistant workflows because of the hourly execution cap and project-file isolation, but it is not a frontier-model or infrastructure change, so it sits mid-range.
Sources
Public references used for this report.
Practice interview problems based on real data
1,625 SQL & Python problems across 15 industry datasets — the exact type of data you work with.
Try 250 free problems