OpenParable
Skip to content
← Back to skills

Studio

Apps & Automation
studio

Studio 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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
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

  1. From the repository root, run:
bun i && bun run build
  1. 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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Tell the user the Studio URL and whether this is a newly started or already running server.