Skip to main content

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.

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 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: 
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 for flags (pass a test path to import a single test plus the modules it uses). 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: 
npx @momentic/wizard@latest
After that, run npx momentic import from the project root.

​
What is deprecated

These surfaces are no longer supported. They may still respond for backwards compatibility but will be removed in a future release.
  • 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.
  • Cloud-hosted test runs (momentic queue tests and queue suites). Run with momentic run locally or in CI instead.
  • Momentic Copilot (the cloud-based AI authoring assistant). Use your coding agent with the MCP server for natural-language test authoring.

​
What is not deprecated

The dashboard at app.momentic.ai is still the home for everything that isn’t authoring or execution: 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:
1

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 and describe the behavior in natural language. Tests are YAML files in your repo.
2

Run locally and in CI

Replace momentic queue tests and momentic queue suites with momentic run. For CI, drop in one of the ready-made templates.
3

Triage in the dashboard

Pass --upload-results to surface runs in the dashboard. Nothing changes about how you view, share, or quarantine runs.

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