trace2e recorder

Writing end-to-end tests by hand is slow: you inspect the DOM, guess at selectors, run, fail, repeat. trace2e recorder removes that loop — you just use your website once, and get a real Playwright test out of it. Record a flow in Chrome (log in, search, buy, sign up — anything), upload it to your trace2e daemon, and run /trace2e in Claude Code. It writes a complete, maintainable Playwright spec from what you actually did. WHY TRACE2E INSTEAD OF A PLAIN RECORDER Most recorders dump brittle CSS/XPath selectors that break on the next deploy. trace2e records the way Playwright wants you to test: ✔ Semantic locators first — getByRole, getByLabel, getByText — with ranked fallbacks, so tests survive UI refactors ✔ Fragile-selector warnings — positional selectors are flagged in the panel with one-click retargeting before they ever reach a test ✔ Secrets never captured — password and one-time-code fields automatically become {{PASSWORD}}-style placeholders; the real value never enters the recording, the upload, or the generated test ✔ Real test structure, not a click log — the AI generation step produces readable specs with assertions, waits and variables, ready for CI BUILT FOR REAL FLOWS, NOT JUST HAPPY PATHS • Element picker to add assertions ("this heading is visible", "this text equals…") and waits by clicking the page • URL assertions, waits and delays for redirects and slow backends • Custom JS steps and before/after hooks (reset a DB, fetch an OTP) for flows plain recorders can't express • Screenshots per step so the test generator — and your teammates — see what happened • Pause/resume recording, edit or delete steps before uploading MADE FOR TEAMS Point everyone's extension at one shared daemon: each teammate signs in with their own account and API token, recordings are private per user, and flows are organized into projects. A web dashboard lets you browse, edit and re-organize recordings — rename steps, fix a URL, reorder — without re-recording. Prefer solo? Run the daemon locally with one command. HOW IT WORKS 1. Open the side panel, name the flow, hit Record 2. Use your site like a real user; add checkpoints with the picker 3. Upload to your daemon 4. In Claude Code: /trace2e your-flow-name → a Playwright spec appears in your repo SETUP You'll need the trace2e daemon (free, open source — run it locally or self-host for your team) and Claude Code for test generation. Configure the extension in its options page: daemon URL + your API token. Docs, daemon and client binaries: github.com/erickdsama/trace2e Recordings are only captured while you press Record, and are only sent to the daemon URL you configure — never to anyone else.