DEDUPED Hot AI repos, turned into use cases Get 5 a day

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

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

Who it is forA 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 problemEach simulator can take several GB, and Metro servers fight over the same port when several branches run together.

The outcomeEach 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.

What you need first

  • A Mac running macOS
  • Bun 1.1 or newer (https://bun.sh)
  • Xcode for iOS work, plus `brew install mobai-app/tap/simslim baguette watchman`
  • Android SDK with platform-tools and emulator for Android work, plus `brew tap kdbhalala/avdslim https://github.com/kdbhalala/avdslim.git && brew install avdslim scrcpy`
  • A React Native or Expo app with a Git repository

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 for your agent

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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page