> ## Documentation Index
> Fetch the complete documentation index at: https://extension.js.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Extension.js command guide

> Reference for every Extension.js CLI command including dev, build, start, preview, create, install, and uninstall with usage examples.

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

## Command chooser

| Goal                               | Command     | Example                                                         |
| ---------------------------------- | ----------- | --------------------------------------------------------------- |
| Scaffold a new project             | `create`    | `npx extension@latest create my-extension --template=new-react` |
| Develop with watch mode            | `dev`       | `extension dev --browser=firefox`                               |
| Build production artifacts         | `build`     | `extension build --browser=chrome,firefox --zip`                |
| Build and launch production output | `start`     | `extension start --browser=edge`                                |
| Launch existing build output only  | `preview`   | `extension preview --browser=chrome`                            |
| Install a managed browser runtime  | `install`   | `extension install chrome`                                      |
| Remove a managed browser runtime   | `uninstall` | `extension uninstall chrome`                                    |

## 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.

## Command references

* [create](/docs/commands/create)
* [dev](/docs/commands/dev)
* [build](/docs/commands/build)
* [start](/docs/commands/start)
* [preview](/docs/commands/preview)
* [install](/docs/commands/install)
* [uninstall](/docs/commands/uninstall)

The `telemetry` command (`enable` / `disable` / `status`) manages anonymous telemetry consent — see [Telemetry and privacy](/docs/features/telemetry-and-privacy).

## Next steps

* Apply cross-command controls in [Global flags](/docs/workflows/global-flags).
* Keep defaults centralized in [Extension configuration](/docs/features/extension-configuration).

## Video walkthrough