# AI use cases for Simfleet (entropyconquers/simfleet)

Repo: [entropyconquers/simfleet](https://github.com/entropyconquers/simfleet) | Use cases: 4 | Page: https://dedupedai.com/use-cases/entropyconquers-simfleet/

simfleet is a macOS control plane that runs and tracks parallel React Native work across iOS simulators, Android emulators, Metro ports, and native builds, with a live dashboard and agent device attribution.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Run several app branches side by side without port clashes: https://dedupedai.com/use-cases/entropyconquers-simfleet/run-parallel-branch-lanes/
- Share one native build across agents on JS-only branches: https://dedupedai.com/use-cases/entropyconquers-simfleet/share-native-builds-across-agents/
- See which coding agent is using which simulator: https://dedupedai.com/use-cases/entropyconquers-simfleet/attribute-agent-device-use/
- Test a running app by driving devices in the browser: https://dedupedai.com/use-cases/entropyconquers-simfleet/drive-devices-from-live-dashboard/

## How to run several app branches side by side without port clashes with Simfleet

Repo: [entropyconquers/simfleet](https://github.com/entropyconquers/simfleet) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README

Give each branch its own slim device, worktree, and leased Metro port from one dashboard.

**Who it is for:** A React Native developer who needs to test three or four feature branches at the same time and is losing time to simulators and Metro port 8081 conflicts.

**The problem:** Each simulator can take several GB, and Metro servers fight over the same port when several branches run together.

**The outcome:** Each branch runs as a lane on its own device and its own leased Metro port, and the dashboard shows every device with its state and memory footprint.

### Steps

1. `bun add -g simfleet`
2. `cd path/to/your-app`
3. `simfleet init`
4. `simfleet serve`
5. `simfleet sim boot`
6. `simfleet lane start "$PWD" development debug` (inferred, check the README)
7. `simfleet lane launch`

### Prompt to paste into your agent

```text
Using the simfleet repo (entropyconquers/simfleet), run `simfleet lane start "$PWD" development debug` inside <path-to-app> and then `simfleet lane launch`. Expected output: a lane with a leased Metro port and the dev client opened on that port. Verify with `simfleet ports` that the leased port appears in the list.
```

### Caveat

Simfleet trusts the local machine: its API binds to 127.0.0.1 with no authentication, and it needs the Xcode and Android tooling installed before any device can boot.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/entropyconquers-simfleet/run-parallel-branch-lanes/

## How to share one native build across agents on JS-only branches with Simfleet

Repo: [entropyconquers/simfleet](https://github.com/entropyconquers/simfleet) | Difficulty: Advanced | Time: 1 hour 30 minutes | Basis: From the README

Cache native builds by fingerprint so many agents reuse one build and environment switches skip native rebuilds.

**Who it is for:** A team lead or platform engineer whose coding agents run many JS-only branches and keep triggering slow native rebuilds.

**The problem:** Every branch or environment switch can force a fresh native build, which wastes time and machine resources when only JavaScript changed.

**The outcome:** Native inputs are fingerprinted with JavaScript excluded, so agents on JS-only branches share one build, and switching staging and production does not rebuild native code.

### Steps

1. `bun add -d simfleet`
2. Add `buildCacheProvider: { plugin: require.resolve("simfleet/build-cache") }` under `experiments` in `app.config.js` (inferred from the README snippet).
3. `simfleet native plan`
4. `simfleet native ensure` (inferred, check the README)

### Prompt to paste into your agent

```text
Using the simfleet repo (entropyconquers/simfleet), set up the Expo build cache in <path-to-app> and run `simfleet native plan` to inspect the fingerprint. Expected output: a plan that lists the native inputs and whether a cached build exists. Verify that changing only a JavaScript file leaves the native fingerprint unchanged.
```

### Caveat

Only `projectName`, `nativeAuth`, and `nativeShells` feed the native fingerprint, so native changes outside those settings may not be detected as expected.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/entropyconquers-simfleet/share-native-builds-across-agents/

## How to see which coding agent is using which simulator with Simfleet

Repo: [entropyconquers/simfleet](https://github.com/entropyconquers/simfleet) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

Track Claude Code and Codex device calls per session and claim devices so agents stop colliding.

**Who it is for:** A developer running Claude Code or Codex sessions in parallel who needs to know which agent touched which simulator or emulator.

**The problem:** Coding agents stepping on each other's devices is hard to notice and hard to trace back to a session.

**The outcome:** The dashboard and CLI show which session touched which device, and a session can hold a device so other agents leave it alone.

### Steps

1. `bun add -g simfleet`
2. `simfleet skill install`
3. `simfleet serve`
4. `simfleet agents` (inferred, check the README)
5. `simfleet claim <device-id> "<note>"` (inferred, check the README)

### Prompt to paste into your agent

```text
Using the simfleet repo (entropyconquers/simfleet), run `simfleet agents` from inside a Claude Code or Codex session in <path-to-app>. Expected output: the live agent sessions and the devices they have touched. Verify that after `simfleet claim <device-id>` the device is listed as held by this session.
```

### Caveat

Attribution only reads the session IDs that Claude Code and Codex expose, and touches expire after 30 minutes, so an idle session will drop off the list.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/entropyconquers-simfleet/attribute-agent-device-use/

## How to test a running app by driving devices in the browser with Simfleet

Repo: [entropyconquers/simfleet](https://github.com/entropyconquers/simfleet) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README

Tap, swipe, and type on live iOS and Android screens from one browser wall.

**Who it is for:** A mobile developer or QA tester who wants to watch and control several simulators and emulators from one screen while checking a build.

**The problem:** Switching between device windows and recording what each one shows makes multi-device checks slow to set up and easy to lose track of.

**The outcome:** Every booted device streams into one browser view where the tester can click to tap, drag to swipe, and type, with lifecycle and deep-link controls in the inspector.

### Steps

1. `simfleet serve`
2. Open http://127.0.0.1:8790 in a browser.
3. `simfleet sim boot`
4. `simfleet emu boot Pixel_8_API_35`
5. Click a device on the wall, then click to tap or drag to swipe.

### Prompt to paste into your agent

```text
Using the simfleet repo (entropyconquers/simfleet), start `simfleet serve` in <path-to-app>, then open the dashboard at http://127.0.0.1:8790. Expected output: each booted simulator and emulator shown on the wall with its state. Verify that a tap sent from the dashboard changes the screen on the target device.
```

### Caveat

The dashboard and API have no authentication and are reachable only on the local machine, so anyone with access to your user account can drive your devices.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/entropyconquers-simfleet/drive-devices-from-live-dashboard/