Point Cartographer at any URL. It crawls every route, traces every flow, and writes Playwright tests you actually own — in a real browser, with real reasoning, on a budget you set.
Molar is a release guard with four surfaces. Cartographer is the one that reads your app end-to-end and writes the tests. It feeds the other three.
Crawls routes, plans goals, runs flows in a real browser, exports owned Playwright code. The reader and writer.
Stateful mirrors of Stripe, SendGrid, Twilio, Postgres. Real APIs without real side effects.
Runs Cartographer's flows against live production on a schedule. Catches bugs before users do.
Replay any failed run like a debugger. Diff against last green to see exactly what changed.
BFS from any seed URL. Resolves auth gates, follows forms, maps routes into a graph you can browse, filter, and diff between deploys.
Write a goal in plain English. A LangGraph planner decomposes it into steps; the actor drives a real browser; the verifier escalates only when it needs to.
7-stage export pipeline: prune → rank selectors → cluster page objects → harvest assertions → generate → lint → sandbox-verify → heal. Drops a Playwright spec into your repo.
Every step runs axe accessibility, visual diff against a baseline, and optional VLM sampling. Findings land in an inbox with dedupe, severity, and dismissal.
Same run_id everywhere. Drive Cartographer from Cursor / Claude Code / Windsurf via MCP, from your terminal with cartog, or from the web dashboard. They share state.
Show Cartographer the flow once via the Chrome extension. It chunks the rrweb session by intent, deduplicates against the route map, and replays deterministically.
No fixtures. No YAML. No DSL. Cartographer reads what's there and reasons about what to do next, just like a careful human QA engineer would — except in parallel, on every flow, every commit.
A BFS crawler with anti-bot defaults walks every reachable route from a seed URL. It captures DOM hashes, status codes, headers, screenshots, and discovered actions. The result is a queryable site graph — not a sitemap.xml dump.
Planner reads the route map, the natural-language goal, and any cached skills from a prior demo. It produces a substep list. The actor executes; the verifier checks; the grounding ladder escalates only when accessibility-tree grounding isn't enough.
When a run succeeds, the export pipeline drops a clean Playwright spec into your repo (or a presigned zip). Page objects clustered automatically. Selectors ranked by stability. Assertions harvested from what the agent actually verified.
Hand the spec to Molar Guard and Cartographer will keep running it against staging and production on a schedule. Failures route back to the diff that introduced them, attributed to the human or agent who wrote it.
Most agent UIs show you a flat log and call it observability. Cartographer's run detail shows you reasoning, grounding tier, selector candidates, before/after screenshots, and the exact moment Tier 0 escalated to Tier 1 — for every step.
2026 is the first year more than half of merged code is written by an agent. The PR-time E2E suite, the post-deploy monitor, the customer support ticket — none of that scales when a Sonnet checkpoint silently inverts a coupon calculation at 3am.
Cartographer answers searches for agentic crawl, app mapping, Playwright test generation, and autonomous E2E authoring — with a site graph you can query and tests you actually own.
Playwright codegen records one session. Cartographer crawls your app (BFS from a seed URL), builds a route graph, then runs goal-driven flows and exports owned .spec.ts files through a 7-stage pipeline. Compare Molar vs Playwright.
Yes — Cartographer resolves auth gates, stores session state, and maps routes behind login. Safe production crawl with configurable rate budgets.
No — it augments it. Export new specs into your repo, or feed existing flows to Guard for PR gating and production monitoring.
Flows that hit Stripe, email, or SMS run against Molar Clones so the agent can test checkout and webhooks with zero production side effects.
Cartographer is one of four Molar surfaces. You can pay for it on its own — by run-hours and pages crawled — or get it included in the Molar suite.
Sixty seconds from your seed URL to a working Cartographer agent mapping your app, running goals, and writing Playwright tests you keep.