Common options
webstorio init
<directory>: webstorio.config.ts,
package.json, tsconfig.json, a pages/home.tsx, components/_header.tsx +
components/_footer.tsx, plus a README.md and .gitignore. The directory is
created if missing, and existing files are never overwritten.
The directory name seeds the default project name and subdomain.
webstorio update
package.json devDependencies, and install. Existing versions are
realigned to the compatible ones, and imports outside the Webstorio allowlist are
reported and skipped.
The package manager is detected from
packageManager in package.json or a
lockfile (pnpm-lock.yaml, yarn.lock, bun.lockb, package-lock.json),
defaulting to npm.
webstorio dev
Start the local preview server with file watching and live reload. Fully offline
in empty/dummy modes.
See Local development for details on data modes.
webstorio schema
schemasDir (requires schemasDir in config).
Enable the matching website features (
content, form_and_survey, app_data)
before syncing definitions for that kind.
How-to: Feature schemas.
webstorio generate
.tsx modules under pages/, enables the
matching feature flag, and registers routes in webstorio.config.ts. This does
not call remote create-page APIs — preview with webstorio dev and sync with
webstorio push.
Existing slugs / files are skipped. Define matching schemas under
schemas/ (or
the dashboard) for CMS and forms before or after generating pages.
webstorio login
Authenticate the CLI through your browser. The CLI opens a Webstorio URL, you
approve, and a token is stored securely (OS keychain when available, otherwise a
0600 file under ~/.webstorio/).
webstorio logout
Revoke the current CLI token on the server and remove the stored token from
this machine.
webstorio status
webstorio push
Compose every page and component and sync them to your Webstorio project. The
project is resolved by the subdomain in your config and created automatically
if it doesn’t exist yet.
Output reports each page as
created, updated, or error (with the reason).
