.molar.md config

Project configuration at the repo root — base URLs, auth aliases, clones, and scenario intents.

.molar.md

.molar.md is your project's Molar configuration — a single, human-readable file at the repo root that tells Molar what your app is, where it lives, and how to test it. npx molar-agent init creates it.

Anatomy

# My App

base_url: https://staging.myapp.com
prod_url: https://myapp.com

## Auth
- credentials_alias: staging-admin   # resolved from your vault, never inline

## Clones
- stripe        # use the Stripe clone for billing flows
- email         # use the email clone for verification

## Scenarios
- checkout: a user buys one item and reaches the receipt
- signup: a new user registers and confirms their email

How it's used

  • Cartographer reads base_url to crawl and ## Scenarios to know which flows you care about.
  • Guard runs the scenarios under .molar/scenarios/ against base_url (PR gate) and prod_url (production monitor / shadow-prod diff).
  • Clones listed under ## Clones are spun up hermetically for the run, so tests never touch the real vendor.

Scenarios directory

Compiled, runnable specs live in .molar/scenarios/*.spec.ts (Playwright). You can hand-edit them or let Cartographer generate and heal them. Keep them in version control — they are the contract Guard enforces.

Secrets

Never inline secrets in .molar.md. Reference a credentials_alias; the actual values are stored encrypted and resolved at run time. See BYOK for model keys.