ııı motion.mdVideo style specification
Cursor / V074

Cursor SDK — We’re introducing the Cursor SDK so you…

Write a minimal SDK example, run it alongside, then switch execution environments by changing only configuration. Connect code and terminal to demonstrate interface consistency.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 35.03 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>Cursor SDK — We’re introducing the Cursor SDK so you… · 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 elementsCode lineLine numberSyntax colorActive lineTerminalOutput logCompletion mark
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Reveal code in dependency order

Write imports, agent creation, task submission, and event handling in sections. Center attention on the active block, keeping line numbers stable and adding lines downward; do not shrink the whole page into tiny text immediately.

Separate cream code and black terminal areas clearly. Use monospaced code with limited syntax colors, a pale background or accent on active configuration lines, and simple sans serif headings.

02

Let the terminal show progress during execution

Let the terminal show progress during 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>Cursor SDK — We’re introducing the Cursor SDK so you… · 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="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>

Once code is complete, shrink it left and reveal the terminal right. Enter the execution command before logs of reading, modification, checks, and completion. Logs may accelerate, but pause on key completion lines.

03

Highlight only changed lines when switching environments

When replacing a local path with a cloud repository or related configuration, keep most code unchanged. Briefly highlight active lines, then rerun and show the second result.

Keep the same goal in both runs, concentrating differences on execution location; do not replace code, task, and output together merely to indicate cloud use.

04

Prepare readable minimal code before changing examples

Choose a short task whose configuration and output fit readably on screen. Replace code, terminal command, and logs together, preserving minimal configuration, one run, a small change, and another run.

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 4.00 seconds
4.00s
Composition reference at 9.00 seconds
9.00s
Composition reference at 18.00 seconds
18.00s
Composition reference at 22.00 seconds
22.00s
Composition reference at 31.00 seconds
31.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to SDK instruction, preserving minimal example→execution→configuration-only change→execution again
  • Validate code independently; source text is not a promise of runnable code

Production constraints

Code line / line number / syntax color / active line / terminal / output log / completion mark

  • Write code progressively, then shrink it into the left column while the terminal on the right executes the same configuration
  • when switching from local to cloud, highlight only relevant configuration lines and reuse other code to show interface consistency
  • logs follow invocation, changes, validation and completion