Studio Modes

SkillWeb & browsing

studio-mode is a skill that helps an AI agent understand the capabilities and restrictions of each Remotion Studio mode. It covers interactive, detached, deployed, and browser-based Studios, so the agent can reason about Studio actions, permissions, availability, and UI before implementing or reviewing features. Use it when you need your agent to know what a given Studio mode can and cannot do.

Use Studio Modes in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Studio Modes and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Studio Modes skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Make sure your AI agent can load skills and has access to the studio-mode skill files.

Studio ModesStart free

What your AI can do with it

  • Explain what each Remotion Studio mode can and cannot do
  • Describe Studio actions and permissions per mode
  • Compare availability across interactive, detached, deployed, and browser-based Studios
  • Guide UI decisions for Studio features based on mode restrictions
  • Support implementation and review of Studio actions

Getting started

  1. Make sure your AI agent can load skills and has access to the studio-mode skill files.
  2. Add the studio-mode skill to your agent's skill set or configuration.
  3. Ask the agent to use studio-mode when working on Remotion Studio actions, permissions, availability, or UI.
  4. Review the agent's output against the mode restrictions the skill provides.

What this skill tells your AI

The instructions your AI receives, as published by remotion-dev/remotion in .agents/skills/studio-mode/SKILL.md and read by ahel’s review.

Remotion Studio operates in four modes:

  1. Regular interactive Studio: Started with npx remotion studio. A Studio server is attached and the Studio is fully interactive. It can render server-side, use "Open in" actions, execute codemods, install packages, and perform other server-backed actions.
  2. Regular Studio with the preview server detached: previewServerConnected is false. The Studio is effectively read-only, although client-side rendering remains available.
  3. Read-only Studio: A deployed Studio with no server attached. Hide or disable actions that require a server. GitHub is the only supported "Open in" action.
  4. Browser Studio: Deployed at remotion.dev/new and backed by a virtual file system that is hidden from the user. It cannot use "Open in" actions, but it can install dependencies and execute codemods.

When adding or changing a Studio action, determine which modes support it and hide or disable it everywhere else.

Signals

GitHub stars
61k
Forks
5k
Last commit
Sep 2026

Questions

What does studio-mode cover?
It covers the capabilities and restrictions of each Remotion Studio mode: interactive, detached, deployed, and browser-based. It helps with Studio actions, permissions, availability, and UI.
When should I use studio-mode?
Use it when implementing or reviewing Studio actions, permissions, availability, or UI across interactive, detached, deployed, and browser-based Studios.
Does studio-mode support all Remotion Studio modes?
It covers interactive, detached, deployed, and browser-based Studios. Other modes are not mentioned.
Can studio-mode help with permissions?
Yes, it helps understand permissions for Studio actions across the different modes.
Advanced
Item type
skill
Key
studio-mode
Source
github.com/remotion-dev/remotion