$npx -y skills add remotion-dev/remotion --skill studioStart Remotion Studio from packages/example and open it in the Codex browser. Use when the user invokes /studio or $studio, asks to launch the example Studio, or wants the Remotion Studio dev UI available locally.
| 1 | # Remotion Studio |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | Prepare the Remotion monorepo, launch the example Studio, and open the served URL in the Codex in-app browser. |
| 6 | |
| 7 | ## Workflow |
| 8 | |
| 9 | 1. From the repository root, run: |
| 10 | |
| 11 | ```bash |
| 12 | bun i && bun run build |
| 13 | ``` |
| 14 | |
| 15 | 2. Start Studio from the example package: |
| 16 | |
| 17 | ```bash |
| 18 | cd packages/example && bunx remotion studio --no-open |
| 19 | ``` |
| 20 | |
| 21 | Use `bunx`, not `npx`. Always pass `--no-open`; Codex should open the printed URL explicitly instead of letting the CLI open a browser. |
| 22 | |
| 23 | 3. Do not check `localhost:3000` before starting Studio. Another worktree may already be using that port, and probing it first can open the wrong Studio. |
| 24 | 4. Keep the server process running and read its output for the local URL. The expected default is `http://localhost:3000`, but the CLI output is the source of truth. |
| 25 | 5. If the CLI says Studio is already running, use the exact URL printed by that CLI invocation. Only verify with `curl` after the CLI has identified the URL for this worktree. |
| 26 | 6. Open the exact CLI URL in the Codex in-app browser yourself. If no browser tool is available yet, use `tool_search` for the in-app browser control tool, then navigate to the local URL. |
| 27 | 7. Tell the user the Studio URL and whether this is a newly started or already running server. |