ııı motion.mdVideo style specification
Cursor / V274

Cursor · Control a computer agent from your phone

Explain remote collaboration with phone and computer side by side: authorize first, synchronize context, then initiate the next task from the phone.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 38.80 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>You can now control agents on your computer from your phone.

Check in, reply, or start new tasks from the Cursor iOS ap · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f5f5f1}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 chatComputer agentAuthorization dialogPairing stateShared imageFollow-up questionKeyboard
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Pair first, then share content

Give phone and computer stable positions, with authorization on the computer or clearly designated recipient. Confirm the connection state before showing the same message and image on both sides.

Frame dark interfaces with purple surroundings and pale sans serif for important text. The narrower phone retains current context; the wider computer shows execution and results.

02

Express synchronization through matching content, not random movement

Express synchronization through matching content, not random movementRule example
0.00 / 7.00 seconds
14–21 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>You can now control agents on your computer from your phone.

Check in, reply, or start new tasks from the Cursor iOS ap · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#f5f5f1}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="14" data-end="21"><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>

Show the result image on the computer before the phone. Keep name, content, and task title consistent; scroll only to support current reading, without requiring both devices to move at the same speed.

03

Let the computer handle the phone's follow-up

Show the phone keyboard or input field, then put the computer into processing after sending. Update the result on both ends, closing with this clearly directed round trip.

For another scenario, use a design image, report, or code result while preserving authorization, shared context, and remote initiation.

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 6.00 seconds
6.00s
Composition reference at 14.00 seconds
14.00s
Composition reference at 21.00 seconds
21.00s
Composition reference at 28.00 seconds
28.00s
Composition reference at 36.00 seconds
36.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • For remote control, preserve authorization→shared context→remote initiation→feedback
  • Keep device roles and message identities consistent; branding may change

Production constraints

Phone chat / computer agent / authorization dialog / pairing state / shared image / follow-up / keyboard

  • Authorize pairing first, then show the same message and result at both ends
  • the computer begins executing after the phone sends input, and both update at the end with a clear direction
  • image appearance order conveys synchronization without requiring frame-by-frame synchronized scrolling