The canvas is a plugin app
Infinite Canvas registers as an application plugin, owning canvas editing, workflow storage, import/export, and execution scheduling. It is not built into the framework — removing it never affects generation.
On an infinite canvas, connect image, video, speech, agent, and resource processing into one auto-executing production pipeline: drop nodes, wire ports, set parameters, run. The canvas itself is a plugin app, nodes are plugins too, and existing generation capabilities plug in directly — the plugin platform grows one layer further while the framework stays thin.
Neither canvas editing nor node business logic enters the framework. The framework only adds generic node discovery, node invocation, and safe asset import protocols.
Infinite Canvas registers as an application plugin, owning canvas editing, workflow storage, import/export, and execution scheduling. It is not built into the framework — removing it never affects generation.
A new canvas_node plugin type ships agent, resource, and control-logic nodes. Canvas nodes appear only in the canvas node panel — never in capability pickers, job toolbars, or the MCP tool list.
Registered image, video, and audio capabilities are wrapped automatically as generic generation nodes, running through the framework's schema validation, queues, and project archiving — no per-model node code.
Port types are stable and versioned (text, JSON, image, video, audio, job, and more); connections are type-checked, never silently converted.
Text, number, and boolean inputs; text templates, joins, and splits; JSON parsing and structure validation; conditional branches, merges, and parallel branches.
Browse and pick images, video, and audio from the project library; upload from your computer; import public external resources; write results back into the project library.
Structured script and copy writing, storyboard planning, prompt review, and constrained AI decisions. Outputs must pass JSON Schema validation, and callable capabilities are declared by allowlist.
Pick a capability_id, wire the prompt port and declared media inputs, set parameters and defaults — reusing existing plugins without copying any generation code.
The canonical carrier of a workflow is a JSON document: the canvas saves it as a project document and supports standalone import and export.
Workflow definitions and individual runs are stored separately — a run is a first-class, recoverable object.
The canvas ships with the next release. Build your capabilities as plugins now, and they become nodes the day it lands.
Download VideoFree → Plugin guide