Agents inherit the project
Agent Canvas and MCP clients work from the same production state the editor sees, so requests stay tied to real source media, scene IDs, selected takes, continuity anchors, and export readiness.
- Project context instead of standalone prompt history.
- Scene, reference, and provider metadata travel with each action.
- Review notes and export state remain part of the handoff.
Provider routing stays controlled
Video Loom keeps API keys server-side while agents route work through the configured provider stack, budget signals, readiness checks, and fallback rules already used by the web app.
- OAuth-protected MCP access.
- Per-scene provider and model context.
- Cost and readiness signals before expensive generation.
Finish inside the timeline
Agent-created plans still land in the same production path: generate takes, compare revisions, assemble clips, caption the cut, package review notes, and export a finished video.
- Generated work returns to the timeline.
- Continuity anchors stay attached across revisions.
- Final exports, captions, and review links stay connected.