Skip to main content
The wizard handles sign-in, install, a sample run, and editor setup. The manual steps below cover the same setup if you’d rather do it yourself.

​
Prerequisites

The wizard and manual setup both require:
  • Node.js 22.12.0+ or 24.0.0+
  • A package.json in your project (run npm init -y if you don’t have one)
  • A Momentic account; sign up to generate an API key
Run the onboarding wizard in your terminal. It signs you in through the browser, installs Momentic, runs a sample test, and sets up the editor MCP server.

​
Setup with coding agent

A coding agent can’t complete the browser sign-in, so the agent path uses an API key and runs the wizard non-interactively. Copy the prompt below into Cursor, Claude, or another agent:

Set up Momentic for a web project end to end via the onboarding wizard, non-interactively.

Open in Cursor

​
Manual setup

Option A: sign in with your browser (recommended):
This opens a browser-based login flow and saves credentials to ~/.momentic/auth.json. The CLI automatically uses this file when MOMENTIC_API_KEY is not set. Option B: use an API key: Create an API key in the dashboard, then export it:
Persist the key by appending the export line to ~/.zshrc (macOS) or ~/.bashrc (Linux). In CI, set MOMENTIC_API_KEY as a secret environment variable.
This writes momentic.config.yaml to your project root. init does not scaffold any tests; author your first one in the editor below. (For pre-scaffolded sample tests, use the onboarding wizard instead.) The wizard configures Momentic’s MCP server and installs agent skills for you. For manual setup, follow the MCP setup guide to connect your editor and install the skills your coding agent needs. Momentic runs your tests against a headless browser. Install Chromium:
Open the local editor:
Create a test with base URL https://practicetestautomation.com/practice-test-login/ and author a single natural-language step (for example, Log in with username "student" and password "Password123", then confirm the success page loads.). Save it (the editor writes the .test.yaml to your project), run it from the editor to verify, then run it from the CLI by name:
  • Check the .test.yaml you just authored exists in your project root
  • Open the dashboard and check Runs for the result

​
Next steps

Core concepts

Finding elements, writing assertions, modules, variables

CI/CD

Run Momentic on every pull request

Best practices

Write tests that hold up over time
Need a full working example? Clone momentic-ai/examples.