ııı motion.mdVideo style specification
Kimi / V246

Kimi Web Bridge - Kimi's browser extension.

Show browser actions and agent feedback side by side, keeping input, execution, and results aligned throughout.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 63.33 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>Kimi Web Bridge - Kimi's browser extension. · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#62a4d5}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 elementsBrowserTerminalCommandWebpage highlightTableSurvey formValidation report
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Fix both views to reduce searching for positions

Use a dark-to-light blue gradient outside, with a wider browser on the left and continuous terminal on the right. Use sans serif on pages and monospace in the terminal; let chapter headings briefly fill the frame only between tasks.

02

Move from search results to a spreadsheet

Move from search results to a spreadsheetRule example
0.00 / 24.00 seconds
6–30 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>Kimi Web Bridge - Kimi's browser extension. · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#62a4d5}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="6" data-end="30"><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>

Enter the command in the terminal first, then open multiple source pages. Highlight key content locally; once collection finishes, switch to a spreadsheet whose entries correspond to those sources.

03

Show form-building through growing fields

Start the second task with a short request, then add the title, questions, and options to the page in sequence. Show current status in the terminal and new content in the browser, keeping the same task name on both sides.

04

Show the completed website and browse it

45.00s · Composition reference

After entering the target, browse the page before showing the generated version. Scroll through major sections at the end while the terminal summarizes corresponding results, making the outcome clear.

05

Give all three tasks a beginning and an ending

Separate retrieval, form, and website examples with short chapter phrases. Show each request before its actions and output, completing one example before starting the next.

06

Replace tools and sites

Change the browser assistant, target sites, and tasks. Maintain distinct roles for both views and vary result types by task; avoid ending every example with scrolling commands.

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 13.00 seconds
13.00s
Composition reference at 23.00 seconds
23.00s
Composition reference at 40.00 seconds
40.00s
Composition reference at 45.00 seconds
45.00s
Composition reference at 58.00 seconds
58.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Suitable for browser automation demonstrations; replace task sites and results while preserving cause and effect across both views.
  • The example does not prove real online execution or recreation accuracy.

Production constraints

Browser / terminal / command / webpage highlight / spreadsheet / survey form / validation report

  • Place browser actions and terminal feedback side by side to show the correspondence between the agent's plan and page results.
  • Give each of the three tasks input, execution, and results, with chapter headings briefly interrupting the screen recording.
  • The final report must correspond to webpage checks, not merely scrolling commands.