Manus Mastery — Autonomous Agents That Finish the Job

Week 1 — meet the tool, get an account, and learn the screen before you learn the prompting.

1. Meet Manus — what it is and who makes it

   Manus is Manus's general autonomous agent that plans, browses, builds and delivers a result. It is at its best at a task with a finish line that can be reached by doing many small steps — research, comparison, a document, a small site. It is at its weakest at knowing when to stop, and at any task where you cannot say in one sentence what a good result looks like — and knowing both halves is what separates somebody who uses it well from somebody who trusts it blindly.

   The lesson

   Manus is a general autonomous agent that plans, browses, builds and delivers a result made by Manus. The models behind it are a set of frontier models orchestrated by a planning loop with a browser and a code sandbox. None of that matters on its own — what matters is that you know what kind of worker you have hired. At a task with a finish line that can be reached by doing many small steps — research, comparison, a document, a small site is the job you hand it. At knowing when to stop, and at any task where you cannot say in one sentence what a good result looks like is the job you keep.

   Most people come to a course like this expecting a list of magic words. There is no such list. What there is, is a tool that produces a delivered artefact — a report, a spreadsheet, a small site, a set of files — rather than an answer, and produces it at a speed no human matches — which means the skill is not in writing the prompt, it is in knowing what a good answer looks like so you can tell the difference.

   Here is the first thing to try, worded the way you will word things for the rest of the course:

   PromptCopy

   I need to choose a laptop under a fixed budget. Write the plan first and show it to me before doing any research, then compare five options with a source and a date on every price, and mark anything you cannot find as NOT FOUND.

   Read the answer twice. The first read is for the content; the second is for the shape — did it answer the question you asked, or the question it found easiest? That second read is the habit this whole course is built on.

   Example A plan before the work, and an explicit instruction to leave a gap rather than fill it — the two habits that make an autonomous run safe.

   Practice Open Manus, ask it the one question you would normally put to a search engine about your own field, and write down two things: whether the answer was right, and whether it would have taken you longer to find it yourself.

2. Signing in: what is free, what is paid, and what you actually need

   You do not need the paid plan to finish this course. Start on the free tier — a limited free allowance of daily credits, enough to learn the briefing technique. Upgrade only when you hit a wall you can name: a longer file, a newer model, or a rate limit you keep meeting.

   The lesson

   Every one of these tools has a free tier that is good enough to learn on and a paid tier that removes a limit. paid plans add credits, faster runs and more concurrent tasks. The mistake is buying the paid plan in week one, before you know which limit you hit — you end up paying to remove ceilings you were never going to touch.

   Work out your own honest usage first. How many questions a day do you actually ask? How big are the files you upload? Do you need the newest model, or the fast one? For revision, for drafting, for coursework, the answer is usually the free tier.

   If your college or workplace provides an account, use it: a team plan with shared outputs is how most people in a job get access, and asking your placement cell whether one exists costs nothing.

   Example The free allowance is best spent on two well-briefed tasks rather than ten vague ones.

   Practice Create the account, find the plan page, and write down in one line which limit you would hit first in your own week. It is usually a message cap or a file-size cap, not the model.

3. The screen: where every control lives

   A tour of the interface you will live in — a chat with an attached workspace: the agent shows its plan, its steps, the files it makes, and a result panel you can download from. Every panel has a reason to exist, and half of them are the difference between a chat and a system.

   The lesson

   The interface of Manus is a chat with an attached workspace: the agent shows its plan, its steps, the files it makes, and a result panel you can download from. That sentence is worth slowing down on, because the single biggest cause of bad output is not a bad prompt — it is a good prompt typed into the wrong place.

   The history list is your memory of what worked. Name your conversations. The temporary or private mode is for anything you would not want in an account's history. The settings panel holds the personal instructions that apply to everything, which is where your context belongs rather than repeated at the top of every message.

   Do this once, properly: write one brief and watch the plan it produces before it starts. If the plan is wrong, correcting it there costs ten seconds.. It takes fifteen minutes and saves you those fifteen minutes every week after.

   Example The step list is the part to watch — it is where you see the agent misunderstand the task, before it spends twenty minutes working from the wrong idea.

   Practice Spend fifteen minutes doing nothing but clicking. Open every panel, rename one conversation, and save one setting you will want again. Fluency with the screen is what stops you re-explaining yourself every session.

Week 2 — how Manus reads text, the four-part prompt, your own work, and what to do when the answer is wrong.

1. How Manus reads what you type

   Context, instructions and roles. It keeps the whole task in view and works across many turns, so your brief is the only thing constraining it for the length of the run. Understanding what the model can see — and what it has already forgotten — explains almost every disappointing answer you will get.

   The lesson

   It keeps the whole task in view and works across many turns, so your brief is the only thing constraining it for the length of the run. This is the machinery. A model does not remember your last conversation the way a person does; it is handed text and asked to continue it well. Everything you want it to know has to be in that text, in the same window.

   There is a difference between a system instruction — the standing context, set once — and a message, which is this request. Put your standing context in the standing place. "I am a final-year mechanical engineering student applying for data roles" belongs in your profile, not typed again at the start of every chat.

   And there is a hard limit. When a conversation gets long enough, the earliest turns fall out of view. Symptoms: it contradicts an instruction you gave ten messages ago, or forgets the file you uploaded. The fix is a new conversation with a written summary of where you got to, not a longer argument.

   Example A brief that says "compare the four cheapest options and cite each price" produces a table; a brief that says "research laptops" produces a page of prose you cannot use.

   Practice Ask the same question twice: once on its own, once after a short paragraph of setup about who you are and what you need. Compare the two answers and write down the difference. That gap is the thing you are learning to control.

2. The four-part prompt: role, task, context, format

   Almost every good prompt has four parts: who the model should be, what it must do, the facts it must use, and the shape of the answer you want. Leave out the fourth and you get an essay when you wanted a table.

   The lesson

   Write the four parts as four lines, in this order. ROLE: who it should answer as. TASK: the single thing you want done, as an instruction, not a wish. CONTEXT: the facts, pasted, not referred to. FORMAT: the exact shape of the answer — "a table with three columns", "five bullets, no more than twelve words each".

   FORMAT is the part everybody skips and the part that saves the most time. An answer you have to restructure by hand was not really an answer. Ask for the shape you are going to use: if it is going into a slide, ask for slide bullets; if it is going into a spreadsheet, ask for rows.

   Here is the same request done both ways — first as people usually write it, then in four parts:

   PromptCopy

   Weak:  tell me about data analyst jobs
   
   Strong:
   ROLE:    A hiring manager for entry-level analytics roles in India.
   TASK:    List what you screen for in a fresher's first 30 seconds.
   CONTEXT: I am a 2026 B.Com graduate with Excel, basic SQL and one
            dashboard project. No internship yet.
   FORMAT:  A table: skill | what a fresher shows | what most get wrong.
            Five rows maximum. No introduction.

   The second prompt is not longer because long is good. It is longer because it contains four things the model cannot guess, and the guess is where the useless answer came from.

   Example "Stop and check with me after the outline" turns an autonomous run into a collaboration, which is the single most useful instruction in this course.

   Practice Take a task you did last week without AI and write the prompt in four labelled lines. Then run it, and rewrite only the part that failed — not the whole prompt.

3. Manus for the work you actually have

   Assignments, revision, email, applications, meeting notes. A comparison table with sources, a research pack on a topic, a small one-page site, a data file cleaned into a fixed format. The test of a tool is whether it removes an hour from your week, not whether the demo looked clever.

   The lesson

   The highest-value use of Manus for a student or a fresher is not writing essays. It is compression: turning a 40-page chapter into the six things you actually have to remember, turning a messy set of notes into a revision sheet, turning a job description into a list of what to prove.

   The second highest is structure: given a blank page, ask for three possible outlines and pick one. Being stuck is usually a problem of options, not of effort.

   Here is a prompt worth keeping verbatim — it is the one that turns a document into something you can study:

   PromptCopy

   TASK      Build a comparison table of [5 options] for [a stated need].
   
   DELIVERABLE
     A table: name, price, key spec, what it is bad at.
     Plus three paragraphs: which one I should pick, and what would change
     your answer.
   
   SOURCES
     Manufacturer pages and at least two independent reviews.
     Cite every price with the URL and the date you saw it.
   
   CONSTRAINTS
     Budget under [amount]. Available in India. No discontinued models.
   
   STOP RULE
     Stop after the outline and show it to me before doing the research.
     If a price cannot be found, write NOT FOUND rather than estimating.

   Notice the last line. Asking for the gaps is asking the tool to mark its own work, and it is the single most useful line you can add to a study prompt: the material it could not summarise is the material you have not understood yet.

   Example Write the deliverable, the constraints, the sources allowed and the stopping rule into one brief.

   Practice Pick the one task you repeat every week — the one that is boring rather than hard — and rebuild it in Manus today. Time it. Then keep the prompt that worked, saved and named.

4. When the answer is wrong: iterate instead of restarting

   A bad answer is information. The failure is confident effort in the wrong direction, and quiet invention where a fact could not be found. Keep the conversation, name the fault, and correct one thing at a time — restarting from scratch throws away everything the model has already got right.

   The lesson

   There are four things that usually went wrong, and each has a different fix. It answered a different question — restate the TASK as one sentence. It made things up — supply the facts yourself and say "use only these". It wrote too much — ask for the length first. It sounded like a machine — ask it to rewrite for one specific reader and cut every third word.

   Say the fault out loud, in the message. "This is too long for a WhatsApp message and it sounds like a brochure." A model cannot fix a problem you have not named, and naming the problem is also how you find out what you actually wanted.

   Follow-ups that work: "shorter", "only the parts that are true for a fresher", "rewrite the second sentence three ways", "what would you have to check before I send this?". That last one is worth using before anything goes out with your name on it.

   Example If a figure appears with no source, ask which page it came from. An agent that cannot cite has guessed, and the guess is usually plausible.

   Practice Take the worst answer you have received this week and correct it in three follow-up messages without retyping the original prompt. Notice how much faster it converges.

Week 3 — documents and tables, The brief, the plan, and a delivered artefact, the API, and one boring task automated.

1. Files, tables and long documents

   Uploading a PDF, a spreadsheet or a screenshot and asking questions about it: It produces files you can download, and it can work from files you upload — a spreadsheet in, a cleaned spreadsheet out. This is where these tools stop being a chat and start being work, and where the failure modes are worth knowing.

   The lesson

   It produces files you can download, and it can work from files you upload — a spreadsheet in, a cleaned spreadsheet out. The two failures to expect are the ones nobody warns you about: a long document is summarised as it is read, so a detail on page 60 can be missed; and a table with merged cells or a scanned page is likely to be read wrongly.

   So the working method is: ask narrow questions, and ask the tool to quote the line it is answering from. "From the attached file only, what does clause 4.2 let me do? Quote the sentence." If it cannot quote it, it did not read it.

   For a spreadsheet, ask for the formula and an explanation instead of the computed column — require a source next to every number, since the agent will otherwise fill gaps — then you can fix it yourself next month when the columns change.

   Example Upload a messy list of forty companies and get back the same list with a website, a sector and a source for each.

   Practice Upload one real document you already own — a syllabus, a marksheet, a project report — and ask three questions whose answers you already know. When it gets one wrong, read the passage it quoted before you blame the file.

2. The brief, the plan, and a delivered artefact — Manus's own feature

   You give it a task rather than a question. It writes a plan, runs it with a browser and a code sandbox, and hands back files. The skill is the brief and the stopping rule, not the prompting.

   The lesson

   Because this is the shape of the work that is actually being delegated now: not "write me a sentence" but "go and find out, and bring back a table". Knowing how to brief and audit that work is a management skill as much as a technical one.

   Write five labelled lines: task, deliverable, sources, constraints, stopping rule. Ask for the outline before the research. Then audit — open the sources, check the numbers, and read the reasoning for the recommendation. Keep the brief; it is reusable for the next comparison.

   Here is the shape of it, in the form you will actually use:

   Plain textCopy

   THE FIVE-LINE BRIEF (reuse this for any delegated task)
   
   TASK          one sentence, with a verb: "build a comparison table of ..."
   DELIVERABLE   the exact artefact and its shape
   SOURCES       what it may use, and that every number needs a URL and a date
   CONSTRAINTS   the limits that rule options out
   STOP RULE     when to stop — "show me the outline before researching",
                 or "stop if two sources disagree on a price"
   
   AUDIT, after it finishes
     1. Open two sources at random and check the number on the page.
     2. Find one NOT FOUND and decide whether you can live without it.
     3. Read the recommendation paragraph and ask: does the evidence
        in the table actually support this?
   
   Step 3 is the one that catches a confident agent. The table is usually
   right; the conclusion drawn from it is where the invention hides.

   The mistake is running an agent for an hour and reading only the summary at the end. The invention is in the details, and the details are what somebody will check.

   Example A one-page brief produces a comparison spreadsheet with sources, a short recommendation and the reasoning behind it — in twenty minutes, unattended.

   Practice Write one brief with a stopping rule, ask for the outline first, correct the outline, then let it run and check every number it produced.

3. Where this fits next to a chat window and your first script

   Autonomous agents are offered as products rather than raw endpoints, and the same planning loop can be built on any provider's API with tool calling. You do not need this to finish the course, and you do not need it for a fresher job either — but an afternoon here is what turns "I have used Manus" into "I have built with it", which is a different sentence in an interview.

   The lesson

   Autonomous agents are offered as products rather than raw endpoints, and the same planning loop can be built on any provider's API with tool calling. The idea is simple: the same model you have been chatting with also answers a web request, so you can put it inside a script, a spreadsheet or a page. A key identifies you; a request sends the text; a response comes back as data.

   The reason to try it once, even if you never build anything: it makes the chat version less mysterious. You see that the whole conversation is text in and text out, that your instructions are literally lines of a request, and that "the model" is one parameter among several.

   A first call looks like this:

   PythonCopy

   # The smallest version of the same loop, so you understand what you are buying:
   #
   #   1. plan      ask the model for the steps, as a list.
   #   2. act       run one step with a tool (search, fetch, compute).
   #   3. record    append the result, with the source, to a file.
   #   4. repeat    until the plan is finished or a step fails twice.
   #   5. deliver   write the artefact, and list what could not be found.
   #
   # Step 3 is the difference between this and a chat: every result is written
   # down with its source as it happens, so the output can be audited
   # afterwards. A loop without step 3 cannot be checked, and therefore
   # cannot be trusted with anything that matters.

   The mistake is giving an agent credentials, a live account or the ability to send things. Read-only access and a sandbox is the only sensible starting point.

   Example A script that searches, summarises and writes a CSV is the smallest version of what the product does — building it once is the best way to understand when the product is worth its credits.

   Practice Get a key, run one request that works, and change one word in it to see the answer change. That is the whole of the first afternoon.

4. Automate one boring task with Manus

   Automation is not about building a system. It is about doing one repetitive job the same way every time, in less time than last time, and being able to do it again next month.

   The lesson

   Pick the task by how often it happens, not by how impressive it would be. A weekly report you can half-generate beats a clever pipeline you build once and never open again.

   A recurring comparison or monitoring task: the same five-line brief run monthly, with the change list as the output.. Whatever you choose, write the steps back out in plain English afterwards — "Step 1, open the sheet, Step 2, paste the names —" because the written steps are what you follow when the tool changes next quarter.

   And keep a copy of the prompt next to the task. A prompt that lives only in your chat history is a prompt you will rewrite from scratch in March.

   Example A monthly price comparison of the same five tools, in the same table shape, so the diff between months is the useful part.

   Practice Name the task you repeat most often that involves typing, then write the prompt for it and run it three weeks in a row from the same saved place. Three runs is the point at which you know whether it is genuinely automated.

Week 4 — a finished portfolio project, the privacy rules, the limits, and the Manus certification paths.

1. Build the portfolio project: a research pack with every number sourced

   Delegate one real piece of project work — a comparison, a market note, a shortlist — and audit it properly: every number opened at its source, every gap marked. It is the thing you will talk about in the interview, so it has to be small enough to finish in a fortnight and concrete enough to show a person in one minute.

   The lesson

   Delegate one real piece of project work — a comparison, a market note, a shortlist — and audit it properly: every number opened at its source, every gap marked. Finish it before you start the next one. A half-built idea shows nothing; a small finished thing shows that you can finish.

   Use the tool as a collaborator, not an author: ask it for a plan, a critique and a checklist, and write the work yourself. In the interview the questions will be about the decisions — why this, why not that — and only the work you did yourself has answers.

   Write one paragraph beside the project: what problem it solves, what you used, and what you would do differently next time. That paragraph is the interview.

   Example Finished, it is a table, a short recommendation, and your own audit note of the two things the agent got wrong.

   Practice Present the finding in two minutes, including the audit. Saying "this figure came from here, and I could not verify this one" is the part that reads as professional.

2. Ethics, privacy and what never to paste

   These tools send what you type to somebody else's computer and keep it in a history. Never paste passwords, government ID numbers, bank or card details, medical records, or another person's private data — and never paste a company's confidential document.

   The lesson

   There is no version of this tool where your text stays on your laptop. Everything you type is sent to a server, kept in a history you can usually see, and may be reviewed or used to improve the product depending on the plan.

   Give it read-only access, never the ability to send messages or spend money, and never hand it credentials to an account that matters. Watch the step list for the first run of any new brief.

   The practical rule for a fresher: replace the real thing with a stand-in. "Client A", "my friend's phone number", "the amount in the offer letter". The tool rarely needs the real value to do the work, and the stand-in costs you nothing.

   And the professional rule: unattended access to an account that can send, buy or delete is not a time saver, it is a risk. If your employer has an approved plan or a policy, that policy is the answer, not your judgement about how sensitive a file really is.

   Example An agent with a browser will log into things if you let it, and a long unattended run can do a lot before you look at it

   Practice Go through your last five conversations and delete anything containing a real phone number, a client name, or a document you did not write. If you cannot find the delete button, that is the lesson.

3. Limits, hallucinations and how to check

   These tools predict plausible text. It cannot tell when it has gone wrong, and it will fill a gap rather than report it unless the brief tells it not to That is a mechanism, not a moral failing — and the habit it demands is the habit of asking "where did this come from?" out loud, every time, before you use an answer.

   The lesson

   A model does not look things up unless it has been given a way to look things up, and even then it can attach a real number to the wrong claim. It cannot tell when it has gone wrong, and it will fill a gap rather than report it unless the brief tells it not to

   So the rule is: numbers, dates, names, citations and legal or medical claims get checked in a primary source before they leave your hands. Everything else — drafts, structure, explanations, practice — is fair game.

   Three questions to ask before you trust an answer. Where did this come from? What would make it false? Who is the original source, and can I open it? If the third one has no answer, you have writing material, not facts.

   Open two sources at random and find one NOT FOUND. Those two actions catch most of what an autonomous run produces that is not true.

   Example Ask for a comparison without requiring sources and you will get a complete table with invented prices. The table will look finished, which is what makes it dangerous.

   Practice Ask for one statistic with its source, then open the source. Sometimes it exists. Sometimes the citation is invented, and the number is close enough to a real one to be dangerous. Either way you will remember the exercise.

4. Get certified: the official Manus paths

   A Way2Fresher certificate for this course is free and lives on this site. Beyond it, Manus publishes its own learning and certification material — and the rail on this course page links to it.

   The lesson

   There are two things called a certificate and they are not the same. The one this site issues records that you finished a structured course and built the project at the end of it — it is free, and it is yours to print. The ones Manus issues record that you passed their own material.

   Autonomous agent platforms do not issue credentials. Learn the pattern here and then take a recognised certificate in the area you applied it to — a cloud, analytics or project-management credential — because the domain is what an employer is hiring for.

   Get both, in that order. The project is what an interviewer asks about; the certificate is what gets past a filter that looks for keywords. The links to the official paths are in the rail beside this lesson, each labelled with who issues it.

   And put the work on the certificate, not the other way round: a certificate with no project behind it is a line on a resume, and it lasts exactly until the first technical question.

   Example A brief, an artefact and an audit note together show that you can manage delegated work. In an interview that is a more senior answer than a list of tools you have opened.

   Practice Finish every lesson here, take your Way2Fresher certificate, then open one official path and work through it with the project you have already built. Being certified in the tool you can already use is a small additional step.