Skip to main content
Choose the right command for the current phase of extension development, from first scaffold to production validation.

Command chooser

Running a bare extension with no command prints the full help and exits with code 0.

Typical developer flow

  1. create to scaffold.
  2. dev for iterative coding and reload cycles.
  3. build for production artifacts.
  4. preview or start for production-like validation.
  5. install or uninstall when you need to manage Extension.js browser runtimes explicitly.
  6. logs, inspect, eval, storage, reload, and open to observe and drive the running session.
  7. doctor when a dev session or an automation verb talking to it stops responding.
  8. capabilities first, when a script or agent drives the CLI instead of a human.

Command references

The telemetry command (enable / disable / status) manages anonymous telemetry consent. See Telemetry and privacy.

Next steps

Video walkthrough