Skip to content
AI Primer
release

Manus introduces Scheduled Tasks 2.0 with task continuation and self-updating web apps

Manus upgraded scheduled work so recurring jobs can continue inside the same task and drive background updates in Manus-built web apps. That matters because long-lived automations can retain context between runs instead of rebuilding state each time.

2 min read
Manus introduces Scheduled Tasks 2.0 with task continuation and self-updating web apps
Manus introduces Scheduled Tasks 2.0 with task continuation and self-updating web apps

TL;DR

  • Manus says Scheduled Tasks 2.0 now lets recurring jobs continue inside the same task, rather than starting fresh each time, according to ManusAI's launch thread.
  • The bigger product twist is that scheduled work can now drive background actions in Manus-built web apps, as testingcatalog's summary and the linked Manus blog post both describe.
  • Manus also added clearer visibility into upcoming and past runs, a change the official thread framed as better observability for ongoing work.
  • The rollout is live for every Manus account, per ManusAI's blog-link post.

You can read the official post, watch ManusAI's demo thread for the task flow, and testingcatalog's clip is the clearest quick look at the new scheduled-task UI, including the progress view and web-app angle.

Task continuation

Manus is repositioning scheduling from a cron-style trigger into a long-lived task primitive. In ManusAI's launch thread, the company says recurring work can now "continue in the same task," which implies the system keeps prior context attached to later runs instead of rebuilding the workflow from scratch.

That is the main functional change in this release. The official framing in the linked blog post matches the tweet language almost exactly: right time, right place, right context.

Web apps

The most interesting new surface is scheduled background work for apps generated inside Manus. testingcatalog's post says Scheduled Tasks 2.0 introduces web apps that can self-update their data on a schedule, while ManusAI's thread describes the same feature as background actions in Manus-built web apps.

That turns scheduled runs into part of an app runtime, not just a reminder or automation layer. For users building dashboards, reports, or monitoring pages in Manus, the update loop now lives inside the app.

Run history and rollout

Manus also bundled a lighter but useful product change: better visibility into both upcoming and past runs. The official announcement calls this out directly, and testingcatalog's video shows a task list view with progress and status, which makes the observability pitch more concrete.

The company says the upgrade is available now to all users in both ManusAI's post linking the blog and the main launch thread.

Share on X