What Manus Is and What It Can Reach

Most AI tools you've tried answer one question and stop. Manus calls itself an autonomous general AI agent: you give it a job, and it plans the steps, carries them out and hands back finished work. An agent here means software that works toward a goal over many steps, not just one reply.

Here's an example from a product job. A client wants a studio shot of an olive-oil bottle placed on a stone table outdoors and delivered in nine sizes. Paste that brief into a chat tool and you get advice on how to write a shot list. Hand it to Manus and it reads the brief, drafts the shot list as a spreadsheet, looks up sunset time for the location from a source it cites, and gives you the files.

That changes how you work with it. You aren't asking a question. You're delegating: handing a task to someone else to carry out. So you brief Manus the way you'd brief a studio assistant, and you check what comes back the same way before your name goes on it.

Each Manus task runs in its own sandbox. That's a cloud virtual machine: a computer in a data centre, not your own machine. It has networking, a file system, a web browser and software tools. Inside it, Manus can browse websites, install software, run code and write files.

Say you ask for a reference study of five studios' recent product campaigns. Manus opens its browser, visits each site and writes notes to a file. It might run a short script to build a comparison table, then save a report. You can watch or replay all of this later.

Three things follow from this:

• It can't see your computer unless you give it a folder through the desktop app. A later lesson sets that up safely.
• Anything you upload goes to that cloud computer. That's why confidential client files need care.
• The sandbox doesn't last forever. An idle one is recycled after 7 days on Free or 21 days on Pro. Final outputs are restored but intermediate files are not, so keep your own copies of what matters.

For the work around your craft, these Manus outputs matter most:

• Research reports, with links to the sources they used.
• Documents and spreadsheets, such as a shot list, production plan or change log.
• CSV files: plain tables any spreadsheet opens. Examples are a shoot catalogue or a metadata sheet keyed by filename.
• Slide decks as editable .pptx or PDF. Manus can also make web slides and a speaker-notes file, and you can apply your own .pptx template.
• Websites, such as a case-study page or a portfolio. You preview it, and only you decide whether it gets published.

On the olive-oil job, that could mean a shot list spreadsheet, a reference memo, a CSV of the shoot's filenames and capture times, and later a case-study deck built on your studio template.

Plan note: slides, website deployment and Wide Research (Manus running many research items in parallel) need a paid Pro plan as of October 28, 2026. The Free plan can still produce reports, documents and spreadsheets. Plans are covered later in this module.

Manus connects to other apps through connectors: links you approve so it can read from or act in a service such as Google Drive or Gmail. The catalogue lists more than 75 apps. As of October 28, 2026, there is no Adobe connector in that catalogue or in Manus's API connector list. No documented feature opens PSD, AI, PRPROJ or Lightroom catalogue files.

That matters because those files hold the work itself: layers, masks, linked smart objects, sequences and edit history. Manus can't open your bottle composite, check whether the reflection still shows the old label, or move a marker on your timeline.

What it can work with are things you export: flattened JPEGs or low-resolution proxies (small stand-in copies of an image), PDFs, text notes and CSVs. It can also use a folder of copied image files on your machine that you grant through the desktop app.

You may see claims online that it can sometimes get further by running code. Don't build a client job on undocumented behaviour. Check the connector catalogue again before relying on this, because it changes.

So the split is clear. Manus does the coordination work around the craft. That means turning a brief into a shot list, researching references, preparing and cataloguing a shoot, writing metadata and captions, merging feedback into a change log, and presenting finished work. You finish the craft in Adobe: the selection, the shadow, the label at 100 percent, the export.

Manus 2.0 also has built-in image and video models. You might be tempted to let them make the stone table or the summer light. This course does not use them for final production imagery. Their output wouldn't come from your accepted source, and it couldn't go through your layered, checked workflow. If a client asks whether anything was generated, you need to be able to answer.

On the olive-oil job, the work alternates between you and Manus. Put the stages in the order they would actually happen.

Ely Greenfield is chief technology officer for Adobe's creative business, including the Firefly models. In an October 2025 interview with The Neuron, he described two kinds of people using media agents. Some have no production skills and let the agent work everything out. Professionals accept the help but take back the reins when the agent falls short. Adobe's professional customers, he said, want repetitive production work automated without losing control. He speaks for a vendor that sells these tools, so take this as his perspective, not as proof.

This course takes that stance. Hand Manus the logging, sorting, researching, chasing and drafting. Keep the image decisions, the permission questions and the final release.

In practice, that means three habits you'll build in later lessons:

• Every brief says what Manus must not do, such as send, publish or rename without asking.
• Every result gets checked before anyone relies on it.
• A named person signs off what leaves the studio.