Codex Build iOS Apps Plugin: Mirror the Simulator in the Browser and Hot-Reload SwiftUI Previews
OpenAI's Build iOS Apps plugin lets Codex mirror the iOS Simulator in the in-app browser and hot-reload package-backed SwiftUI previews without leaving Codex. It packages Swift and iOS workflows -- designing App Intents and Shortcuts, building and refactoring SwiftUI, auditing performance, and debugging on simulators through XcodeBuildMCP-backed flows. The plugin is open source in OpenAI's plugins repo.
OpenAI shipped a Build iOS Apps plugin for Codex, highlighted by OpenAIDevs on June 4, 2026. The headline claim from the announcement: the plugin lets Codex view and test your iOS app in the in-app browser, open SwiftUI previews, and hot reload edits without leaving Codex. The plugin is open source in OpenAI's plugins repository, and OpenAI's developer docs include matching iOS use-case guides.
For context on how Codex keeps adding surfaces, see our writeup of the Codex Chrome extension and Codex computer use and thread automations. For where Codex sits against other agentic coding tools, see Codex CLI vs Claude Code vs Cursor architecture.
Key Takeaways
- Headline feature: mirror the iOS Simulator in Codex's in-app browser and hot-reload package-backed SwiftUI previews -- no trip back to Xcode to see edits.
- Open source. The plugin lives at
github.com/openai/pluginsunderplugins/build-ios-apps. - XcodeBuildMCP-backed. Simulator build, run, and debug flow through XcodeBuildMCP, keeping the loop CLI-first.
- Broader than previews. It also covers App Intents and Shortcuts design, SwiftUI building and refactoring, performance auditing, ETTrace profiling, and memgraph leak diagnosis.
- Discovery source: the OpenAIDevs announcement on June 4, 2026; capabilities verified against the plugin README and Codex iOS use-case docs.
What the Plugin Does
The Build iOS Apps plugin packages Swift and iOS workflows for Codex. Per the plugin README, its capabilities include:
- Designing App Intents, app entities, and App Shortcuts for system surfaces.
- Building and refactoring SwiftUI UI using current platform patterns.
- Auditing SwiftUI performance and guiding profiling workflows.
- Mirroring Simulator in the browser and hot-reloading package-backed SwiftUI previews.
- Debugging iOS apps on simulators with XcodeBuildMCP-backed flows.
- Capturing symbolicated ETTrace simulator profiles for focused app flows.
- Capturing and comparing iOS memgraphs to root-cause leaks.
The announcement frames the day-to-day value plainly: you view and test the app in the in-app browser, open SwiftUI previews, and hot reload edits, all without leaving Codex.
The In-App Browser Preview Loop
The differentiator is the feedback loop. Traditional SwiftUI iteration means editing code, rebuilding in Xcode, and relaunching the app or canvas preview to see the change. The plugin collapses that: it mirrors the Simulator inside Codex's in-app browser and hot-reloads package-backed SwiftUI previews, so an edit shows up live in the same window where you are working with the agent.
That matters because it keeps the human in one surface. Codex already has an in-app browser for local dev servers and file-backed previews; pointing that browser at a mirrored Simulator with live reload extends the same pattern to native iOS UI work.
How It Fits With XcodeBuildMCP
The plugin is not a black box around the simulator -- it leans on XcodeBuildMCP. Per the Codex iOS use-case docs, XcodeBuildMCP lets Codex list schemes and targets, launch the app, capture screenshots, and keep iterating without leaving the agentic loop. The docs emphasize keeping the build loop CLI-first with xcodebuild (or Tuist) rather than driving the Xcode GUI.
So the division of labor is: XcodeBuildMCP handles the build/run/inspect mechanics against the simulator, and the plugin layers iOS-specific workflows (SwiftUI patterns, App Intents, profiling) plus the in-browser mirrored preview on top.
How a Reader Uses This
Pattern 1: Tight SwiftUI UI Iteration
You are building a SwiftUI screen and want fast visual feedback. With the plugin, Codex mirrors the Simulator in the in-app browser and hot-reloads package-backed previews, so you describe the change, Codex edits, and the preview updates live -- without switching to Xcode.
Pattern 2: Adding System Integration
You want your app to expose actions to Shortcuts and Spotlight. The plugin's App Intents workflow guides Codex through designing app intents, entities, and App Shortcuts for those system surfaces, then wiring them in.
Pattern 3: Performance and Leak Triage
An app flow feels slow or is leaking memory. The plugin can capture symbolicated ETTrace simulator profiles for a focused flow and capture/compare iOS memgraphs to root-cause leaks -- giving Codex concrete signals to reason about instead of guessing.
Caveats and Open Questions
- Claims sourced to official material. The headline feature wording comes from the OpenAIDevs announcement; the detailed capability list comes from the open-source plugin README and the Codex iOS use-case docs. We have not asserted availability tiers, pricing, GA/beta status, or a plugin-catalog count, because the official sources reviewed do not state them.
- Requires the Codex iOS toolchain. The simulator-backed flows depend on XcodeBuildMCP and a working local Xcode/simulator setup; the plugin orchestrates that toolchain rather than replacing it.
- Open source means it can change. Because the plugin lives in a public repo, its exact capability set can evolve -- check the README in
github.com/openai/pluginsfor the current state.
FAQ
See the structured FAQ in the schema header for question-level details: what the plugin does, how the in-app browser preview works, open-source location, XcodeBuildMCP usage, and capabilities beyond previews.
Sources
- OpenAIDevs announcement (X): https://x.com/OpenAIDevs/status/2062599291479478275 (June 4, 2026)
- Build iOS Apps plugin (open source): https://github.com/openai/plugins/tree/main/plugins/build-ios-apps
- Codex iOS use-case docs: https://developers.openai.com/codex/use-cases/native-ios-apps
Read next
Keep building the workspace playbookCodex Chrome Extension: How Codex Drives a Signed-In Browser for LinkedIn, Salesforce, Gmail, and Internal Tools
OpenAI's Codex Chrome extension lets the agent use Chrome for browser tasks that need signed-in state -- LinkedIn, Salesforce, Gmail, internal tools. Available in the Codex app in all regions except EU and UK at launch. Setup is Codex > Plugins > add Chrome > install extension > approve permissions. Invoke with @Chrome. By default Codex asks before each new website; allowlist/blocklist and elevated-risk options live in Computer Use settings.
OpenAI Codex Goes 'For Almost Everything': Mac Computer Use, Browser Comment Mode, and Thread Automations Explained
OpenAI shipped a major Codex update on April 16, 2026 that pushes the product past coding into general work. Three changes matter: Codex can now drive your Mac apps directly, an in-app browser captures both screenshots and DOM elements through 'comment mode', and Codex threads can run continuously to watch Slack, email, and PRs. Here is how each works, the workflows that justify each one, and where Codex now sits relative to Perplexity Personal Computer and Claude Code Routines.
Codex CLI vs Claude Code vs Cursor: 2026 Architecture Deep-Dive (Sandboxing, Context, Plugins, Scheduling)
Codex CLI, Claude Code, and Cursor all reach for the same outcome -- an AI agent that ships code -- with three different architectures. Codex enforces safety at the OS kernel layer. Claude Code uses application-layer hooks for programmable governance. Cursor builds the agent into a visual IDE with a marketplace of plugins. The right one depends less on which model you prefer and more on which architecture matches your security posture, your composition needs, and your team shape.
Frequently Asked Questions
What does the Codex Build iOS Apps plugin do?
It packages Swift and iOS workflows for Codex. Per the official OpenAIDevs post, it lets Codex view and test your iOS app in the in-app browser, open SwiftUI previews, and hot reload edits without leaving Codex. The plugin README also covers App Intents design, SwiftUI building and refactoring, performance auditing, and simulator debugging.
How does the in-app browser preview work?
The plugin README describes mirroring the Simulator in the browser and hot-reloading package-backed SwiftUI previews. That means you can see the running app inside Codex's in-app browser and have edits reflected live, rather than switching to Xcode to rebuild and relaunch.
Is the Build iOS Apps plugin open source?
Yes. The plugin lives in OpenAI's public plugins repository at github.com/openai/plugins under plugins/build-ios-apps. The README documents its capabilities, and the Codex docs include iOS use-case guides for scaffolding and building SwiftUI apps.
Does the plugin use XcodeBuildMCP?
Yes. The README states it debugs iOS apps on simulators with XcodeBuildMCP-backed flows. The Codex iOS use-case docs describe XcodeBuildMCP as the integration that lets Codex list schemes and targets, launch the app, and capture screenshots while iterating, keeping the build loop CLI-first.
What else can the plugin do beyond previews?
Per the README: designing App Intents, app entities, and App Shortcuts for system surfaces; building and refactoring SwiftUI using current platform patterns; auditing SwiftUI performance and guiding profiling; capturing symbolicated ETTrace simulator profiles; and capturing and comparing iOS memgraphs to root-cause leaks.