Manus Advanced tutorial

Advanced · step 1 of 7

Decompose and chain

1. Split a big job into steps with a clear output each.
2. Feed each step's output into the next.
3. Check the output between steps, not just at the end.

Why this step matters: Small steps with a checked output each fail visibly and early, instead of one big answer that is wrong somewhere.

Advanced · step 2 of 7

Structured output

Ask for a fixed table or JSON so you can check and reuse it.

Return only JSON: [{"claim": "...", "source_url": "...", "quote": "...", "confidence": "high|medium|low"}]

Why this step matters: A fixed format can be checked by eye or by code and reused without retyping.

Advanced · step 3 of 7

Automation and agents

Manus supports scheduled automations (2 on the free plan). Schedule only tasks you have run by hand at least twice, and have results sent to you for review, not straight to customers.

Why this step matters: Automation repeats mistakes at scale, so you need to know exactly what is run and what is checked.

Advanced · step 4 of 7

Failure modes to watch

• Confident wrong turns early in a long task. Approve the plan.
• Outdated prices from cached pages. Open the source.
• Credit drain from retries on a vague goal.

Why this step matters: Knowing how it typically fails tells you where to look when you review its work.

Advanced · step 5 of 7

Cost control

• Free: 300 daily credits, 1 concurrent task, 2 scheduled automations.
• Pro: from $20/month (4,000 credits) or $40/month (8,000 credits, with a 7-day trial). About 17% off yearly. Up to 20 concurrent tasks.
• Team: from $20 per seat a month or $200 per seat a year. SSO is a $150 add-on for teams under 30 seats.

Source: Manus Help Center, checked Oct 30, 2026.

Free: 300 daily credits and 1 concurrent task. Pro: 4,000 or 8,000 monthly credits and up to 20 concurrent tasks (Manus Help Center).

Why this step matters: Paying for features you don't use is the most common waste. Knowing the limits first tells you if the free tier is enough.

Advanced · step 6 of 7

Privacy and team rules

• Don't paste passwords, ID numbers, card numbers or other people's private details.
• Assume the company can read and keep your chats unless its official policy says otherwise.
• For health, money or legal decisions, confirm with a professional or an official source.
• Never give the agent your passwords or card details. If a site needs a login, do that step yourself.
• Review files and outputs it creates before sharing them.
• Write down which data is allowed in which tool, and who approves paid plans.

Why this step matters: Anything you paste may be stored and read. Deciding what never goes in is easier than undoing a leak.

Advanced · step 7 of 7

Build a 10-task test set

1. Collect 10 real tasks with known good answers.
2. Run them now and score each pass/fail.
3. Re-run them when the model, plan or your prompt changes.
4. Keep the prompt that wins, not the one that feels better.

Why this step matters: Without a fixed test set, 'better' just means 'felt better'. Scores let you compare prompts and models fairly.