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.
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>Motion and composition
Local motion · Composition rules
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.
From code view to document request
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.
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.
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.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
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.