I have very mixed feelings about using Manus.
On one hand, I’m genuinely impressed by its high efficiency and task completion — it can quickly and accurately build product prototypes based on my needs.
On the other hand, when I invited my friends to try it, the system falsely flagged me for “fake referrals” and suspended my account — even though my friends actually subscribed.
I’ve reached out to their support team multiple times, but the issue has never been resolved.
I honestly don’t understand what their support team is doing. No matter how great a product is, poor customer service can easily ruin it.
Manus-built web apps can now run their own scheduled actions. That detail is easy to skim past, but it changes what kind of software Manus can actually produce.
What it is: Scheduled Tasks 2.0 is a system-wide upgrade to recurring work in Manus, covering task continuity, Project configuration inheritance, and embedded scheduling inside Manus-built web apps.
When you build an app with Manus, you are not just generating a static interface. You are building something that could, in principle, maintain itself.
A dashboard that refreshes its own data every morning. A reporting tool that generates its weekly summary without prompting. A client-facing app that sends reminders on a schedule. With this update, those behaviors are configurable inside the app rather than managed externally by the user.
What makes it different: Most agent scheduling tools treat the schedule as something you bolt on from outside. Manus is treating it as something native to the task, Project, or app where the work actually lives. The schedule inherits the context of its environment rather than running in a vacuum.
Key features:
Embedded scheduled actions inside Manus web apps (refreshes, summaries, reminders, script runs)
Same-task continuation mode for recurring work that depends on existing context
Project-level context and configuration inherited by scheduled tasks
Connector support for linked data sources
Skip confirmations for trusted automated pipelines
Calendar, schedule, and history views for run oversight
Benefits:
Apps built with Manus can stay live and updated without the creator manually triggering runs
Recurring analysis and reporting stays coherent across cycles
Easier to manage and audit scheduled work across tasks and Projects
Who it's for: Builders and operators using Manus to create client-facing or internal tools that need to stay current without constant manual input.
A scheduling system embedded in an app-building agent is a different product category than a task scheduler with a cron job underneath. That is the direction Manus is pointing.
P.S. I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified → @rohanrecommends