Cursor can control a computer
Use a shared frame to clarify who controls and who responds. The agent on the left receives the task; the phone simulator on the right performs traceable actions.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Cursor can control computers · 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>Motion and composition
Local motion · Composition rules
Enter one specific goal first
After the feature statement, enter a computer-control request, start the agent, then introduce the phone simulator. Choose a task completable within the clip, such as viewing and saving an item.
Use a dark agent column and pale simulator content, connected by a warm background. Keep task text in clear sans serif and retain the app's own internal heading hierarchy.
Connect actions into one path
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Cursor can control computers · 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="9" data-end="18"><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>Scroll the list, open details, return, favorite, and enter favorites in sequence. Retain the same item's name or image on each new page so viewers recognize it.
Move the pointer or touch indicator to its target before changing the interface. Highlight only the current agent-log action, avoiding long text scrolling simultaneously with the phone.
Close on the result state
Finally push into the saved favorite or completion state, letting the agent panel recede into the background.
For another app, replace the task, list, details, and final result. Keep controller and controlled roles unchanged; do not make the two sides unrelated animations.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- When changing apps, retain the agent side and controlled side as distinct roles
- List content may change, but preserve causality between user actions and the final result
Production constraints
Instruction box / agent log / phone simulator / route list / detail page / favorite state / pointer
- Keep the agent on the left and simulator on the right in the same view, with results occurring inside the controlled app
- scrolling → details → back → favorites filter forms a coherent interaction rather than unrelated images
- push in on favorites at the end, matching feedback to the earlier favorite actions