ııı motion.mdVideo style specification
Manus / V048

Cloud Computer: Deploying and using a cloud computer

Organize the demonstration around one persistent cloud computer: establish the environment, inspect resources, then deploy and run services.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 47.97 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Manus — general AI agent that bridges minds and… · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f7f8f6}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsCloud containerInput fieldResource panelTask processDeployment result
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Give the computer a clear state first

The entry page establishes a functional cloud environment before the resource panel appears. Arrange CPU, memory, files, and connections in orderly values and charts; keep system name and running state visible.

Use primarily light workspaces, with blue for current controls and charts. Slightly heavier headings and layered resource values and units provide hierarchy; do not exaggerate every reading with bouncing motion.

02

Follow the resource panel with real work

Choose a concrete task such as deploying a bot, collecting data, or building a data service. Proceed through request, execution feedback, and opening the output, making the service page the result of the cloud computer's work.

03

Vary the services, keep the working environment stable

Reuse the same application frame or entry position between examples, changing only tasks and outputs. Move closer to key settings, then return to the full window; avoid repeated large zooms that lose orientation.

04

Adapt to another cloud workspace

Preserve environment, resources, tasks, and online results. When changing deployment targets, supply matching inputs, execution states, and result pages rather than retaining irrelevant resource text.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 10.01 seconds
10.01s
Composition reference at 20.01 seconds
20.01s
Composition reference at 27.02 seconds
27.02s
Composition reference at 36.03 seconds
36.03s
Composition reference at 45.03 seconds
45.03s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Preserve environment→task→persistent result when adapting
  • Change service names and outputs while preserving distinct output forms for different tasks

Production constraints

Cloud container / Input field / Resource panel / Task process / Deployment result

  • Explain the persistent execution environment first, then prove it through three examples: bots, scraping and deployment
  • move each example from a request to execution evidence, then an accessible result
  • tool icons surround the scene before gathering as input resources