Skip to content

Open source Grok Bot alternative, Bring your own agent and subscription: message Claude Code, Codex, Gemini CLI, Cursor, Copilot and 40+ AI agents as bots on your own computer, from iPhone, Mac, Windows, Linux or terminal. Agent-agnostic and free. Also a Muse and Dots alternative. Built in Rust.

docs: drive native e2e steps with cua-driver instead of cluadex

leepokai41bef836db93
diff --git a/.claude/workflows/after-change.js b/.claude/workflows/after-change.js
index b596ee09..4530c399 100644
--- a/.claude/workflows/after-change.js
+++ b/.claude/workflows/after-change.js
@@ -116,7 +116,7 @@ ${JSON.stringify(refactors, null, 2)}
const walk = (flows, round) => agent(`End-to-end test a code change on the real apps, ${e2e} e2e as CLAUDE.md "End-to-end test every change" defines it (minimal: only this computer's platform; full: also Lima Linux and the UTM Windows VM, skipping and reporting a VM that isn't installed).
${scope}
${flows}
-Walk each flow once, as a person would, until it clearly passes or fails, and note what you saw; don't explore beyond the listed flows. Drive them as docs/guides/test-stack.md says: the desktop with the whole Playwright suite (\`npm run e2e\` in apps/desktop against \`npm run dev -- --cdp\`); the phones with one Maestro run under the Maestro lock, only the flows tagged \`smoke\` plus the tags of the areas the change touches (\`--include-tags\`, \`--shard-all\`), never the whole Maestro suite for now; Computer Use (cluadex) only for the native steps that guide lists. Add or update only the spec or flow each changed flow needs and touch no other test. Edit an existing test only for a reason that matches the behavior the change says it changes, and list each such edit with its reason in the check's evidence; without such a reason the failing test found a regression, so report it as a fail instead of changing the test. Keep it quick: short messages to bots, no sleeps or long-running tasks to stretch a turn, and when \`host/\` is unchanged start \`npm run dev\` with \`CODYNC_HOST_BIN\` pointing at an already built host instead of building one (docs/guides/dev-app.md). A failure the change didn't cause (the same without it) is \`preexisting\`, not \`fail\`. Stop the old build before installing the new one. In this worktree \`npm run dev\` in apps/desktop runs an isolated sandbox (docs/guides/dev-app.md#worktree-sandboxes); never stop or replace the shared Codync Dev, the production Codync app or another session's sandbox. In a worktree every client signs into the sandbox's Clerk test account, never the maintainer's: the sandbox runs with \`--cloud\`, and the iPhone and Android apps are seeded with \`npm run phone-account -- --ios <udid>\` / \`-- --android <serial>\` on the worktree's test devices: the iPhone on its own simulator \`Codync <sandbox name>\`, never one signed into the maintainer's account (\`npm run dev\` prints its udid, or the command that creates it when there is none yet; \`--prune\` deletes it later), Android on the shared \`codync_worktree\` emulator, the only one that may run (never a second AVD, never \`codync_api36\`, the maintainer's), one test at a time under its lock, with \`pm clear\` and the notification grant first (docs/guides/dev-app.md#worktree-sandboxes). When done, leave this worktree's \`npm run dev\` running (it is stopped after the merge) but stop anything else you started. A change with nothing to walk (CI, tools, docs) reports one not_run check saying so.`,
+Walk each flow once, as a person would, until it clearly passes or fails, and note what you saw; don't explore beyond the listed flows. Drive them as docs/guides/test-stack.md says: the desktop with the whole Playwright suite (\`npm run e2e\` in apps/desktop against \`npm run dev -- --cdp\`); the phones with one Maestro run under the Maestro lock, only the flows tagged \`smoke\` plus the tags of the areas the change touches (\`--include-tags\`, \`--shard-all\`), never the whole Maestro suite for now; Computer Use (cua-driver, in the background) only for the native steps that guide lists. Add or update only the spec or flow each changed flow needs and touch no other test. Edit an existing test only for a reason that matches the behavior the change says it changes, and list each such edit with its reason in the check's evidence; without such a reason the failing test found a regression, so report it as a fail instead of changing the test. Keep it quick: short messages to bots, no sleeps or long-running tasks to stretch a turn, and when \`host/\` is unchanged start \`npm run dev\` with \`CODYNC_HOST_BIN\` pointing at an already built host instead of building one (docs/guides/dev-app.md). A failure the change didn't cause (the same without it) is \`preexisting\`, not \`fail\`. Stop the old build before installing the new one. In this worktree \`npm run dev\` in apps/desktop runs an isolated sandbox (docs/guides/dev-app.md#worktree-sandboxes); never stop or replace the shared Codync Dev, the production Codync app or another session's sandbox. In a worktree every client signs into the sandbox's Clerk test account, never the maintainer's: the sandbox runs with \`--cloud\`, and the iPhone and Android apps are seeded with \`npm run phone-account -- --ios <udid>\` / \`-- --android <serial>\` on the worktree's test devices: the iPhone on its own simulator \`Codync <sandbox name>\`, never one signed into the maintainer's account (\`npm run dev\` prints its udid, or the command that creates it when there is none yet; \`--prune\` deletes it later), Android on the shared \`codync_worktree\` emulator, the only one that may run (never a second AVD, never \`codync_api36\`, the maintainer's), one test at a time under its lock, with \`pm clear\` and the notification grant first (docs/guides/dev-app.md#worktree-sandboxes). When done, leave this worktree's \`npm run dev\` running (it is stopped after the merge) but stop anything else you started. A change with nothing to walk (CI, tools, docs) reports one not_run check saying so.`,
{ label: `e2e:${round}`, phase: 'E2E', schema: CHECKS })
phase('E2E')
diff --git a/AGENTS.md b/AGENTS.md
index 521d268b..e549f1d8 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -36,7 +36,7 @@ Keep only the latest build: in this checkout, Apple builds go to `build/dd` only
## End-to-end test every change
-After every change, test it end to end on the real apps, not just builds and unit tests: install the new build (old one stopped first) and walk through the changed flow. Drive the desktop app with Playwright (`npm run e2e` against the sandbox) and the iPhone app (iOS Simulator) and Android app (the one shared emulator, never a second: [test devices](docs/guides/dev-app.md#worktree-sandboxes)) with one Maestro run (`apps/maestro`); Computer Use only for the native steps they can't reach: [test stack](docs/guides/test-stack.md). Report any check that could not run and why.
+After every change, test it end to end on the real apps, not just builds and unit tests: install the new build (old one stopped first) and walk through the changed flow. Drive the desktop app with Playwright (`npm run e2e` against the sandbox) and the iPhone app (iOS Simulator) and Android app (the one shared emulator, never a second: [test devices](docs/guides/dev-app.md#worktree-sandboxes)) with one Maestro run (`apps/maestro`); Computer Use (cua-driver, in the background) only for the native steps they can't reach: [test stack](docs/guides/test-stack.md). Report any check that could not run and why.
- **Minimal e2e** (default): only the platform of the computer you test on (on the Mac: macOS).
- **Full e2e** (large changes: platform code, packaging, the desktop main process; or when asked): macOS, Linux (Lima `codync-linux`) and Windows (UTM, [Windows testing](docs/guides/windows-testing.md)). A platform whose VM isn't installed is skipped and reported, not set up.
diff --git a/CLAUDE.md b/CLAUDE.md
index 86f3bcca..bf85d027 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -62,7 +62,7 @@ Keep only the latest build: in this checkout, Apple builds go to `build/dd` only
## End-to-end test every change
-After every change, test it end to end on the real apps, not just builds and unit tests: install the new build (old one stopped first) and walk through the changed flow. Drive the desktop app with Playwright (`npm run e2e` against the sandbox) and the iPhone app (iOS Simulator) and Android app (the one shared emulator, never a second: [test devices](docs/guides/dev-app.md#worktree-sandboxes)) with one Maestro run (`apps/maestro`); Computer Use only for the native steps they can't reach: [test stack](docs/guides/test-stack.md). Report any check that could not run and why.
+After every change, test it end to end on the real apps, not just builds and unit tests: install the new build (old one stopped first) and walk through the changed flow. Drive the desktop app with Playwright (`npm run e2e` against the sandbox) and the iPhone app (iOS Simulator) and Android app (the one shared emulator, never a second: [test devices](docs/guides/dev-app.md#worktree-sandboxes)) with one Maestro run (`apps/maestro`); Computer Use (cua-driver, in the background) only for the native steps they can't reach: [test stack](docs/guides/test-stack.md). Report any check that could not run and why.
- **Minimal e2e** (default): only the platform of the computer you test on (on the Mac: macOS).
- **Full e2e** (large changes: platform code, packaging, the desktop main process; or when asked): macOS, Linux (Lima `codync-linux`) and Windows (UTM, [Windows testing](docs/guides/windows-testing.md)). A platform whose VM isn't installed is skipped and reported, not set up.
- **Desktop build to use**: develop and e2e with `npm run dev` in `apps/desktop` (renderer reloads on save, restart it after `src/main` or preload changes; nothing packaged or signed). In a linked worktree it runs a [sandbox](docs/guides/dev-app.md#worktree-sandboxes) beside the main checkout's Codync Dev (own host build, port and data); `--sandbox` does the same from the main checkout when another session's Codync Dev is running. In the main checkout, after a host change run `node tools/native-host.mjs dev` there first: `npm run dev` prefers that build over `host/target/debug`. Package `npm run dist:mac:dev` (about 45 s) only for what an unpackaged run lacks: the bundled host install, Codync Screen / computer use, system permissions. `dist:*:main` (universal, timestamped, minutes) only to check the production app.
diff --git a/docs/guides/test-stack.md b/docs/guides/test-stack.md
index c4e249cd..331bb3dc 100644
--- a/docs/guides/test-stack.md
+++ b/docs/guides/test-stack.md
@@ -49,7 +49,7 @@ Two things that look like failures but aren't the app's:
## What Computer Use covers
-Computer Use (cluadex, in the background) checks only these steps. Tag them `@native` in the change's e2e list. Everything else uses Playwright or Maestro. If cluadex fails, stop and ask the user to reconnect it with `/mcp`; don't switch to cua-driver.
+Computer Use (cua-driver, in the background: never bring an app to the front) checks only these steps. Tag them `@native` in the change's e2e list. Everything else uses Playwright or Maestro. If cua-driver fails, stop and ask the user to reconnect it with `/mcp`.
- **Desktop**: the tray or menu bar icon and its menu; the approval island's global shortcut; system notification banners; macOS privacy prompts (screen recording, notifications); Clerk sign-in in the system browser and the `codync-dev://` callback back into the app; anything that needs the packaged `Codync Dev.app` (Codync Screen, computer use, `SMAppService`).
- **Phones**: how system alerts and notification banners look; the desktop QR pairing (Computer Use reads the QR on the Mac, Maestro finishes on the phone); widgets, Live Activity and the Dynamic Island.