The current CLI delegates local state, editing, and exports to the installed bridge. Start with Agent plugins for the available packages and setup instructions.
Previous commands
These command names now return CLI_MIGRATION_REQUIRED; their old flags and behavior are no longer supported.
| Previous workflow | Current path |
|---|---|
preview, dev, dev-server | Use start and open, or the Vite and Next.js adapters. |
render | Use export with an explicit revision and a connected browser renderer. |
auth, cloud-render, sync, webhook | Use @editframe/api for existing cloud API integrations. See renders, files, and webhooks. |
check, process, process-file, transcribe | These utility commands have no direct thin-CLI replacement. Use the browser editor's available workflows; application build integrations use @editframe/build-adapter. |
Connection changes
Local commands require an explicit project directory and an installed bridge executable or verified component directory. Installing the npm package alone does not install a runtime.
Hosted runtime commands use --endpoint, --project-id, and EDITFRAME_TOKEN. Existing @editframe/api cloud integrations use their own API client credentials; the old CLI's EF_TOKEN option is not a runtime login mechanism.
Framework adapters
The default Vite and Next.js plugins connect your application to the installed runtime. They no longer embed the legacy asset server. Update to the current projectRoot and bridge selection options shown in their reference pages.