Type after a plugin chip, click send, and hard-cut into the agent's working log
Study the source, inspect the editable build, then adapt the treatment to your own content.
What the source does
A centred heading asks what to build; below it a white composer holds a blue plugin chip and a request typing on with a caret (f0–42). The pointer drifts to the black send circle and clicks at ~f62; the button flashes. At ~f68 the frame hard-cuts to the workspace: the prompt (chip plus text) sits as a grey pill at upper right, a right-hand environment column lists context, and under a 'Working' label a paragraph streams in, ending with a faint 'Thinking' status.
Composer type-on behind an inline chip, a click on send, then a hard cut that re-homes the prompt as a message pill while the agent's log streams in.
Phase notes
- Frame 0 — Typing after the chip, caret visible
- Frame 42 — Prompt complete
- Frame 62 — Send clicked
- Frame 68 — Hard cut to workspace with prompt pill
- Frame 72 — Working paragraph streams
- Frame 91 — Thinking status holds
Use this example
- Watch the source and draft at normal speed. Compare the order of actions, the held states, and the transition into the result.
- Download the project and read its README before changing inputs. The package includes its implementation and declared dependencies.
- Replace the sample content through the package's documented input or content builder. Keep source footage in the research comparison.
- Render your adaptation and inspect text fit, framing, intermediate states, and entry and exit frames.
The source and remake are different assets. The original code-based illustration remains editable; source footage is a research reference. Read the retained findings below before using the choreography.
Recorded limits
- Visual fidelity is an authored draft judgement from sampled source frames; no independent blind review or native Resolve execution.
- Both variants rerendered after correcting unrevealed whitespace and the caret’s active line.