Ciying AI Directory
AI DirectorySkills
中文
Ciying AI Directory

Codex Run Actions for Expo: Start Metro from the Run Button

Connect a local Expo project to the Codex desktop Run action. Use the project’s package manager to launch Metro in the action terminal so you can see logs and stop it from the same place.

中文

Setup for Codex (desktop app)

Codex desktop with a runnable Expo project, its existing Node.js dependencies, and a shell that can execute the provided Bash script. The example needs only the local Metro server.

  1. Open the Expo plugin in the Codex plugin picker. For the exact version reviewed here, copy the pinned codex-expo-run-actions directory into the project’s .agents/skills directory, including references.
  2. Open the Expo app’s own directory in Codex. In a monorepo, select the package containing the Expo app configuration and dependencies.
  3. Invoke $codex-expo-run-actions and have it create or update script/build_and_run.sh and .codex/environments/environment.toml. Review the generated command, then open the Run action.

Example task

Use $codex-expo-run-actions in a scratch Expo app that already starts from the terminal. Wire one Run action that starts the existing Expo development server and shows Metro output. Keep the process attached to the action terminal. Stop after demonstrating that Stop ends the server. Skip simulators and builds for this test.

Expected result

The Run action starts the project’s Expo command and Metro logs become visible in the action terminal. Stop terminates the foreground process. No simulator or build should run in this basic example.

Upstream documentation

Original SKILL.md on GitHub · MIT license · Source reviewed

Frequently asked question

Where should Expo run configuration live in a monorepo?

Point the action at the Expo app package that owns the app configuration and dependencies. Use its declared package manager or lockfile to choose how to start the project.