e2e 0.16.0 → 0.18.0

package/docs/migrate/playwright.mdx

@@ -1,10 +1,33 @@
 ---
 title: From Playwright
 description: Run e2e alongside Playwright and migrate tests one file at a time.
+icon: "/images/icons/playwright.svg"
 ---
 
-`@e2e-dev/web` uses your installed Playwright when its version satisfies
-the engine's peer dependency (`>=1.63.0 <2`). Both runners can stay in one
+import { SetupPrompt } from '../snippets/setup-prompt-card.jsx';
+
+export const migrationPrompt = `Migrate this project's Playwright tests to e2e, one spec at a time. Docs: \`https://e2e.tester.army/docs/migrate/playwright.md\`
+
+1. Read the migration guide above. It maps every Playwright config key, API, and CLI flag to e2e and marks what e2e does not have yet.
+2. If the project has no e2e config (\`e2e.config.ts\` or \`e2e.config.mts\`), run \`npx e2e init --yes\` (or the pnpm or bun equivalent). It writes a config and an example test, and installs nothing yet.
+3. Read the e2e skill (\`npx e2e guide\` prints it, \`npx e2e guide <topic>\` prints a topic) and follow it for every step below.
+4. If you ran init, ask me which model to use for agent steps: a ChatGPT, GitHub Copilot, OpenCode Console, or SuperGrok subscription, an API key, or a local model. Configure it with its provider package. If it needs a sign-in, give me the \`npx e2e login\` command and wait until I confirm.
+5. Port \`playwright.config.ts\` into the e2e config with the guide's Config tables. \`baseURL\` and \`webServer\` become the target's \`app\`, \`projects\` become \`targets\`, and browser options under \`use\` (viewport, locale, testIdAttribute) become \`web(...)\` options; \`trace\`, \`video\`, and the timeouts are top-level keys. Keep \`@playwright/test\` installed and the two file patterns apart.
+6. Install dependencies.
+7. List the Playwright specs and ask me which one to move first. Suggest a flow whose steps change often, such as a wizard or a checkout.
+8. Rewrite that spec as a \`.e2e.ts\` file under \`tests/\` (e2e runs \`tests/**/*.e2e.ts\` by default). Map each \`page\` call to \`screen\`, \`app\`, or \`browser\` with the guide. String names in e2e queries match the whole text, case-sensitive, so add \`{ exact: false }\` or a RegExp where the Playwright query matched a fragment. Where the guide marks a feature missing, use the workaround it gives, or leave that test in Playwright and tell me why.
+9. Keep navigation and the final assertions deterministic, with \`app.open()\` and locator assertions. Where a run of scripted interactions breaks often, propose an \`agent.act\` goal for it instead.
+10. Run the new file with \`npx e2e run <file>\` and fix it until it passes. Keep the Playwright spec until I confirm it can go.
+11. Summarize which tests moved, which stayed in Playwright, and why.`;
+
+<SetupPrompt>
+
+<Prompt description={migrationPrompt} children={migrationPrompt} actions={["copy", "cursor"]} />
+
+</SetupPrompt>
+
+`@e2e-dev/web` brings its own pinned `playwright-core`, so your
+`@playwright/test` version is yours to keep. Both runners can stay in one
 project. e2e reads `e2e.config.ts` and finds `tests/**/*.e2e.ts` by default,
 so keep the two file patterns apart.
 
@@ -27,7 +50,7 @@ A Playwright key the runner recognizes (`testDir`, `baseURL`, `webServer`,
 | Playwright | e2e | Status |
 | --- | --- | --- |
 | `use.baseURL` | `app: { url }` on the target | renamed |
-| `webServer` | `app: { url, command }` on the target, see [Starting your app](/starting-your-app) | renamed |
+| `webServer` | `app: { url, command }` on the target, see [Starting your app](/web#starting-your-app) | renamed |
 | `webServer` array | `app: { url, command }` on each target; targets declaring the same command share one process. Other dependency processes are not started by this version | missing |
 | `webServer.reuseExistingServer` | `app.command: { reuseExisting: true }`; CI ignores it | renamed |
 | `globalSetup`, `globalTeardown` | not yet; `test.setup` for sign-in, hooks and fixtures for setup code | missing |
@@ -59,7 +82,8 @@ A Playwright key the runner recognizes (`testDir`, `baseURL`, `webServer`,
 | `use.trace` | `trace` with the same modes (`'off'`, `'on'`, `'retain-on-failure'`, `'on-first-retry'`, `'on-all-retries'`), at the top of the config, per target, `test('x', { trace }, ...)`, or `--trace [mode]` for one run; the default differs, see [below](#defaults-that-differ) | same |
 | `use.video` | `video` with the same modes as `trace`, at the top of the config, per target in place of a project, `test('x', { video }, ...)` in place of `test.use`, or `--video [mode]` for one run | same |
 | `use.headless: false` | `--headed` on the CLI | renamed |
-| `use.locale`, `timezoneId`, `colorScheme`, `geolocation`, `permissions` | not yet | missing |
+| `use.locale`, `use.timezoneId` | `web({ locale, timezoneId })` | renamed |
+| `colorScheme`, `geolocation`, `permissions` | not yet | missing |
 | `use.userAgent` | `web({ userAgent })` | renamed |
 | `devices['iPhone 15']`, `deviceScaleFactor`, `isMobile`, `hasTouch` | not yet; `web({ viewport })` sets the size only | missing |
 | `ignoreHTTPSErrors`, `bypassCSP`, `offline`, `launchOptions`, `proxy` | not yet | missing |
@@ -139,7 +163,9 @@ what to do today.
 | `fill(value)` | the same; also takes a `Secret` | same |
 | `pressSequentially(text, { delay })` | the same; keystrokes through the platform keyboard, a `Secret` is refused | same |
 | `press(key)` | the same; modifiers join with `+`, see the [key grammar](/reference/engine#keys) | same |
-| `clear()`, `check()`, `uncheck()`, `focus()`, `hover()`, `selectOption()`, `setInputFiles()`, `dragTo()` | the same | same |
+| `clear()`, `focus()`, `hover()`, `setInputFiles()`, `dragTo()` | the same | same |
+| `check()`, `uncheck()` | the same, except for a control the click removes or navigates away from, such as a radio the app replaces with its selected view: the click landed, so the action passes, even when the app renders an unchecked control in its place. Playwright fails it because it cannot read the state back. Assert on what replaced the control | by design |
+| `selectOption('pro')` | `selectOption('Pro')`: a string matches the option's label only, where Playwright matches its value or its label; `selectOption({ value: 'pro' })` for the value | by design |
 | `selectOption(['a', 'b'])` | not yet; one option per call. An array is `INVALID_ARGUMENT` | missing |
 | `setInputFiles({ name, buffer })` | not yet; paths only, resolved from the project root | missing |
 | `scrollIntoViewIfNeeded()` | `scrollIntoView()` | renamed |
@@ -149,8 +175,7 @@ what to do today.
 | `isChecked()` | the same on a checkbox, radio, or `aria-checked` node; `false` on any other node, where Playwright throws | by design |
 | `isHidden()`, `isDisabled()` | the same | same |
 | `isEditable()` | not yet | missing |
-| `waitFor({ state: 'visible' })`, `'hidden'` | the same | same |
-| `waitFor({ state: 'attached' })`, `'detached'` | not yet; `expect(locator).toBeAttached()` and `.not.toBeAttached()` | missing |
+| `waitFor({ state: 'visible' })`, `'hidden'`, `'attached'`, `'detached'` | the same | same |
 | `locator.evaluate(fn)`, `evaluateAll(fn)` | not yet; `browser.evaluate(fn, selector)` with a CSS selector argument | missing |
 | `locator.screenshot()` | not yet; `app.screenshot(label)` captures the viewport | missing |
 | `innerHTML()`, `dispatchEvent()`, `selectText()`, `blur()`, `highlight()` | not yet; `browser.evaluate` | missing |
@@ -173,14 +198,14 @@ what to do today.
 | `toHaveText(['a', 'b'])`, `toContainText([...])` on several matches | the same: `toHaveText` needs the count to match, `toContainText` an ordered subsequence | same |
 | `toBeChecked({ checked: false })`, `toBeEnabled({ enabled })`, `toBeVisible({ visible })`, `toBeAttached({ attached })` | the same | same |
 | `{ ignoreCase }` on `toHaveText()`, `toContainText()`, `toHaveAccessibleName()`, `toHaveAttribute(name, value)` | the same | same |
-| `toBeChecked({ indeterminate })`, `{ useInnerText }`, `toHaveURL(url, { ignoreCase })` | not yet; `INVALID_ARGUMENT`, so the matcher never passes on its default | missing |
+| `toBeChecked({ indeterminate })`, `{ useInnerText }` | not yet; `INVALID_ARGUMENT`, so the matcher never passes on its default | missing |
 | `toHaveAttribute('aria-selected', 'true')`, `'aria-expanded'` | `toBeSelected()`, `toBeExpanded()` | renamed |
 | a positive matcher on several matches | `LOCATOR_AMBIGUOUS` at once; narrow with `filter`, `first`, or `{ visible: true }` | by design |
 | `toBeAttached()` | the same; passes on a hidden match too | same |
 | `toBeEmpty()`, `toBeInViewport()`, `toBeEditable()`, `toHaveRole()`, `toHaveAccessibleDescription()` | not yet | missing |
 | `expect(locator).toHaveClass(cls)` | `expect(browser).toHaveClass(locator, cls)`; a DOM fact is asserted through `browser`; reads the `class` attribute, so `''` matches `class=""` and not a missing attribute | web only |
 | `toHaveCSS()`, `toHaveId()`, `toHaveJSProperty()`, `toContainClass()`, `toHaveValues()` | not yet; `browser.evaluate` plus a value matcher | missing |
-| `expect(page).toHaveURL()`, `toHaveTitle()` | `expect(browser).toHaveURL()`, `toHaveTitle()` | web only |
+| `expect(page).toHaveURL()`, `toHaveTitle()` | `expect(browser).toHaveURL()`, `toHaveTitle()`; `toHaveURL` takes `ignoreCase` | web only |
 | `toHaveScreenshot()`, `toMatchSnapshot()` | not yet; `agent.assert('...', { vision: true })` is a judgment, not a pixel diff | missing |
 | `toMatchAriaSnapshot()` | not yet | missing |
 | `expect(value).toBe()`, `toEqual()`, `toMatch()`, `toBeTruthy()`, `toBeCloseTo()` and the rest | the same, except `toContain`, below, see [value matchers](/reference/expect#value-matchers) | same |
@@ -219,9 +244,9 @@ what to do today.
 | Playwright | e2e | Status |
 | --- | --- | --- |
 | `page.route(pattern, handler)` | `browser.route(pattern, handler)`; a string or `RegExp` pattern, no predicate function; the handler decides exactly once | web only |
-| `route.fulfill({ json, body, status, headers })` | the same; `json` or `body`, never both | web only |
-| `route.fulfill({ path, contentType })`, `route.fetch()` | not yet; read the file in the test and pass `body` | missing |
-| `route.continue(overrides)`, `route.abort(code)` | `continue()` and `abort()` take no arguments | missing |
+| `route.fulfill({ json, body, path, status, headers, contentType })` | the same; one of `json`, `body`, or `path`, and `path` is relative to the project root | web only |
+| `route.continue({ url, method, headers, postData })`, `route.fallback()` | the same; a `url` goes through the navigation rule, and `fallback()` takes no overrides | web only |
+| `route.fetch()`, `route.abort(code)`, `route.fallback(overrides)` | not yet; `abort()` takes no error code | missing |
 | `page.unroute()` | `browser.unroute()` | web only |
 | `page.waitForResponse(pattern)` | `browser.waitForResponse(pattern)`: a string or `RegExp`, no predicate function; `url`, `status`, `headers`, `json()`, `text()` | web only |
 | `response.ok()`, `response.body()`, `response.request()` | not yet; `status` and `text()` | missing |
@@ -232,10 +257,11 @@ what to do today.
 | `page.waitForEvent('popup')`, `context.on('page')` | not yet; a window the app opens is not driven | missing |
 | `page.on('console')`, `page.on('pageerror')` | not yet; assert on what the page shows | missing |
 | `page.evaluate(fn, arg)` | `browser.evaluate(fn, arg)`; JSON in and out, no handles | web only |
-| `page.exposeFunction()`, `addInitScript()`, `addStyleTag()`, `setExtraHTTPHeaders()`, `emulateMedia()`, `clock` | not yet; `browser.evaluate` appends a `<style>` once the page is open, and returns `null` since its result must be JSON | missing |
+| `page.addInitScript(script, arg)`, `context.addInitScript()` | `browser.addInitScript(script, arg)`, or `web({ initScripts })` for every test; pass `{ content }` as a plain string | web only |
+| `page.exposeFunction()`, `addStyleTag()`, `setExtraHTTPHeaders()`, `emulateMedia()`, `clock` | not yet; `browser.evaluate` appends a `<style>` once the page is open, and returns `null` since its result must be JSON | missing |
 | `context.addCookies()`, `context.cookies()` | `browser.setCookies()`, `browser.cookies()` | web only |
 | `context.clearCookies()` | not yet; `app.clearState()` also clears other persisted state and recreates the context | missing |
-| `request` fixture | Node `fetch`, see [Testing APIs](/api-testing) | by design |
+| `request` fixture | Node `fetch`, see [API](/api-testing) | by design |
 | `context.storageState({ path })` | not yet; sessions are per run and encrypted, see [By design](#by-design) | by design |
 
 ### Test structure
@@ -284,9 +310,9 @@ what to do today.
 | `--update-snapshots` | no equivalent; there is no pixel assertion | missing |
 | `--list` | `npx e2e list`, with the same selection flags | renamed |
 | `npx playwright codegen` | `npx e2e explore` walks the app from a goal and reports what it found; `npx e2e mcp` gives a coding agent a live session so it writes the test while driving the app, see [Coding agents](/coding-agents) | renamed |
-| `npx playwright show-trace` | the same, on `trace/<name>.zip` under the attempt's artifact directory | same |
+| `npx playwright show-trace` | `npx playwright-core@1.63.0 show-trace` (`pnpm dlx` under pnpm), on `trace/<name>.zip` under the attempt's artifact directory | renamed |
 | `npx playwright show-report` | not yet; `.e2e/summary.md` from the `markdown` reporter | missing |
-| `npx playwright install` | still works; the engine also installs a missing browser once per run, before the run's clock starts | same |
+| `npx playwright install` | `npx @e2e-dev/web install`, for the Playwright version the engine pins; the engine also installs a missing browser once per run, before the run's clock starts | renamed |
 
 ## Page objects
 
@@ -421,8 +447,8 @@ Start with a flow whose interaction sequence changes often, such as a wizard
 or checkout; stable Playwright tests can stay where they are.
 
 <CardGroup cols={2}>
-  <Card title="Writing tests" icon="pen-to-square" href="/writing-tests">
-    Goals, checks, extraction, and where a deterministic call still belongs.
+  <Card title="Core concepts" icon="pen-to-square" href="/core-concepts">
+    Goals, assertions, and locators instead of scripted selectors.
   </Card>
   <Card title="Web engine reference" icon="masks-theater" href="/reference/web">
     Every option and every `browser` method.

package/docs/migrate/selenium.mdx

@@ -1,8 +1,32 @@
 ---
 title: From Selenium
 description: Rewrite Selenium flows in TypeScript with locators, retrying assertions, and agent goals.
+icon: "/images/icons/selenium.svg"
 ---
 
+import { SetupPrompt } from '../snippets/setup-prompt-card.jsx';
+
+export const migrationPrompt = `Migrate this project's Selenium tests to e2e, one flow at a time. Docs: \`https://e2e.tester.army/docs/migrate/selenium.md\`
+
+1. Read the migration guide above. It maps Selenium config and WebDriver calls to e2e.
+2. e2e tests are TypeScript. If the Selenium suite is Java, Python, or another language, ask me where the new test project should live, for example an \`e2e/\` folder with its own \`package.json\`.
+3. If that project has no e2e config (\`e2e.config.ts\` or \`e2e.config.mts\`), run \`npx e2e init --yes\` (or the pnpm or bun equivalent) there. It writes a config and an example test, and installs nothing yet.
+4. Read the e2e skill (\`npx e2e guide\` prints it, \`npx e2e guide <topic>\` prints a topic) and follow it for every step below.
+5. If you ran init, ask me which model to use for agent steps: a ChatGPT, GitHub Copilot, OpenCode Console, or SuperGrok subscription, an API key, or a local model. Configure it with its provider package. If it needs a sign-in, give me the \`npx e2e login\` command and wait until I confirm.
+6. Set the target's \`app\` to the URL every \`driver.get\` used, and the command that starts the app if the suite starts it. Move passwords and tokens into \`credentials\` or \`secrets\`.
+7. Install dependencies.
+8. List the page objects and the flows that use them, and ask me which to move first. Suggest one page object and its flows.
+9. Rewrite those flows as \`.e2e.ts\` files under \`tests/\` (e2e runs \`tests/**/*.e2e.ts\` by default). Prefer role, label, and test id queries on \`screen\` over \`By.id\`, CSS, and XPath. Replace explicit waits, implicit waits, and \`Thread.sleep\` with locator assertions, which retry. \`findElement\` takes the first match and e2e fails on several, so narrow those queries. Turn the page object's setup code into a fixture.
+10. Keep navigation and the final assertions deterministic, with \`app.open()\` and locator assertions. Where a run of scripted interactions breaks often, propose an \`agent.act\` goal for it instead.
+11. Run the new files with \`npx e2e run <file>\` and fix them until they pass. Keep the Selenium tests until I confirm they can go.
+12. Summarize which flows moved, which stayed in Selenium, and why.`;
+
+<SetupPrompt>
+
+<Prompt description={migrationPrompt} children={migrationPrompt} actions={["copy", "cursor"]} />
+
+</SetupPrompt>
+
 e2e tests use TypeScript, locators based on roles and labels, and assertions
 that retry until they pass or time out. A Java or Python suite needs to be
 rewritten. Run both suites while you move one flow at a time.
@@ -15,7 +39,7 @@ agent calls; the locator-based example below works without one.
 | Selenium | e2e |
 | --- | --- |
 | The URL in every `driver.get` | `app: { url }` on the target, then relative paths |
-| Starting the app in a script | `app: { url, command }`, see [Starting your app](/starting-your-app) |
+| Starting the app in a script | `app: { url, command }`, see [Starting your app](/web#starting-your-app) |
 | One driver per browser | One target per browser, `web({ browser: 'firefox' })` |
 | Selenium Grid | `workers` for parallelism; `connect` attaches to a remote Chromium over CDP, and a [browser provider](/browser#hosted-browsers) such as [Kernel](/integrations/kernel) leases hosted browsers |
 | `manage().window().setSize` | `web({ viewport })` |
@@ -101,8 +125,8 @@ Start with one page object and the flows that use it; its setup code can
 become a fixture.
 
 <CardGroup cols={2}>
-  <Card title="Writing tests" icon="pen-to-square" href="/writing-tests">
-    Goals, checks, extraction, and the deterministic APIs.
+  <Card title="Core concepts" icon="pen-to-square" href="/core-concepts">
+    Goals, assertions, and locators instead of scripted selectors.
   </Card>
   <Card title="screen reference" icon="crosshairs" href="/reference/screen">
     Every query, refinement, action, and read.

package/docs/mobile-ci.mdx

@@ -1,6 +1,7 @@
 ---
 title: Mobile CI
 description: Run iOS and Android tests on GitHub Actions, EAS Workflows, Bitrise, and Codemagic.
+icon: "mobile-screen-button"
 ---
 
 A mobile CI job does the same four things on every service: build the app
@@ -16,7 +17,7 @@ credentials, sharding, and exit codes; everything there applies here.
 | Machine | macOS with Xcode and a simulator runtime | Linux with KVM (nested virtualization) |
 | Build | Release simulator `.app`, no signing | Release `.apk` |
 | Device | A booted simulator | A booted emulator |
-| Node | 22.12 or later | 22.12 or later |
+| Node | 24.8 or later, or 22.22.3 or later on 22 | 24.8 or later, or 22.22.3 or later on 22 |
 
 Build Release on both platforms: a React Native or Expo debug build loads
 its JavaScript from Metro, which no CI job here starts, so the app opens on
@@ -115,7 +116,7 @@ simulator; swap in your own build command as long as it writes a simulator
 Release --device generic --no-bundler --output build/ios` builds without
 booting a simulator and writes the `.app` under `build/ios`.
 
-```yaml title=".github/workflows/e2e-mobile.yml"
+```yaml title=".github/workflows/e2e-mobile.yml" expandable
 name: e2e mobile
 
 on:
@@ -247,7 +248,7 @@ The iOS job runs on a macOS runner; the Android one needs a
 `nested-virtualization` Linux runner, the only EAS machines that can run the
 emulator:
 
-```yaml title=".eas/workflows/e2e.yml"
+```yaml title=".eas/workflows/e2e.yml" expandable
 name: e2e
 
 on:
@@ -357,7 +358,7 @@ booting both devices: `xcode-start-simulator` on macOS, and `avd-manager`
 with `wait-for-android-emulator` on Linux. Start the emulator before the
 Gradle build so it boots while the APK compiles.
 
-```yaml title="bitrise.yml"
+```yaml title="bitrise.yml" expandable
 format_version: '25'
 default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git
 
@@ -482,7 +483,7 @@ workflows:
 Android runs on a Linux instance. The Ubuntu image comes with AVDs named `emulator` (API 34),
 `emulator-35`, and `emulator-36`.
 
-```yaml title="codemagic.yaml"
+```yaml title="codemagic.yaml" expandable
 workflows:
   e2e-ios:
     name: e2e iOS

package/docs/mobile.mdx

@@ -1,10 +1,11 @@
 ---
-title: Testing iOS and Android
-description: Set up a simulator or emulator target, write a device test, and know what differs from the web.
+title: Mobile
+description: Set up a simulator, emulator, or connected phone as a target, write a device test, and know what differs from the web.
+icon: "mobile-screen"
 ---
 
-`@e2e-dev/mobile` runs tests on iOS simulators and Android emulators. It is
-built on [agent-device](https://github.com/callstack/agent-device).
+`@e2e-dev/mobile` runs tests on iOS simulators, Android emulators, and
+phones connected to your machine. It is built on [agent-device](https://github.com/callstack/agent-device).
 Tests use the same `agent`, `screen`, and `expect` APIs as browser tests.
 A test launches the configured app with `app.open()`; between tests the app
 stays where the last one left it.
@@ -178,6 +179,82 @@ mobile({ platform: 'ios', device: ['iPhone 17', 'iPhone 17 Pro'] })
 Without `device`, the engine uses booted devices up to the worker limit.
 If none are booted, it boots one. Two workers never drive the same device.
 
+## Physical devices
+
+agent-device drives a phone plugged into your machine the same way it
+drives a simulator, so a physical device needs no other engine or option.
+List what agent-device sees, then name the phone in `device` as it is
+listed:
+
+<CodeGroup>
+```bash npm
+npx agent-device devices --platform ios
+```
+
+```bash pnpm
+pnpm exec agent-device devices --platform ios
+```
+
+```bash bun
+bunx agent-device devices --platform ios
+```
+</CodeGroup>
+
+```ts
+mobile({ platform: 'ios', device: 'QA iPhone' })
+```
+
+Name a phone by its name, not its id. The engine reads a `device` string as
+an id only when it is a simulator UDID or an `emulator-<port>` serial, so a
+phone's UDID or adb serial is looked up as a name and not found. The first
+device with a matching name wins, so give each phone a unique name: two
+phones both called `iPhone` or `Pixel 8` would bind one phone to two
+workers. Without `device`, a connected phone counts as booted and joins the
+pool beside any booted simulators, so name it to be sure a run lands on it.
+
+Set the phone up once:
+
+- **iOS**: the phone is paired and trusted, unlocked, with Developer Mode
+  on. agent-device builds and signs its XCTest runner onto the phone, so set
+  `AGENT_DEVICE_IOS_TEAM_ID` to your team id and `AGENT_DEVICE_IOS_BUNDLE_ID`
+  to a unique reverse-DNS id (`com.example.agentdevice.runner`); the
+  signing profile must allow that id and `<id>.uitests`. Set them before the
+  first agent-device command, or run `npx agent-device daemon stop` after:
+  a running daemon keeps the environment it started with. The first run
+  builds the runner and takes longer. `app.appPath` must be a signed device
+  build: a simulator `.app` does not install on a phone.
+- **Android**: USB debugging is on and the phone is authorized, listed as
+  `device` in `adb devices`. `app.appPath` is the same `.apk`.
+
+`npx agent-device doctor` checks the setup, and
+`npx agent-device help physical-device` covers iOS signing in detail.
+
+Some device controls need a simulator or emulator, and fail on a phone with
+agent-device's message:
+
+- On an iPhone, every device setting is simulator-only: `app.permissions`
+  and `device.setPermission`, `app.clearState()`, `device.setNetwork`,
+  `device.setAirplaneMode`, `device.setLocation`, `device.clearLocation`,
+  `device.setAppearance`, the biometric methods, and `device.clearKeychain`.
+  So are `device.clipboard`, `device.setClipboard`, and `device.fold`. For a
+  fresh start, reinstall with `device.installApp(path, { reinstall: true })`,
+  with `app.bundleId` on the target or `app` in the options, so agent-device
+  knows which app to remove.
+- An older iPhone that `xcrun devicectl list devices` does not list is
+  driven without CoreDevice: taps, typing, and the screen work, but
+  installs, `--video`, `device.openLink`, and `app.launchArguments` fail.
+  Install the build from Xcode and pin `app.bundleId`.
+- On an Android phone, `device.setLocation` is emulator-only, and
+  `device.setBiometrics('fingerprint', ...)` works only where the phone
+  exposes `cmd fingerprint`.
+- `--video` on an iPhone is built from screenshots at about 15 frames a
+  second, and drops frames.
+- A phone is not this machine, so `localhost` in the app is the phone
+  itself. Point the app at your machine's network address, or on Android
+  forward the port with `adb reverse tcp:<port> tcp:<port>`.
+
+To run on phones in a device farm, see [Hosted devices](#hosted-devices).
+
 ## Hosted devices
 
 A `device` can also be a `DeviceProvider`: an object that leases one hosted
@@ -264,7 +341,7 @@ record leaves `record` out, and the engine records with agent-device.
 A provider against a typical session API has three requests: create a
 session, poll it until the daemon is reachable, stop it.
 
-```ts title="device-provider.ts"
+```ts title="device-provider.ts" expandable
 import type { DeviceProvider } from '@e2e-dev/mobile';
 
 /**
@@ -344,7 +421,7 @@ A device cloud agent-device speaks to itself needs no session API of your
 own: the provider allocates a lease through a daemon it starts for the run and
 hands the worker the lease scope as `client`.
 
-```ts title="device-cloud-provider.ts"
+```ts title="device-cloud-provider.ts" expandable
 import { createAgentDeviceClient } from 'agent-device';
 import type { DeviceProvider } from '@e2e-dev/mobile';
 
@@ -560,6 +637,17 @@ daemon (`npx agent-device daemon stop`) and reboot the simulator
 
 Do what it says.
 
+**`device.installApp()` on Android reports no bundle id or package.** The
+build installed, but agent-device could not say which package it is, so
+`app.open()` would have nothing to launch. agent-device 0.21.18 cannot parse
+the manifest of an APK built with aapt2 (every current Android build), so it
+falls back to the Android SDK's `aapt`, which it looks for under
+`ANDROID_SDK_ROOT`, `ANDROID_HOME`, or `~/Android/Sdk`, not the macOS default
+`~/Library/Android/sdk`. Without `aapt` it names only a package the install
+added, and a build already on the emulator adds none. Set the target's
+`app.bundleId`, or export `ANDROID_HOME` and stop the agent-device daemon
+(`daemon stop` below) so the next run starts it with the variable.
+
 **A timeout on the device.** A simulator boot, runner connection, or app
 launch that times out on the device is `ENGINE_FAILURE` with agent-device's
 message and hint, never one of e2e's own timeout codes (`LAUNCH_TIMEOUT`,
@@ -589,7 +677,7 @@ xcrun simctl shutdown <udid> && xcrun simctl boot <udid>
   <Card title="Mobile engine reference" icon="mobile-screen" href="/reference/mobile">
     Every option, the `device` fixture, and the tool pack.
   </Card>
-  <Card title="Writing tests" icon="pen-to-square" href="/writing-tests">
-    Goals, checks, and the deterministic APIs, on any platform.
+  <Card title="Locators" icon="crosshairs" href="/core-concepts#locators">
+    Exact taps, swipes, and checks with `screen` and `expect`, on any platform.
   </Card>
 </CardGroup>

package/docs/models.mdx

@@ -1,15 +1,21 @@
 ---
 title: Models
 description: Configure a model with your own subscription, an API key, or a local server.
+icon: "brain"
 ---
 
+import { ModelProvider } from './snippets/model-provider.jsx';
+
 Agent steps use the model configured in `e2e.config.ts`. You can use an
 [existing subscription](/subscriptions), an API key, or a local server.
+e2e uses the [AI SDK](https://ai-sdk.dev/providers). You can use
+[all AI SDK providers that support tool calls](#ai-sdk-providers).
 `e2e init` offers these choices and writes the config for you. For the first
 setup, follow the [quickstart](/quickstart#use-a-subscription-or-api-key).
 
-Tests without agent steps do not need a model. For the built-in agent,
-choose a model that supports tool calls and images. Agent steps need the `ai`
+Tests without agent steps do not need a model. [Decision models](/decision-models), hosted or locally
+hosted, such as Clef or Jev, can drive bounded actions and judge assertions through a custom executor. For the built-in agent,
+choose a model that supports tool calls and images. Steps using the built-in agent need the `ai`
 package installed, whichever provider you use:
 
 <CodeGroup>
@@ -77,7 +83,8 @@ const agent = { model: openai('gpt-6-luna') };
 ```
 
 Use `agent` as `agents.default`. Other AI SDK providers work the same way,
-with their own package, model IDs, and authentication settings.
+with their own package, model IDs, and authentication settings. See
+[AI SDK providers](#ai-sdk-providers).
   </Tab>
   <Tab title="Local or self-hosted">
 
@@ -103,11 +110,6 @@ Use `agent` as `agents.default`. Add `apiKey` if the server requires one.
 Model IDs depend on the provider. Gateways usually use `provider/model`;
 direct providers use their own model IDs.
 
-DeepSeek's V4 models (`@ai-sdk/deepseek`) think by default, and in that mode
-they refuse the forced tool choice agent steps ask for. The step is sent again
-with `auto` and an instruction to reply with tool calls only, and later steps
-on that model start that way, so thinking can stay on.
-
 ### Vercel OIDC instead of a key
 
 Without `AI_GATEWAY_API_KEY`, `gateway()` authenticates with a Vercel OIDC
@@ -145,6 +147,46 @@ An OIDC failure is the same `MODEL_PROVIDER_FAILED` as a bad key, and the AI
 SDK's message names only `AI_GATEWAY_API_KEY`. With no key set, check that the
 Vercel CLI is signed in and that `.vercel/project.json` exists.
 
+## AI SDK providers
+
+Select a provider. The three steps below show the setup for that provider.
+
+<ModelProvider show="select" />
+
+The list shows the AI SDK providers that support tool calls. A provider that
+is not in the list also works if it uses the AI SDK language model
+specification v2 or later. Its model must support tool calls and images.
+
+### Install the provider package
+
+Install `ai` and the provider package.
+
+<ModelProvider show="install" />
+
+### Set the credentials
+
+The provider reads its credentials from the environment. e2e does not load
+`.env` files. Export the variables in your shell or CI, or load the file in
+the config with [`process.loadEnvFile()`](/reference/config#loading).
+
+<ModelProvider show="env" />
+
+If a key is missing or wrong, the first agent step fails with
+`MODEL_PROVIDER_FAILED`. Some providers read the key when the config loads.
+For these providers, a missing key stops all runs with `CONFIG_LOAD_FAILED`.
+
+### Add the model to the config
+
+Set the model in `agents.default`. The model ID is an example. Use a model
+that supports tool calls and images.
+
+<ModelProvider show="config" />
+
+DeepSeek's V4 models (`@ai-sdk/deepseek`) think by default, and in that mode
+they refuse the forced tool choice agent steps ask for. The step is sent again
+with `auto` and an instruction to reply with tool calls only, and later steps
+on that model start that way, so thinking can stay on.
+
 ## Several models in one config
 
 Give agents different names to use different models:
@@ -192,12 +234,21 @@ Judgments use the current screen and the question, without the acting
 agent's transcript or summaries. Reports include the model used for each
 judgment. See [Custom executors](/executors) if you replace the built-in agent.
 
+`judge` takes an AI SDK language model. Clef and Jev use a different API;
+use the [decision executor](/decision-models) for `agent.act` and `agent.assert`.
+
 ## Data retention and compliance
 
 Model input is the redacted screen, the step instruction, and the
 screenshots the agent asks for. e2e reads nothing back from the provider
 after a response, so a run needs no state kept on the provider's side.
 
+Every model request names e2e: the `User-Agent` starts with
+`e2e/<version> (<platform>; <arch>)`, and `HTTP-Referer:
+https://tester.army/e2e` with `X-Title: e2e` attribute the traffic to e2e on
+the Vercel AI Gateway and OpenRouter. These replace the same headers set on
+the provider instance.
+
 **OpenAI and Azure OpenAI.** Every request carries `store: false` and a
 prompt cache key. The provider keeps no copy of the conversation, a
 reasoning model's earlier turns travel inline as encrypted content, and the
@@ -233,7 +284,7 @@ organizations with zero data retention.
 
 <CardGroup cols={2}>
   <Card title="Subscriptions" icon="key" href="/subscriptions">
-    Sign in with ChatGPT, Copilot, or SuperGrok.
+    Sign in with ChatGPT, Copilot, OpenCode Console, or SuperGrok.
   </Card>
   <Card title="Agents and personas" icon="users" href="/agents">
     Choose agents for tests and signed-in users.

package/docs/quickstart.mdx

@@ -1,16 +1,18 @@
 ---
 title: Quickstart
 description: Set up e2e with one prompt to your coding agent, or step by step.
+icon: "rocket"
 ---
 
+import { ModelProvider } from './snippets/model-provider.jsx';
 import { SetupPrompt } from './snippets/setup-prompt-card.jsx';
 
 export const setupPrompt = `Set up e2e end-to-end tests in this project. Docs: \`https://e2e.tester.army/docs/quickstart.md\`
 
 1. Run \`npx e2e init --yes\` (or the pnpm or bun equivalent for this project). It writes a web config using Vercel AI Gateway, an example test, the e2e skill, and MCP config. It installs nothing yet.
 2. Read the e2e skill (\`npx e2e guide\` prints it, \`npx e2e guide <topic>\` prints a topic) and follow it for every step below.
-3. Point the target at this app. For a web app, set its URL and the command that starts its dev server. For an iOS or Android app, replace @e2e-dev/web and playwright with @e2e-dev/mobile and rewrite the example test for the mobile engine.
-4. Ask me which model to use for agent steps: a ChatGPT, GitHub Copilot, or SuperGrok subscription, an API key, or a local model. Configure it with its provider package. If it needs a sign-in, give me the \`npx e2e login\` command and wait until I confirm.
+3. Point the target at this app. For a web app, set its URL and the command that starts its dev server. For an iOS or Android app, replace @e2e-dev/web with @e2e-dev/mobile and rewrite the example test for the mobile engine.
+4. Ask me which model to use for agent steps: a ChatGPT, GitHub Copilot, OpenCode Console, or SuperGrok subscription, an API key, or a local model. Configure it with its provider package. If it needs a sign-in, give me the \`npx e2e login\` command and wait until I confirm.
 5. Install dependencies, run the example test, and fix setup errors until it passes.
 6. Write one test for the most important user flow in this app, run it, and iterate until it passes.`;
 
@@ -29,7 +31,7 @@ The agent installs the [e2e skill](/coding-agents), so later prompts like
 "add a test for checkout" or "why did this run fail" work without more setup.
 
 <Note>
-Use Node.js 22.12 or newer. On Windows, run inside WSL. Mobile tests also
+Use Node.js 24.8 or newer (22.22.3 or newer on Node.js 22). On Windows, run inside WSL. Mobile tests also
 need Xcode with an iOS simulator runtime, or the Android SDK with an emulator.
 </Note>
 
@@ -63,7 +65,7 @@ need Xcode with an iOS simulator runtime, or the Android SDK with an emulator.
   <Tabs>
     <Tab title="Web">
     Start your app's dev server at `http://localhost:3000`, or set its address
-    in `e2e.config.ts`. You can also [let e2e start it](/starting-your-app).
+    in `e2e.config.ts`. You can also [let e2e start it](/web#starting-your-app).
 
     <Accordion title="Example web config and test">
     This config uses Vercel AI Gateway. The wizard configures the provider you chose.
@@ -122,7 +124,7 @@ test('Settings opens', async ({ app, screen }) => {
 ```
     </Accordion>
 
-    See [Testing iOS and Android](/mobile) to use your own app.
+    See [Mobile](/mobile) to use your own app.
     </Tab>
   </Tabs>
   </Step>
@@ -159,23 +161,33 @@ Connect the provider you chose in the wizard.
   | --- | --- |
   | ChatGPT Plus or Pro | `npx e2e login openai` |
   | GitHub Copilot | `npx e2e login github-copilot` |
+  | OpenCode Console (OpenCode Zen and OpenCode Go) | `npx e2e login opencode-console` |
   | SuperGrok or X Premium+ | `npx e2e login spacexai` |
 
   Copilot reuses your GitHub CLI login if available. See
   [Subscriptions](/subscriptions) for details.
   </Tab>
   <Tab title="API key">
-  Set your provider's key in the terminal where you run e2e. For Vercel AI
-  Gateway:
+  Select your provider. Install its package and set the variables it reads,
+  if any, in the terminal where you run e2e.
 
-  ```bash
-  export AI_GATEWAY_API_KEY="your-api-key"
-  ```
+  <ModelProvider show="select" />
+
+  <ModelProvider show="install" />
+
+  <ModelProvider show="env" />
+
+  Vercel AI Gateway reads `AI_GATEWAY_API_KEY`, or a
+  [Vercel OIDC token](/models#vercel-oidc-instead-of-a-key) in a project
+  linked with `vercel link`. OpenRouter reads `OPENROUTER_API_KEY`.
+
+  The wizard writes the config for Vercel AI Gateway, OpenRouter, and
+  OpenAI-compatible endpoints. For another provider, replace the model import
+  and `model` value in `e2e.config.ts`, and use `agent` as `agents.default`:
+
+  <ModelProvider show="model" />
 
-  A project linked with `vercel link` can use a
-  [Vercel OIDC token](/models#vercel-oidc-instead-of-a-key) instead.
-  OpenRouter uses `OPENROUTER_API_KEY`. See [Models](/models) for other
-  providers and local models.
+  See [Models](/models) for local models and more options.
   </Tab>
 </Tabs>
 
@@ -245,8 +257,8 @@ to watch a web test, `--no-cache` to skip replaying cached actions.
 ## Next
 
 <CardGroup cols={2}>
-  <Card title="Writing tests" icon="pen-to-square" href="/writing-tests">
-    Write goals, check outcomes, and extract data.
+  <Card title="Core concepts" icon="pen-to-square" href="/core-concepts">
+    Goals, assertions, and locators.
   </Card>
   <Card title="Signing in" icon="key" href="/authentication">
     Reuse an app login and keep passwords out of model input.