Simfleet

simfleet

  One control plane for parallel React Native work on macOS.
  Slimmed iOS simulators and Android emulators, a live browser dashboard, leased Metro ports,
  a shared native build cache, and per-agent device attribution for Claude Code and Codex.

  Documentation ·
  Quickstart ·
  API reference

https://github.com/user-attachments/assets/96422e28-f5a8-400b-b8d9-9a2530fa1eda

Running several branches of a React Native app at once usually means five simulators eating 4 GB each,
Metro servers fighting over port 8081, native rebuilds every time you switch environments, and coding
agents stepping on each other's devices. simfleet turns that into one managed fleet:

- Always slim. Every iOS simulator is trimmed with SimSlim
  (about 3.8 GB → 1.3 GB) and every Android emulator with
  avdslim (-lowram, host GPU, ~45 background packages
  disabled). Devices booted any other way (Xcode, Android Studio, simctl) are slimmed automatically.
- One live dashboard. Every booted device streams into a browser wall you can drive directly: iOS
  over MJPEG, Android as hardware H.264 through scrcpy's device
  server with real touch down/move/up (15–80 ms input-to-frame on an M-series Mac).
- Lanes, not port juggling. A lane is one worktree on one device with one leased Metro port from the
  environment's range. Lanes refuse to steal a device, worktree, or port.
- Native builds once. An Expo buildCacheProvider fingerprints native inputs (JS excluded) and
  single-flights misses, so ten agents on JS-only branches share one build, and switching
  staging/production never rebuilds native.
- Know which agent is where. Every CLI call from a Claude Code or Codex session is attributed to the
  device it touches; sessions can claim devices. A menu-bar icon shows who is driving…