VideoFree Studio VideoFree Studio 2.0.1 released
This release focuses on standardizing the plugin and system-extension protocols, making platform capabilities more regular and laying the groundwork for future extension and maintenance.
Plugin manifest standardization
A formal JSON Schema for the plugin manifest now constrains identity, capabilities, actions, UI, settings and localization declarations. Manifests are validated with the same rules during the startup scan, reducing load failures caused by field typos or incomplete declarations. Structural validation belongs to the schema; semantic checks such as paths and cross-field rules stay in the framework.
Generic extensions for system services
A generic system-service Provider registration and invocation protocol is added. LLM providers already run on the unified registry, declaring actions, input/output shapes and config fields in their manifests; the framework handles provider discovery, config reading, schema validation and error handling. Adding a provider for an existing service type no longer requires modifying framework routes.
Stable plugin runtime interface
PluginRuntime gains a stable API version tag and a generic system-service call entry. Plugins can call registered services through the framework runtime instead of binding to provider implementations or reading system-service configuration directly.
Security & diagnostics
Manifest errors for plugins and system services now surface at startup or release checks. System-service configuration uses a field allowlist with secrets treated as sensitive fields; errors for invalid input never echo the input value. Providers with inconsistent contracts are refused at load, preventing unpredictable behavior differences across the same service.
Developer & release docs updated
The plugin protocol, system-service protocol, development guide and release checklist are updated accordingly, providing machine-checkable specifications and contract tests for future plugin development.
Scope notes
Plugins and providers remain locally trusted code, not a sandbox; the generic system-service protocol covers JSON request/response operations. File streams, ComfyUI operations and lifecycle-managed scheduling continue to be handled by their corresponding typed framework interfaces. This release does not include multi-tenancy, multiple ComfyUI nodes, or remote storage.