Repository navigation
feat: let the agent set a zoom's 3D camera - #1122
Conversation
addZoom, addZooms and setZoom take rotationPreset (left, right, orbit, or none for a flat screen), the editor's 3D camera control. It is stored as the zoom's rotationPreset, which getCurrentDocument already reported but no tool could set. Served to the in-app agent and to every MCP client alike.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to The zoom tools appear ready to merge after normal checks; no actionable issue was identified. Pre-merge checks |
|
What
The agent can now set a zoom's 3D camera, the editor's 3D camera control:
addZoom,addZoomsandsetZoomtakerotationPreset.left/right: the screen turned in 3D to that side.orbit: the camera moves around the screen while the zoom holds.none(default onaddZoom): a flat screen; onsetZoomit takes an existing camera off.It is stored as the zoom's
rotationPreset, whichgetCurrentDocumentalready reported but no tool could set. The tool descriptions tell the model it is a strong effect, for a reveal or a key moment rather than every zoom. The in-app agent and every MCP client (openscreen mcpincluded) get it through the same tool registry.Part of the agent-made demo work (#1119): a 30 s demo without voice needs the visual effects the editor has.
Verification
electron/ai-edition/agent-tools.test.ts: set onaddZoom, reported in the result, changed and removed bysetZoom, kept when another field changes, an unknown value refused, absent by default. Every document round-trips throughdocumentSchema.npx vitest --run electron/ai-edition electron/mcp(421 tests) and both typechecks green.🤖 Generated with Claude Code
Summary by CodeRabbit