ııı motion.mdVideo style specification
OpenAI / V304

ChatGPT Desktop — now in preview on Linux

Take one coding task, organize it into a shareable document, and open it in the editor used for everyday work.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 45.25 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>ChatGPT Desktop — now in preview on Linux · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fbfbfb}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 elementsConversation sidebarInputCode diffReplyDocument linkDocument window
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Keep the task's name and materials

Fix the conversation sidebar on a white workspace, use monospace for code, and highlight only the current action in blue-violet. Code filenames, document title, and body all concern the same task.

02

From code view to document request

From code view to document requestRule example
0.00 / 22.00 seconds
6–28 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>ChatGPT Desktop — now in preview on Linux · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fbfbfb}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="6" data-end="28"><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>

Wait for the code result to settle before requesting a document. Open the new document beside it so viewers can see the relationship between source and output.

03

Finish in the destination editor

Keep the editor toolbar visible after opening the document, showing title, code snippets, and explanatory text. The endpoint is an output that remains editable.

04

Adapt to another knowledge output

Use research, meeting notes, or design documentation instead. Preserve correspondence among source, organization request, and target file; for longer documents, show a representative opening and one key section.

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 3.00 seconds
3.00s
Composition reference at 6.01 seconds
6.01s
Composition reference at 22.02 seconds
22.02s
Composition reference at 28.03 seconds
28.03s
Composition reference at 40.04 seconds
40.04s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to design→documentation, preserving the step of opening and checking the generated file.
  • Content may change, but source materials and delivered files must correspond.

Production constraints

Conversation sidebar / Input / Code diff / Reply / Document link / Document window

  • Show the coding task first, then request that the code be organized into a document; open the result to verify cross-application delivery.
  • The camera switches among conversation, code, and document areas while preserving the same task context.