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

# Cloud deprecation

> Authoring and running tests in the Momentic cloud is deprecated. Run `npx momentic import` to pull your tests into your repo and own them with the CLI.

Momentic is **CLI-first**. Tests live in your repo as YAML, are authored and
edited with the CLI (and your coding agent through MCP), and run locally or in
CI. The web app at [app.momentic.ai](https://app.momentic.ai) is the dashboard
for triage, settings, and integrations.

## Move your tests with `momentic import`

The whole migration is one command. From the root of the repo you want your
tests to live in, run:

```bash theme={null}
npx momentic import
```

This pulls every test, module, and environment from the cloud down into your
repo as YAML. Commit the generated files alongside your application code and you
are done with the cloud editor. See
[`momentic import`](/cli-reference/momentic/commands/import) for flags. You can
also pass test paths to import individual tests or folder paths (e.g.
`auth/onboarding`) to import an entire cloud folder; the folder hierarchy is
recreated on disk so your local layout mirrors the dashboard.

If you do not have the CLI set up yet, the onboarding wizard installs it, logs
you in, and scaffolds a project in one step:

```bash theme={null}
npx @momentic/wizard@latest
```

After that, run `npx momentic import` from the project root.

## What is deprecated

<Warning>
  These surfaces are no longer supported. They may still respond for backwards
  compatibility but will be removed in a future release.
</Warning>

* **Authoring tests in the cloud editor.** Create and edit tests with the CLI
  (and the local editor it ships with) or your coding agent via the
  [MCP server](/integrations/mcp-server).
* **Cloud-hosted test runs**
  ([`momentic queue tests`](/cli-reference/momentic/commands/queue) and
  `queue suites`). Run with
  [`momentic run`](/cli-reference/momentic/commands/run) locally or in
  [CI](/running-tests/ci/github-actions) instead.
* **Momentic Copilot** (the cloud-based AI authoring assistant). Use your coding
  agent with the [MCP server](/integrations/mcp-server) for natural-language
  test authoring.

## What is **not** deprecated

The dashboard at [app.momentic.ai](https://app.momentic.ai) is still the home
for everything that isn't authoring or execution:

* [Results and the Run Viewer](/running-tests/results): videos, traces,
  auto-heal history, step output
* [API keys, team, and SSO](/account/api-keys-and-team)
* [Security and audit](/account/security)
* [Quarantine](/reliability/quarantine) and quarantine rules
* [Results classification](/reliability/failure-analysis) and recovery history
* AI settings and model version pinning
* Integrations: [Slack](/integrations/slack), [GitHub](/integrations/github),
  [GitLab](/integrations/gitlab)
* Usage and billing

Every CI template and quickstart in these docs still points at the dashboard for
these. Nothing about that is changing.

## After importing

Once your tests are in the repo:

<Steps>
  <Step title="Author with the CLI or MCP">
    Edit imported tests (or write new ones) in the local editor that ships with
    the CLI, or hand your coding agent the [MCP
    server](/integrations/mcp-server) and describe the behavior in natural
    language. Tests are YAML files in your repo.
  </Step>

  <Step title="Run locally and in CI">
    Replace `momentic queue tests` and `momentic queue suites` with [`momentic
            run`](/cli-reference/momentic/commands/run). For CI, drop in one of the
    [ready-made templates](/running-tests/ci/github-actions).
  </Step>

  <Step title="Triage in the dashboard">
    Pass `--upload-results` to surface runs in [the
    dashboard](https://app.momentic.ai). Nothing changes about how you view,
    share, or quarantine runs.
  </Step>
</Steps>

## Why

CLI-first means tests are versioned with your application code, run the same way
on a laptop and in CI, and integrate naturally with coding agents through MCP.
The dashboard's job is triage and configuration, not authoring or execution.

## Related

* [`momentic import`](/cli-reference/momentic/commands/import)
* [`momentic run`](/cli-reference/momentic/commands/run)
* [`momentic queue`](/cli-reference/momentic/commands/queue) (deprecated)
* [How Momentic works](/get-started/how-momentic-works)
* Quickstart: [Web](/quickstart/web), [iOS](/quickstart/ios),
  [Android](/quickstart/android)
* [MCP server](/integrations/mcp-server)