browser block sets defaults for every web test in the project. A test’s
Test options override the ones it exposes, such as the browser type.
momentic.config.yaml
Identity
Default browser used by all tests in the project.
momentic.config.yaml
Chromium: lightweight, open-source browser with a basic feature set. The same engine Playwright and Cypress use.Google Chrome: full Google Chrome build with PDF rendering and WebGL.Chrome for Testing: a versioned Chrome build for test automation, without auto-update.
User agent string sent on every request. Defaults to the current Chrome
desktop UA. Set to
null to disable the default override and use the
browser’s native user agent (which then matches the runner’s OS).momentic.config.yaml
momentic.config.yaml
Default
IANA timezone.
Defaults to
America/Los_Angeles. Per-test settings override this.momentic.config.yaml
Use the host machine’s timezone instead. When
true, all timezone settings
(project- and test-level) are ignored. Default: false.momentic.config.yaml
Timeouts
Maximum wait time for a page to load, in milliseconds. Applies to new tabs
and navigation events. Default:
8000.momentic.config.yaml
Continue after page-load timeouts instead of failing the test. Default:
false.Enable this for applications that render usable content even though the browser
does not report that the page finished loading. Momentic waits up to
pageLoadTimeoutMs for each new document. If that wait times out, later
page-state collections for the same document skip it. A new document or tab
receives its own full wait. momentic.config.yaml
Maximum wait time for smart waiting
between steps, in milliseconds. Default:
5000.momentic.config.yaml
Default maximum wait time for element check
assertions to become true, in seconds. Element check steps with an explicit
timeout are unaffected. Default:
5.momentic.config.yaml
Default delay between keystrokes for type steps, in milliseconds. Type steps
with an explicit delay are unaffected. Increase this if your app needs more
time to react to each keystroke. Default:
25.momentic.config.yaml
How long each key stays held between keydown and keyup for press steps, in
milliseconds. Press steps with an explicit delay are unaffected. Default:
0.momentic.config.yaml
Execution timing
Wait between steps in a step list, in milliseconds. The first executed step
has no delay, including when earlier steps are skipped. A single-step list
has no delay. Values range from Environment browser settings override this value, and the test-level
0 to 10000. Default: 0.momentic.config.yaml
slowMoMs
setting overrides both. For a single run, pass
--slow-mo <milliseconds>
to override all three without changing your configuration files.Headers, storage, and permissions
Extra headers
Set Set
browser.extraHeaders to add HTTP headers to browser requests. Headers
apply to every requested host, including third-party hosts.Load credentials from
environment variables instead of writing
tokens into your config:momentic.config.yaml
AUTH_TOKEN in your shell or CI secrets, then select this environment with
npx momentic run --env staging. See
Secrets for .env files and other
variable-loading options.Local storage values to seed per origin before the test starts. Origin must
include scheme, host, and (if non-default) port. Useful for feature flags or
cached auth.
momentic.config.yaml
Paths to unpacked Chrome extension directories. Each directory must contain
See Load Chrome extensions for
project setup, local editor steps, and troubleshooting.
manifest.json. Momentic loads the extensions before the test starts.Use Chromium with remoteBrowser: false. Hosted browsers and the cloud
dashboard don’t support extensions. Google Chrome 137 and later no longer
support this extension-loading mechanism, and Momentic doesn’t support loading
extensions in Chrome for Testing.Relative paths resolve from the directory where you launch Momentic. The
directories must exist on the machine running the test, including in CI.
Configure one or more extensions in momentic.config.yaml:momentic.config.yaml
Browser permissions to auto-grant during the run. When omitted, all
permissions are granted.
momentic.config.yaml
Ignore HTTPS errors like self-signed certificates. Useful for internal or
development environments. Default:
false.momentic.config.yaml
Performance and stability
Run tests on Momentic hosted browsers instead of a local Chromium. Applies to
momentic run only; the editor and the MCP server always use a local
browser. See
hosted test environments.
Default: false.momentic.config.yaml
Disable intensive graphical operations (WebGL, hardware-accelerated raster).
Speeds up runs on machines without a dedicated GPU. May break sites that
rely on WebGL. Default:
false.momentic.config.yaml
Disable Chrome’s zygote process. Can reduce process overhead but may break
features that depend on the zygote. Default:
false.momentic.config.yaml
Block FullStory scripts from mounting during the run. FullStory’s high-volume
DOM scanning can crash automated pages.
momentic.config.yaml
Run-data capture
Disable Momentic’s default recording of console logs, network requests, HTML
snapshots, and element screenshots. The recordings feed the run viewer’s
debug tabs. Disabling can improve performance on sites with high log volume.
Default:
false.momentic.config.yaml
Page handling
Automatically expand iframes so Momentic can interact with elements inside
them without configuring Act within iframe per step. Default:
false.momentic.config.yaml
Default:
true. Momentic reads the browser’s already-computed accessibility
data. This is fast and stable, but can be incomplete on pages that never
finish loading. Set to false to force the browser to rebuild the tree from
scratch on every read (more complete on slow pages, but slower, and can
crash the browser on very large pages).momentic.config.yaml
Default:
true. Controls whether zero-opacity elements are exposed to the
AI locator agent and available to interactive steps. true: show all elements regardless of opacity.false: filter zero-opacity elements out of the page context and block interactions on them. More closely mimics a human user.inputs-only: still show zero-opacity<input>elements (useful for UI frameworks that style hidden inputs).
momentic.config.yaml
Locator and cache tuning
Default: Without valid Memory, the locator uses eligibility
guidance to find a matching target. This setting does not change memory-backed
checks. The browser validates visibility after locating the element.This setting does not change other element checks, interactive steps, or older
locator agents. Set it to
false. Make the V5 locator respect Momentic’s element eligibility
markers during positive visibility checks.
This helps it select a visible target instead of a matching wrapper that has
no rendered box, such as an element styled with display: contents.Enable it in momentic.config.yaml with a V5 locator:momentic.config.yaml
false or omit it to keep the default behavior. It
does not invalidate existing step caches.Default:
always. Use Momentic’s algorithm to find the top-most interactable
element when a target is covered by another element. Other frameworks throw or
require a forced click; this redirects to the covering element instead.false: disabled.true: only redirects onCLICKsteps (backward compatibility).always: redirects on all interactive steps.
momentic.config.yaml
When
globalLocatorRedirect can’t find a valid redirect target, force-click
the original element instead of failing actionability checks.
Default: false.momentic.config.yaml
Resolve element coordinates with a visual heuristic and use those coordinates
for clicks, hovers, and typing. Default:
false.momentic.config.yaml
Ignore the
href attribute when matching cached anchors. Useful on sites
with auto-generated or rotating links. Only applies when the anchor has text
content. Default: false.momentic.config.yaml
Disable Levenshtein distance validation when resolving cached elements. When
enabled, the cache accepts any element that passes CSS/hybrid selector matching
and requirements checks without comparing its serialized HTML to the cached
version. Default:
false.momentic.config.yaml
Disable HTML l-dist and template-matching cache fallbacks. Faster but less
accurate. Cache entries can occasionally resolve to the wrong element.
Default:
false.momentic.config.yaml
Default:
prefer. Hybrid selectors combine text content, classes, attributes,
parent hierarchy, and shadow DOM piercing to identify elements more reliably
than CSS selectors.off: disabled.test: save and resolve hybrid selectors, but report mismatches to Momentic without using them.prefer: resolve with hybrid selectors first, fall back to CSS.always: only use hybrid selectors; fall back to AI on miss.
momentic.config.yaml
AI context filtering
Extra HTML attributes that should never be pruned from AI context. Common
testing attributes (
data-test-id, aria-label, etc.) are always
important. Suffix with * for a prefix match.momentic.config.yaml
CSS class names that mark an element as important. Matching elements are
never pruned from AI context. Suffix with
* for a prefix match.momentic.config.yaml
HTML attributes to strip from AI context and ignore when matching cached
elements. Use this for attributes whose values change between renders (e.g.
framework-generated If the attribute is genuinely useful for identifying elements, list it under
for IDs) that otherwise invalidate the cache every
run.
Suffix with * for prefix matches.momentic.config.yaml
browser.importantAttributes instead.