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

# Get started with the Extension.dev platform

> Take an extension from a workspace to the browser stores with the Extension.dev platform: create a workspace, import or AI-generate a project, preview it, then build and submit to Chrome, Firefox, and Edge.

The open-source `extension` CLI runs and builds extensions on your machine. The
**Extension.dev platform** is the hosted track on top of it: it takes a project
from a workspace all the way to a store submission, with a managed GitHub mirror,
CI builds, and one-command publishing.

If you are looking for the local command-line workflow instead, start with
[Create your first extension](/docs/getting-started/create-your-first-extension).

## CLI track vs platform track

|               | CLI track                     | Platform track                                            |
| ------------- | ----------------------------- | --------------------------------------------------------- |
| Where it runs | Your machine                  | Hosted on extension.dev                                   |
| Entry point   | `npx extension@latest create` | A workspace at [extension.dev](https://extension.dev)     |
| Best for      | Local development and builds  | Importing, previewing, building, and submitting to stores |
| Output        | Local unpacked build / zip    | Managed mirror repo, CI artifacts, store submissions      |

The two tracks are designed to meet: you can develop locally with the CLI and then
bring the project into the platform at `/import`.

## The primary platform journey

<Steps>
  <Step title="Create a workspace">
    Sign in at [extension.dev](https://extension.dev) and create a workspace. A
    workspace is the home for your projects, builds, and store credentials.
  </Step>

  <Step title="Bring in a project">
    Start a project two ways:

    * **AI generate:** describe what you want at
      [intelligence.extension.dev](https://intelligence.extension.dev) and preview
      the generated extension in the browser.
    * **Import:** go to [extension.dev/import](https://extension.dev/import) and
      import an existing extension. The platform creates a managed GitHub mirror
      for the project so builds are reproducible.
  </Step>

  <Step title="Preview the extension">
    Preview any build in the browser before you ship it. Each build is addressable
    per project, commit, and browser target, so you can confirm behavior on
    Chrome, Firefox, and Edge.
  </Step>

  <Step title="Build in CI">
    The managed mirror builds per-browser artifacts in CI and publishes them to the
    registry with integrity attestations. You do not maintain the build pipeline
    yourself.
  </Step>

  <Step title="Submit to the stores">
    Submit the build to the Chrome Web Store, Firefox Add-ons, and Edge Add-ons.
    Submission is driven from CI (and from AI agents via the
    [MCP server](/docs/ai-access)) using a single deploy step.
  </Step>
</Steps>

## What "publish" guarantees

The platform guarantees that a store **submission** succeeds and is reported
honestly: the upload is accepted, validation passes, and the submission is queued
for review. It does **not** guarantee that the listing goes live. Store-reviewer
acceptance is a third-party decision outside the platform's control. Submission
status is always reported truthfully, and a listing is never claimed to be live
before the store confirms it.

## How this relates to the CLI

You can move between tracks at any time:

* Develop locally with [`extension dev`](/docs/commands/dev) and
  [`extension build`](/docs/commands/build), then import the project into a
  workspace to get CI builds and store submission.
* Start a [template](/docs/getting-started/templates) on the CLI, push it to
  GitHub, then enter the platform at `/import`.

## Next steps

* New to extensions entirely? Begin with the
  [CLI getting-started path](/docs/getting-started).
* Want AI agents to drive builds and submissions? See
  [Connect AI to docs and tools](/docs/ai-access).
* Choosing a starting stack for the local track?
  [Browse templates](/docs/getting-started/templates).