Wire Expo projects into the Codex app with project-local run scripts and .codex/environments/environment.toml actions. Use when the user wants the Codex app Run button, build/run actions, action buttons, or a stable Expo start/run workflow from Codex.
Use this skill to connect an Expo project to the Codex app action bar.
The goal is one project-local script plus .codex/environments/environment.toml,
so the user can press Run in the Codex app and see the Expo CLI / Metro logs in
an action terminal.
Confirm the current workspace is an Expo app.
package.json.app.json, app.config.js, app.config.ts, or expo in package.json.Discover the package runner.
packageManager.npx expo.Create or update .
script/build_and_run.shexpo start.--ios starts Expo and opens iOS simulator.--android starts Expo and opens Android.--web starts Expo for web.--dev-client starts in dev-client mode.--tunnel starts a tunnel.--export-web exports web.Write .codex/environments/environment.toml.
Run.Run to ./script/build_and_run.sh.Run iOS, Run Android, Run Web, or Run Dev Client
actions only when the user asks for those buttons or the project clearly needs them.Use the action script as the default local run path.
./script/build_and_run.sh --help or a short non-server mode if you need to sanity-check syntax.references/expo-run-button-bootstrap.md: canonical Expo script/build_and_run.sh and Codex environment action examples.expo start first; do not default the Codex Run button to expo run:ios, expo run:android, prebuild, or EAS Build.eas build, eas submit, or store deployment into Codex buttons unless the user explicitly asks and accepts the auth / time / cost tradeoff..codex/environments/environment.toml or in the run script.When setup changes are made, summarize: