Conductor is a token-efficient CLI for mobile UI interactions, built for AI agents. It's a TypeScript reimplementation and partial fork of Maestro that bundles its own native drivers — no external CLI, no setup friction, no nonsense.
It started as an experiment: what if Claude could tap through your app while it's writing the code? Turns out that's extremely useful. Now it's a proper tool.
Conductor gives Claude Code the ability to interact with iOS simulators and Android emulators directly from a coding session. It can navigate UI, inspect the live hierarchy, take screenshots, run flows, and manage multiple devices in parallel across concurrent agents.
conductor launch-app com.example.myapp
conductor tap-on "Sign In"
conductor input-text "user@example.com"
conductor assert-visible "Dashboard"
conductor take-screenshot --output /tmp/screen.pngOne agent writes the feature. Another taps through the app. They talk. It works. 🤝
npm install -g @houwert/conductorThat's it. Conductor is a pure CLI. To teach an AI agent how to use it, set up the bundled skills in your repo:
conductor init # interactive: pick scope + skills, writes them into .claude/skills/
conductor init --yes # non-interactive: install all skills into ./.claude/skills/
conductor init --global # install into ~/.claude/skills/ for all repos
conductor init --force # re-sync skills you've already installedinit is the one manual setup step — run it once per repo. In a terminal it walks you through which skills and where; piped or headless (CI/agent) it installs everything non-interactively. It drops a set of capability-scoped Claude Code skills — conductor-device-interact, conductor-inspect, conductor-create-flow, conductor-metro-debugger, conductor-profiler, and conductor-device-setup — that document every command and the act → observe → act workflow.
When you upgrade conductor, re-run conductor init --force to re-sync the installed skills (it stamps the installed version, so init tells you when they're out of date, and prunes any skills no longer shipped). Or wire it in however you like (a custom CLAUDE.md, a slash command — it's up to you). Run conductor --help for the full command reference, or conductor <command> --help for per-command flags.
| Capability | Commands |
|---|---|
| App lifecycle | launch-app, stop-app, clear-state, uninstall-app, install-app, foreground-app, copy-app |
| Interaction | tap-on, input-text, scroll, scroll-until-visible, swipe, press-key, erase-text, hide-keyboard |
| Inspection | inspect, focused, take-screenshot, capture-ui, list-apps |
| Assertions | assert-visible, assert-not-visible |
| Navigation | open-link, back |
| Flows | run-flow, run-flow-inline, run-parallel |
| Devices | start-device, list-devices, set-location, set-orientation |
| Web setup | install-web [browser] (installs a Playwright browser; --check prints status) |
| Discovery | list-options [command] / <command> --options (valid values for enumerated params) |
- Node.js + pnpm v9
- iOS: Xcode with command-line tools
- Android: Android SDK with
adbonPATH
make buildBuilds the iOS driver (xcodebuild), the Android driver (Gradle), packages both into the CLI, and compiles TypeScript. Then link it globally:
cd packages/cli && pnpm link --globalIf the drivers are already built and packaged:
cd packages/cli
pnpm install && pnpm buildmake build-cli # CLI TypeScript only
make build-ios-driver # iOS XCTest driver
make build-android-driver # Android instrumentation driver
make package-cli # Bundle drivers into CLI packageconductor/
├── packages/
│ ├── cli/ # TypeScript CLI (@houwert/conductor)
│ ├── android-driver/ # Kotlin/Gradle instrumentation driver
│ └── ios-driver/ # Swift/Xcode XCTest driver
└── Makefile
pnpm dev # TypeScript watch mode
pnpm lint # ESLint + Prettier check
pnpm lint:fix # Auto-fix formatting
pnpm test # Run test suite- iOS: Xcode with a booted simulator
- Android:
adbonPATHwith a running emulator or connected device
