Repository navigation
MCP stopRecording promises a zoom on each recorded click #1141
Description
Found during the v2.1.0 release-candidate QA (Windows 11, CI build of release/v2.1.0 @ 9c55596).
What happens
The MCP stopRecording description promises "one clip, plus a zoom on each recorded click". A take with two clicks 4.2 s apart came back with autoZooms: 1: the first click, at 1.9 s, got no zoom.
Why this is the wording, not the planner
The auto-zoom planner (src/lib/ai-edition/timeline/zoom-suggestions.ts) does this on purpose:
- the video opens on the whole screen: no zoom moves in during the first 2.5 s, so a click that early gets none;
- it ends on it, and the click in the last second (the Stop click) is ignored;
- clicks less than 3 s apart that fit in one frame share one zoom;
- two zooms with too short a wide shot between them merge, or the one with fewer clicks goes.
The same promise is repeated in the MCP server preamble ("zooms on each click"), startRecording, setPointerTrack ("adds a zoom on each new click"), the openscreen-demo skill, the docs page website/docs/ai-editing.md, and the manual e2e checklist ("MCP server — post-2.0.0": "one clip and a zoom per click").
Fix
Describe what the planner does, and point to autoZooms / autoZoomsAdded for the count.
Activity
EtienneLescot commentedon Oct 12, 2026
The macOS pass on the same candidate (build run 38252812147, macOS 26.5 arm64, PR #1131) hit the merge rule rather than the opening: pass 1 got
autoZooms: 1for 3 clicks about 1.7 s apart, pass 2 got 1 for 2 clicks. Both are theSHOT_MERGE_GAP_MS(3 s) grouping, as intended. Worth deriving the number in the tool text fromSHOT_MERGE_GAP_MS/OPENING_WIDE_MSso the description cannot drift from the planner.docs(mcp): stop promising a zoom on each recorded click
github-actions commentedon Oct 13, 2026
Fixed by #1153 and merged into
main.This change is assigned to the
Next Releaserelease milestone and is not necessarily available in the latest downloadable desktop release yet. It is currently marked asstatus: pending releaseuntil a packaged release containing it is published.EtienneLescot commentedon Oct 15, 2026
Moved into
v2.1.0as part of the pre-release cut.