Manus has rolled out a package of updates that reframe its agent as a persistent operator rather than a one-shot chatbot. The headline pieces are Scheduled Tasks 2.0, a new set of native MCP connectors, and a Chief of Staff template that stitches them together. The pitch is straightforward: hook up your work tools once, teach Manus your preferences, and let it run recurring jobs against the same evolving context.

The Chief of Staff workflow is built on three primitives. According to Manus, you connect tools, encode your preferences as Skills, and put prompts on a schedule. MCP connectors are prebuilt integrations that let Manus read data from an app, perform actions within it, and coordinate workflows across multiple platforms from a single natural language prompt. Authentication runs through OAuth 2.0, the same method used by major platforms, with the user controlling exactly what Manus can access.

What is actually new under the hood

Scheduled Tasks 2.0 is the more interesting half of this release, because it changes how recurring agent work behaves. Run options let users choose whether each run continues in the same task or starts as a separate task. That sounds small, but it is the difference between an agent that wakes up amnesic every morning and one that remembers yesterday's open threads.