# Momentic V2 format reference Use this reference when the high-level Momentic skill does not cover the YAML shape you need. The JSON schemas are for editor validation and autocomplete; this file is the compact authoring reference for coding agents. ## Compatibility | Feature | Minimum version | | -------------------- | ------------------------------------------- | | Web while loops | `momentic@3.8.0` | | Run assertions | `momentic@3.33.0` | | Web `fill` alias | `momentic@3.41.0` | | Bare AI-action goals | `momentic@3.52.0`, `momentic-mobile@1.28.0` | | Mobile while loops | `momentic-mobile@1.26.0` | Use the explicit `act:` form when a project may run an older CLI. Bare AI-action goals always select AI action V3. ## File types Browser test: ```yaml fileType: momentic/test/v2 id: opal-river-sparrow url: https://example.com steps: [] ``` Browser module: ```yaml fileType: momentic/module/v2 id: indigo-cedar-bridge name: Login steps: [] ``` Mobile test: ```yaml fileType: momentic/mobile-test/v2 id: sunlit-forest-window platform: android steps: [] ``` Mobile modules use `fileType: momentic/mobile-module/v2`; their `platform` defaults to `android`. IDs must be unique within the Momentic organization. Momentic creation tools, including MCP, generate readable slugs with a variable number of words. A hand-authored ID can be any stable lowercase kebab-case slug up to 36 characters. Legacy UUID IDs remain valid. The serializer normally omits `version`, default browser type, and default viewport metadata. ## Test sections Tests can contain `before`, `steps`, and `after`. Modules contain `steps`. Do not add legacy `SECTION` steps to V2 YAML. ```yaml before: - navigate: /login steps: - type: text: "{{ env.USER_EMAIL }}" into: Email after: - authSave ``` Browser tests can also define run assertions, which Momentic evaluates against the run recording: ```yaml runAssertions: - A Saved confirmation appears after the form is submitted ``` ## Step shapes Each list item is exactly one step. A preset step can be a bare command, a command with a scalar payload, or a command with detailed options: ```yaml - refresh - click: Submit - click: on: Submit timeout: 5000 ``` Detailed options must be nested under the command key. Do not write sibling options beside a scalar command: ```yaml # Invalid - click: Submit retries: 1 ``` Detailed steps can use `saveAs`, `retries`, `skipped`, and `comment`. Preserve existing metadata unless the requested change requires updating it. ## AI actions A multi-word bare string is an AI action V3 goal on supported CLI versions: ```yaml - Add a Gravity Blanket to the cart and open checkout ``` Known platform-specific one-word strings such as `refresh` on web and `killApp` on mobile remain preset steps. Unknown one-word strings are invalid, which prevents misspelled preset commands from silently becoming AI actions. Use `act` when the action needs options: ```yaml - act: goal: Complete checkout as a guest version: "3" precondition: The cart contains one Gravity Blanket postcondition: An order confirmation number is visible cache: false ``` `precondition`, `postcondition`, and `cache` apply to V3. A postcondition states the durable product outcome that must hold before the action passes. The shorthand and explicit forms have identical execution and cache semantics. `advanced.aiActionShorthand` only controls which form Momentic writes when it serializes a V3 action; it does not control whether shorthand can be parsed. ## Type and fill `type` dispatches keyboard events and can set a delay or clear strategy. `fill` replaces the input value in one operation without per-keystroke events. ```yaml - type: text: ada@example.com into: Email delay: 25 clear: inputs - fill: text: secret-password into: Password ``` Both commands support a scalar payload when the intended input already has focus: ```yaml - type: hello world - fill: replacement value ``` ## Conditionals and while loops Place the assertion directly inside `if`; V2 conditionals do not have a `condition` wrapper or an `else` branch: ```yaml - if: assert: The cart is empty then: - click: Add to cart ``` A while loop has a `do` list plus an inline assertion, `maxIterations`, or both: ```yaml - while: assert: A Load more button is visible do: - click: Load more maxIterations: 10 ``` When there is no assertion, `maxIterations` is required. Keep loops finite. ## Modules and parameters Invoke a module with a scalar path when it has no inputs: ```yaml - module: ../modules/login.module.yaml ``` Use the detailed form for inputs. Each input can be a shorthand string, `{ string }`, or `{ javascript }`: ```yaml - module: path: ../modules/login.module.yaml inputs: EMAIL: "{{ env.USER_EMAIL }}" TENANT: string: acme NOW: javascript: return new Date().toISOString() ``` Prefer object-form module parameter declarations: ```yaml parameters: - name: EMAIL - name: TENANT default: string: acme enum: [acme, globex] ``` The legacy bare-string `parameters`, `defaultParameters`, and `parameterEnums` fields remain valid for backward compatibility. ## File references Relative file references resolve from the YAML file containing the step. A path inside a module is relative to that module, not the top-level test. ```yaml - javascript: ./scripts/setup.js - authLoad: ./auth-state.json - authSave: ./auth-state.json - module: ../modules/login.module.yaml ``` Do not use absolute paths, `~`, or `file://` for local V2 references. ## Browser preset steps | Key | Purpose | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `click` | Click on an element on the page. | | `doubleClick` | Double-click an element on the page. | | `rightClick` | Right-click an element on the page. | | `hover` | Hover over an element on the page. Automatically scrolls the element into view, so can double as a scroll-to. | | `blur` | Remove focus from an element on the page. | | `focus` | Focus an element on the page. | | `type` | Type the specified text into an element. | | `fill` | Replace an input's value in one operation without per-keystroke events. | | `select` | Select an option from a native HTML `