Studio
Apps & AutomationstudioStudio is an Agent Skill for apps & automation published in the remotion-dev/remotion repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Start 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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/remotion-dev/remotion/blob/HEAD/.agents/skills/studio/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/studio, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Remotion Studio
Overview
Prepare the Remotion monorepo, launch the example Studio, and open the served URL in the Codex in-app browser.
Workflow
- From the repository root, run:
bun i && bun run build
- Start Studio from the example package:
cd packages/example && bunx remotion studio --no-open
Use bunx, not npx. Always pass --no-open; Codex should open the printed URL explicitly instead of letting the CLI open a browser.
- Do not check
localhost:3000before starting Studio. Another worktree may already be using that port, and probing it first can open the wrong Studio. - 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. - If the CLI says Studio is already running, use the exact URL printed by that CLI invocation. Only verify with
curlafter the CLI has identified the URL for this worktree. - Open the exact CLI URL in the Codex in-app browser yourself. If no browser tool is available yet, use
tool_searchfor the in-app browser control tool, then navigate to the local URL. - Tell the user the Studio URL and whether this is a newly started or already running server.