codex-expo-run-actions

Wire Expo projects into the Codex app Run button with project-local scripts and environment actions.

5.3k|765|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/openai/plugins --skill codex-expo-run-actions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-expo-run-actions
Source: https://github.com/openai/plugins/tree/main/plugins/expo/skills/codex-expo-run-actions
Command: npx skills add https://github.com/openai/plugins --skill codex-expo-run-actions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Expo developers using the Codex app lack a consistent way to launch their dev server from the action bar, often ending up with ad-hoc commands, wrong package managers, or backgrounded Metro processes that hide logs.

Core Features & Use Cases

  • Project-local run script: Generates script/build_and_run.sh with modes for start, iOS, Android, web, dev-client, tunnel, export-web, and doctor, auto-detecting pnpm, yarn, bun, or npm.
  • Codex environment wiring: Creates or updates .codex/environments/environment.toml with a primary Run action and optional platform-specific buttons.
  • Safe defaults: Keeps the Metro dev server in the foreground so the Codex action terminal owns logs, and avoids wiring cloud builds like EAS unless explicitly requested.
  • Use Case: You open an Expo app in Codex and want a Run button that starts expo start with visible logs; this skill creates the script and environment file so one click launches the dev server.

Quick Start

Use the codex-expo-run-actions skill to wire this Expo project into the Codex app with a Run button and a project-local build_and_run.sh script.

Frequently Asked Questions about codex-expo-run-actions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a Run button for an Expo app in the Codex app?

Create a project-local script/build_and_run.sh that runs expo start in the foreground, then add a Run action in .codex/environments/environment.toml pointing to that script. The Codex app action bar will show the button and stream Metro logs in its terminal.

How do I wire Expo run actions for iOS, Android, and web?

Add optional actions in environment.toml such as Run iOS, Run Android, and Run Web, each calling build_and_run.sh with --ios, --android, or --web flags. Keep the primary Run action even when adding platform-specific buttons.

Does the Expo run script work with pnpm, yarn, or bun?

Yes, the generated script detects the package manager from lockfiles like pnpm-lock.yaml, yarn.lock, or bun.lock and uses pnpm exec, yarn, or bunx accordingly. It falls back to npx expo when no lockfile match is found.

Should the Codex Run button use EAS Build or expo run:ios?

No, the default Run action should use expo start with Expo Go because EAS Build is remote, authenticated, and slow, while expo run:ios may require native project state. Only wire cloud or native builds when the user explicitly accepts the tradeoffs.

Why are Metro logs missing when running Expo from an action?

Logs go missing when the dev server is backgrounded instead of running in the foreground. The run script must exec expo start directly so the Codex action terminal owns the process and displays the Expo CLI output.