Run Dev

---
name: run-dev
description: Start the Codevisor development server and build/run the native macOS or iOS app for local testing. Use when asked to run, launch, or test the dev app, dev server, or iOS simulator app.
---

# Run Codevisor

From the worktree root, use exactly one of:

```sh
bun run dev
bun run dev:macos
bun run dev:ios
```

The runners install locked dependencies, resolve GhosttyKit when needed, and keep build/runtime state under the worktree's ignored `tmp/`. Do not run `bun install`, `xcodebuild`, the server, or Ghostty build scripts separately.

`dev:ios` uses the visible `iPhone 17 Pro` simulator by default. Set `CODEVISOR_IOS_SIMULATOR=<device name>` to select another available simulator. Its development bundle identifier is derived from the worktree path, so installing or stopping it cannot replace another worktree's simulator app.

`dev` builds and launches both native apps against one shared set of local, remote, and cloud development services — the default for day-to-day work and cross-device synchronization testing. It accepts the same `CODEVISOR_IOS_SIMULATOR` override as `dev:ios`. All three native runners start Dev Direct and Dev Cloud as Linux containers by default (Apple `container` preferred, Docker fallback) so sync and authentication are tested across real separate machines. Each accepts `--containers`, `--no-containers`, and `--container-engine=apple|docker|none`; `--no-containers` and `--container-engine=none` run the remotes as same-host processes, which is also the automatic fallback when no engine is available. `dev:macos` builds only the macOS app; `dev:ios` builds only the iOS app.

Keep at most one runner active per worktree. Track and stop the parent process you started before rebuilding. Never stop or modify another worktree's instance; if this worktree already has an instance you do not own, reuse it or report that it is running.

For website-only development, use `bun run dev:web`.