Skip to content
Back to search

codex-mobile-dev-plugin

A Codex plugin for a better mobile development experience for android and iOS

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/callstackincubator/codex-mobile-dev-plugin with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/callstackincubator/codex-mobile-dev-plugin'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/callstackincubator--codex-mobile-dev-plugin/badge.svg)](/listings/callstackincubator--codex-mobile-dev-plugin)

HTML

<a href="/listings/callstackincubator--codex-mobile-dev-plugin"><img src="/api/listings/callstackincubator--codex-mobile-dev-plugin/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install the prebuilt plugin from the release marketplace:

codex plugin marketplace add https://github.com/callstackincubator/codex-mobile-dev-plugin.git --ref release/latest
codex plugin add mobile-dev@mobile-dev

Open a new chat after installing. The package includes the built plugin and bundled runtimes; no plugin build or `npm install` is needed. While the repository is private, installation requires GitHub read access and working Git authentication.

Mobile Dev shows a banner when a newer release is ready to install. Click **Update**, then fully quit and reopen Codex after it finishes.

You can also update an existing installation from the terminal:

codex plugin marketplace upgrade mobile-dev

Fully quit and reopen Codex after updating.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 285 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <a href="https://incubator.callstack.com/codex-mobile-dev-plugin/">
  3. <img src="https://incubator.callstack.com/codex-mobile-dev-plugin/banner.jpg" alt="Mobile Dev by Callstack. Mobile development in your ADE. Supports Codex, Claude, Cursor, and more." width="100%" />
  4. </a>
  5. </p>
  6. ## Features
  7. ### Live devices beside your chat
  8. Stream iOS simulators, Android emulators, and connected iPhones, iPads, and Android devices. Show iOS and Android together or use the fullscreen workspace.
  9. ![](/img/screenshot_side_by_side.png)
  10. ### Device control, inspection and annotations
  11. Select and boot simulators or emulators, interact with taps and drags, type on supported devices, and let your agent inspect accessibility elements and control your app through the bundled [agent-device](https://agent-device.dev/) runtime. Select an element or screen region and leave instructions for your agent, with React Native component and source details when available.
  12. ![](/img/screenshot_annotations.png)
  13. ### App control
  14. Install a built app, launch or stop it, and open a deep link or URL to jump to a screen. Send a test push notification to an iOS simulator app. Allow, deny, or reset an app permission without the system prompt, and run an app in another language than the device. The app tools in each device panel launch and stop apps, open URLs, send pushes, and set permissions and language; the agent can also call every action as an MCP tool. Mobile Dev does not build your app; your project's own tools do.
  15. ### Device settings and network conditions
  16. Change the running device's appearance, text size, rotation, location, and status bar without restarting its stream. Switch the network to LTE, 3G, Edge, or Offline to see how the app behaves on a slow or missing connection, then back to Normal. Available settings depend on the platform and device kind.
  17. ### App Flow
  18. Build a visual map of your app's screens and the navigation between them, for Expo Router and React Navigation projects. **Structure only** reads the navigation out of your source in seconds and needs no device; **Screen UI + Structure** also walks the app on an iOS simulator and photographs every screen it reaches, optionally opening each screen's sheets, modals, and dialogs. The walk runs your project's own `ios` script and reaches each screen through in-app navigation, a deep link, or a path you recorded; record one by hand on the live wireframe for a screen it cannot reach. Explore with AI lists the screens the deterministic pass missed and retries only the ones you pick. Maps, captures, and recorded paths are stored per project under `~/Library/Application Support/mobile-dev/app-flow`.
  19. ### App Intelligence
  20. Trace each Expo Router or React Navigation screen through the source files, assets, and packages it depends on, without building or running the app. Choose a project and generate its static iOS and Android graph, then browse entry points by area, fold or highlight dependency groups, and see which dependencies are platform-specific. Ask your agent what a screen depends on, which screens reach a file, or to show one screen's graph. Saved snapshots live under `~/Library/Application Support/mobile-dev/app-intelligence`; project paths and graph contents are excluded from Sentry telemetry.
  21. ### Testing Studio
  22. Record deterministic e2e tests against a booted iOS simulator or Android emulator. Choose a project with an existing e2e setup, launch the configured target, and right-click elements in the mirror to add taps, text entry, gestures, and assertions. The generated TypeScript and editable step list stay beside the app; save only when the flow is ready, then run the whole test or play to one step with per-line results. Unsaved recordings are kept in Mobile Dev and stored tests remain in the project's `tests/` folder. You can also ask your coding agent to record a flow: its steps appear live in the same panel for you to review, adjust, and save.
  23. ### Native and JavaScript logs
  24. Read iOS unified logs, Android logcat, and Metro console messages together. Follow the foreground app, search and filter logs, and send an error and its stack trace to chat.
  25. ![](/img/screenshot_logs.png)
  26. ### Live performance monitoring and improvements
  27. Track app CPU and memory, expand individual thread charts, and view device-wide Display FPS on supported devices. Ask your agent to record an interaction, inspect interactive charts in chat, compare runs, and analyze selected ranges. Android recordings include display frame pacing and jank statistics.
  28. ![](/img/screenshot_performance.png)
  29. ### Profile analysis with TraceSift
  30. Analyze a local CPU profile or a React DevTools profiling export with TraceSift. The findings appear as cards in chat, each splitting a measured task between the features it entered. Explore opens the full call tree, timeline, and flame graph in the card. Select frames or components there and ask the agent to investigate them, with the measured evidence attached. The TraceSift tool in the device panel uploads a profile and keeps the source folder an investigation should land in.
  31. ### App storage
  32. See what an app has saved without adding code to it, whether it is built with React Native or natively: UserDefaults and App Group containers, Core Data and SwiftData, SharedPreferences, DataStore, MMKV, AsyncStorage, SQLite databases, and the largest files in its data directory. Open SQLite tables as a paged grid, open any file to see JSON, property lists, and archives decoded, search across every store at once, and open the Changes tab to watch keys being added, changed, and removed while you use the app, with only the changed part of JSON values highlighted. SDK data from Firebase, Google Analytics and similar libraries is grouped separately. Clear one store or reset all app data. Works on iOS simulators and debuggable Android builds; MMKV value types are guessed from the stored bytes, and encrypted MMKV instances show as locked.
  33. Storage results are filtered before reaching the host or panel. Recognized sensitive
  34. fields and credential-like values show `[REDACTED]`; binary values are withheld.
  35. Ask for a specific store/key or table/columns to narrow inspection. This filtering
  36. cannot identify all personal or confidential data; use synthetic development data.
  37. See [storage privacy and review checks](docs/storage-privacy.md).
  38. ## Install
  39. ### Codex
  40. **[Add Mobile Dev to Codex](https://chatgpt.com/plugins/plugins_6ac4c117f76881918d3676e851fa4005)**
  41. from the plugin directory, then open a new chat.
  42. To install the prebuilt plugin from this repository instead, see
  43. [Install from the GitHub marketplace](CONTRIBUTING.md#install-from-the-github-marketplace).
  44. ### Claude Code and Claude Desktop
  45. In Claude Code, ask to see a device and Claude opens Mobile Dev's device panel in its
  46. browser beside the chat, such as the Claude desktop app's built-in browser pane. The
  47. first open downloads the panel's runtime (Baguette, Android streaming and iPhone
  48. mirroring) once from this repository's GitHub release, checked against the checksum
  49. the plugin pins. Claude reads the devices you select in the panel and anything you add
  50. to chat from it. Mobile Dev also adds device control through the bundled
  51. [agent-device](https://agent-device.dev/) runtime, native
  52. and Metro logs, app control and storage, interactive CPU, memory and FPS charts in
  53. chat, and TraceSift findings.
  54. On an Apple Silicon Mac with Node.js 22.19 or later, install the Claude Code plugin
  55. from this repository's `release/claude` branch. It finds Node on `PATH` or where
  56. Homebrew, nvm, fnm, Nix, Volta, mise or asdf install it, and Claude tells you at the start
  57. of a session when none is found:
  58. ```sh
  59. claude plugin marketplace add https://github.com/callstackincubator/mobile-dev.git#release/claude
  60. claude plugin install mobile-dev@mobile-dev
  61. ```
  62. Or in a session, `/plugin install mobile-dev --marketplace https://github.com/callstackincubator/mobile-dev.git#release/claude`.
  63. Run `claude plugin marketplace update mobile-dev` to update.
  64. For Claude Desktop chats, download `mobile-dev-<version>-claude-desktop-darwin-arm64.mcpb`
  65. from the [latest release](https://github.com/callstackincubator/mobile-dev/releases/latest),
  66. open **Settings > Extensions > Advanced settings**, and under **Extension Developer**
  67. click **Install Extension…** and select the file, or open it with Claude Desktop.
  68. Claude supplies Node for the bundle. Install a newer `.mcpb` to update. Use either
  69. the plugin or bundle, or the [local development connection](CONTRIBUTING.md#claude-desktop-local-development),
  70. to avoid duplicate Mobile Dev servers.
  71. What the Claude version runs on your Mac, besides its Node.js server:
  72. - **agent-device**, its bundled Node.js runtime, for device control. On first iOS
  73. use it builds its XCTest runner from the included source with your Xcode and
  74. caches it in `~/.agent-device/apple-runner`; it keeps session state and logs in
  75. a temporary directory.
  76. - **Native helpers** for logs and measurements: a physical iPhone log reader built
  77. on libimobiledevice, an iOS FPS and foreground-app reader, and Android CPU and
  78. FPS collectors that it copies to a connected Android device with `adb` and runs
  79. there.
  80. - **Developer tools** already on your Mac: `xcrun simctl`, `devicectl`, `adb`, and
  81. the Android emulator, and TraceSift when you analyze a profile.
  82. - **A Node.js launcher and a session check** in the Claude Code plugin, which find
  83. Node.js and start the server.
  84. It sends plugin errors and aggregate measurements to Sentry, as described under
  85. [Privacy and support](#privacy-and-support), and nothing else to Callstack;
  86. profiles go only to the TraceSift service on your Mac.
  87. ### T3 Code
  88. [T3 Code](https://github.com/pingdotgg/t3code) runs Claude Code and Codex, so it loads
  89. the Mobile Dev plugin that each of them has installed. On the Mac that runs T3 Code,
  90. install the [Claude Code plugin](#claude-code-and-claude-desktop) for Claude threads
  91. and the [Codex plugin](#codex) for Codex threads. In both, the panel opens in T3 Code's
  92. Browser.
  93. Turn off T3 Code's own device integration while you use Mobile Dev. In
  94. **Settings → Devices**, turn off **Use devices**, which also turns off **Agents can use
  95. devices**. Otherwise T3 Code gives agents its own `device_*` tools, with the same names
  96. as Mobile Dev's, and tells them to prefer those tools.
  97. Codex threads need one setting, because T3 Code renders Codex's panel in the chat
  98. and asks you to confirm each action that the panel takes, such as each tap:
  99. 1. Open **Settings → Providers**, then the Codex instance.
  100. 2. Under **Variables**, click **Add variable**. Set `MOBILE_DEV_PANEL` to `browser`.
  101. 3. Start a new thread.
  102. Ask the agent to open Mobile Dev. It opens the panel with T3 Code's `preview_open`
  103. tool, and T3 Code shows the page as a floating preview. To dock the panel beside the
  104. chat, click the preview's **Open in right panel** button. The agent reads the devices
  105. you select in the panel and the screenshots and screen notes you add from it.
  106. Performance recordings still render as cards in the chat.
  107. ### Cursor: manual installation
  108. On an Apple Silicon Mac with Node.js 22.19 or later on `PATH`, obtain the
  109. `mobile-dev` Cursor plugin folder from the person sharing the preview, or
  110. [build one locally](CONTRIBUTING.md#cursor-local-development). The Cursor plugin is
  111. not yet published to the Cursor Marketplace.
  112. 1. Copy the `mobile-dev` folder to `~/.cursor/plugins/local/mobile-dev`.
  113. 2. Run **Developer: Reload Window**, or restart Cursor, and confirm Mobile Dev
  114. appears under **Customize**.
  115. 3. Start a new agent chat and ask **"Open Mobile Dev."** Approve the tool calls
  116. when prompted.
  117. Cursor renders the Mobile Dev views where MCP Apps are available. Otherwise tools
  118. return text, and the agent asks you to choose devices in chat. Copy a newer folder
  119. and reload to update. Use either the plugin or the [local development connection](CONTRIBUTING.md#cursor-local-development)
  120. to avoid duplicate Mobile Dev servers. See [Cursor's plugin guide](https://cursor.com/docs/plugins).
  121. ### Mac app
  122. The Mac app shows the devices and tools in their own window, without a chat. Pick
  123. a tool and the visible platforms in the sidebar. It runs the same server as the
  124. plugins, so the device panels, logs, performance, storage, and TraceSift work the
  125. same way. Chat actions such as Send to chat and annotations are hidden because
  126. there is no chat to send to.
  127. There is no download yet. Build it from a checkout on an Apple Silicon Mac with
  128. Xcode 27, following [the Mac app guide](CONTRIBUTING.md#mac-app):
  129. ```sh
  130. npm ci
  131. npm run build
  132. npm run build:mac
  133. open "release/mac/Mobile Dev.app"
  134. ```
  135. ## Requirements
  136. Mobile Dev runs on an Apple Silicon Mac. In Codex desktop, the prebuilt plugin
  137. uses Codex's bundled Node runtime from its workspace dependency cache; the Claude
  138. Desktop bundle uses Claude's Node runtime, the Cursor plugin uses Node.js from
  139. `PATH`, and the Mac app bundles its own. Install the tools for the platforms you use:
  140. | Platform or feature | Requirements |
  141. | --- | --- |
  142. | iOS simulators | Xcode 26 or later with an installed simulator runtime. |
  143. | Physical iPhones and iPads | Xcode 27 or later, a paired device with Developer Mode enabled, and USB or Wi-Fi connectivity. Screen mirroring requires HEVC WebCodecs support in the host. |
  144. | Android | Android SDK platform-tools and emulator, and an AVD or a physical device with authorized USB or wireless debugging. Screen streaming requires H.264 WebCodecs support in the host. |
  145. | Metro logs and React Native inspection | An existing local Metro server with a compatible app inspector target. |
  146. | Physical iOS CPU and memory | iOS 17.4 or later, a running development-signed app with `get-task-allow`, a mounted developer disk image, and Xcode/LLDB detached. |
  147. | Display FPS | Android 12 or later with FrameTimeline support, or a physical iOS device running iOS 17.4 or later. iOS simulators do not support Display FPS. |
  148. | Testing Studio | A booted iOS simulator or Android emulator, plus an existing e2e project with its dependencies installed and a target bundle ID in `e2e.config.*`. |
  149. | Profile analysis | A local TraceSift installation, found on `PATH` or through `TRACE_SIFT_COMMAND`. |
  150. Simulator tools use the full Xcode installation selected by `xcode-select` (or
  151. `DEVELOPER_DIR`), including its Swift compatibility libraries. Custom Xcode names
  152. and locations are supported. If Command Line Tools or an older Xcode is selected,
  153. choose Xcode 26 or later in Xcode Settings > Locations > Command Line Tools.
  154. The app project's own tools build, install, and launch your app. Mobile Dev supplies
  155. its device panel, inspection, logs, and performance tools.
  156. ## Get started
  157. Ask your agent to open the simulator beside this chat. In Codex, you can also
  158. open Mobile Dev from the sidebar; in Cursor, ask **"Open Mobile Dev"** in an agent chat.
  159. Pick a device from the toolbar; selecting a stopped simulator or AVD
  160. boots it. Use the iOS and Android toggles to show either platform or both.
  161. Click an iOS simulator or Android screen to focus it, then press **Command-V** to
  162. paste text into the device. Paste accepts up to 4,096 printable US-ASCII characters;
  163. line breaks and other characters show a notice without sending partial text.
  164. Ask your agent to work with your app, for example:
  165. - “Build and run my Expo app in the simulator beside this chat.”
  166. - “Read the app logs and help me fix this error.”
  167. - “Record CPU and memory for 30 seconds while I scroll checkout.”
  168. - “Compare these two performance recordings.”
  169. - “Show me the App Intelligence for this project.”
  170. - “Record an e2e test for the checkout flow.”
  171. Open **Tools** and choose **App Intel**, Testing, Logs, Performance, Storage, or TraceSift. App Intelligence, shown as **App Intel** in the Tools menu, is available in Mobile Dev 0.1.183 and later and analyzes a project without a device. If **App Intel** is missing, update Mobile Dev, fully quit and reopen your host, then start a new conversation. Testing records against a simulator or emulator; the other device tools inspect the selected device. Use Screenshot to attach
  172. an image to your next message, or Select to annotate an element or region with an
  173. instruction. Physical iOS supports taps and drags; keyboard and hardware-button
  174. controls are unavailable.
  175. ## Documentation and contributing
  176. Detailed guides are available for
  177. [devices](https://github.com/callstackincubator/mobile-dev/blob/main/docs/devices.md),
  178. [logs](https://github.com/callstackincubator/mobile-dev/blob/main/docs/logs.md),
  179. [performance](https://github.com/callstackincubator/mobile-dev/blob/main/docs/performance.md),
  180. [App Intelligence](https://incubator.callstack.com/codex-mobile-dev-plugin/docs/app-intelligence),
  181. [Testing](https://incubator.callstack.com/codex-mobile-dev-plugin/docs/testing),
  182. and [MCP tools](https://github.com/callstackincubator/mobile-dev/blob/main/docs/mcp-tools.md).
  183. [Architecture](https://github.com/callstackincubator/mobile-dev/blob/main/docs/architecture.md) explains how the hosts share the server
  184. and panel.
  185. The repository is an npm workspace. Shared code lives in `packages/`, and each
  186. product in `apps/`:
  187. | Path | Contents |
  188. | --- | --- |
  189. | `packages/core` | The MCP server, device runtimes, and tool handlers |
  190. | `packages/ui` | The device panels and tools every host shows |
  191. | `packages/mcp-app` | The MCP Apps panel that Codex and Claude Desktop load |
  192. | `packages/shared` | Types and logic the server and UI both use |
  193. | `packages/skills` | Agent skills for the shared tools |
  194. | `packages/native`, `packages/runtimes` | Native helpers and bundled Node runtimes |
  195. | `apps/codex-plugin` | The Codex plugin: manifest, updater, and update banner |
  196. | `apps/claude` | Claude: its server, which downloads the panel's runtime, skill, and the Claude Desktop extension and Claude Code plugin manifests |
  197. | `apps/cursor` | Cursor: the Cursor plugin manifest |
  198. | `apps/mac` | The Mac app: SwiftUI window and its page |
  199. To build a host, install a local package, or contribute changes, see
  200. [CONTRIBUTING.md](https://github.com/callstackincubator/mobile-dev/blob/main/CONTRIBUTING.md).
  201. Implementation and release details live in the linked contributor documentation.
  202. ## Privacy and support
  203. Mobile Dev reports plugin errors, crashes, usage counters, sampled traces, and
  204. aggregate plugin performance measurements to Sentry by default. App logs,
  205. screenshots, input content, tool payloads, app storage contents, profiles, and
  206. device performance recordings are excluded from that telemetry. Errors and
  207. crashes use a randomly generated persistent installation ID. Set
  208. `MOBILE_DEV_TELEMETRY=off` in the MCP launch environment and restart the plugin
  209. processes to disable reporting. For the Mac app, start it with
  210. `open --env MOBILE_DEV_TELEMETRY=off "Mobile Dev.app"`. Tool results and content sent to chat are handled
  211. by the host separately. Read the [Privacy Policy](PRIVACY.md) and
  212. [Terms of Service](TERMS.md), or see
  213. [Sentry observability](https://github.com/callstackincubator/mobile-dev/blob/main/docs/telemetry.md)
  214. for implementation details.
  215. For help, email [hello@callstack.com](mailto:hello@callstack.com).
  216. See [Support](SUPPORT.md) for reporting bugs, security issues, and privacy requests.
  217. ## License
  218. Mobile Dev is available under the [MIT License](LICENSE). Bundled third-party
  219. components keep their own licenses; see [Third-party notices](THIRD_PARTY_NOTICES.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.