ııı motion.mdVideo style specification
Anthropic / V238

Claude — computer use in Cowork and Claude Code

The phone requests, the desktop executes, and the result returns to the phone. Preserve the same direction in every cycle so different tasks share one visual language.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 73.33 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>Claude — computer use in Cowork and Claude Code · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#e1d9ca}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 elementsPhone request endpointDesktop execution endpointConnection lineRequest bubbleOperation windowReturned result card
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Fix the two endpoint roles

34.00s · Composition reference

Sand background, white phone and desktop devices, brick-red request bubbles, and fine connections.

Complete each task through phone request → desktop execution → phone confirmation, repeating this structure three times with progressively developing content.

02

Focus on the request before revealing execution

Focus on the request before revealing executionRule example
0.00 / 10.00 seconds
6–16 seconds · Motion 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>Claude — computer use in Cowork and Claude Code · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#e1d9ca}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="6" data-end="16"><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>

Place the phone on the left and execution environment on the right; thin connections express causality, not decorative trajectories.

Focus on input first, pull back to show both endpoints, then move closer to the returned result.

03

Repeat the cycle, change the task

Each round starts on the phone, moves to computer execution, and returns to the phone for results. Replace content across three tasks while keeping direction and device positions fixed.

04

Replace the cross-device tasks

For creative tools, show remote request→desktop generation→phone review, keeping endpoint roles consistent.

Task count may vary, but each needs a cause, process, and result; do not merely swap static device images.

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 12.00 seconds
12.00s
Composition reference at 25.00 seconds
25.00s
Composition reference at 34.00 seconds
34.00s
Composition reference at 53.00 seconds
53.00s
Composition reference at 70.00 seconds
70.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • For creative tools, show remote request→desktop generation→phone review, keeping endpoint roles consistent.
  • Task count may vary, but each needs a cause, process, and result; do not merely swap static device images.

Production constraints

Phone request endpoint / Desktop execution endpoint / Connection line / Request bubble / Operation window / Returned result card

  • Complete each task through phone request → desktop execution → phone confirmation, repeating this structure three times with progressively developing content.
  • Place the phone on the left and execution environment on the right; thin connections express causality, not decorative trajectories.
  • Focus on input first, pull back to show both endpoints, then move closer to the returned result.