setup-codex-run-actions — Claude command: Expo run buttons
Wires the current Expo project into the Claude action bar with a Run button, plus iOS, Android or web buttons when you ask for them.
~/.codex/prompts/setup-codex-run-actions.mdWhat setup-codex-run-actions does
The command hooks an Expo app into the Claude action bar. It first confirms the target root really is an Expo app, then creates or updates script/build_and_run.sh and .codex/environments/environment.toml.
One primary Run action always points at ./script/build_and_run.sh. Extra actions such as ios, android, web, dev-client, doctor or export-web are added only when you list them comma-separated in the actions argument. Pass root if the app does not sit in the current directory.
Setup does not start the dev server. That happens only with run=true or when you ask for it directly. At the end the command validates with bash -n ./script/build_and_run.sh and ./script/build_and_run.sh --help, then reports the script path, environment file path, action names and validation results. Point it at a non-Expo folder and the check stops you early, which is worth knowing before you run it on a monorepo root.
What it helps with
- add a run button for an Expo app to the Claude action bar
- set up iOS, Android and web buttons in one pass
- generate
script/build_and_run.shto build and launch the project - write the Claude environment file at
.codex/environments/environment.toml - syntax-check the run script before using it
Example prompts for the agent
- /setup-codex-run-actions
- /setup-codex-run-actions actions=ios,android,web
- /setup-codex-run-actions root=apps/mobile run=true
How to install setup-codex-run-actions
Manually: put the files in place
~/.codex/prompts/setup-codex-run-actions.mdCall it with /prompts:setup-codex-run-actions. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.claude/commands/setup-codex-run-actions.mdCall it with /setup-codex-run-actions. For all projects use ~/.claude/commands/
Manually: put the files in place
.github/prompts/setup-codex-run-actions.prompt.mdManually: put the files in place
.gemini/commands/setup-codex-run-actions.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about setup-codex-run-actions
How do I install setup-codex-run-actions in Claude?
Copy the command file to ~/.codex/prompts/setup-codex-run-actions.md.
What does setup-codex-run-actions do?
It wires the current Expo project into the Claude action bar by creating a build-and-run script, an environment file and a Run action.
Does the Expo dev server start right after setup?
No. It starts only with run=true or when you explicitly ask for it.
Source text
setup-codex-run-actions.md · MIT
# /setup-codex-run-actions Wire the current Expo project into the Codex app action bar. ## Arguments - `root`: Expo app root, if not the current directory (optional) - `actions`: comma-separated extra buttons such as `ios,android,web,dev-client,doctor,export-web` (optional) - `run`: whether to start the Expo dev server after setup (optional, default: false) ## Workflow 1. Use the `codex-expo-run-actions` skill. 2. Confirm the target root is an Expo app before editing. 3. Create or update `script/build_and_run.sh` using the skill reference. 4. Create or update `.codex/environments/environment.toml`. 5. Always wire one primary `Run` action to `./script/build_and_run.sh`. 6. Add optional actions only when requested. 7. Validate with `bash -n ./script/build_and_run.sh` and `./script/build_and_run.sh --help`. 8. Start the dev server only when `run=true` or the user explicitly asks. ## Output Report the script path, environment file path, action names, and validation command results.
© Expo Team · MIT · openai/plugins
