Studio Modes
SkillWeb & browsingLets your agent check what actions and features are allowed in each Remotion Studio mode before building or reviewing Studio UI.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Studio Modes skill
About this capability
Understand the capabilities and restrictions of each Remotion Studio mode. Use when implementing or reviewing Studio actions, permissions, availability, or UI across interactive, detached, deployed, and browser-based Studios.
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:
- 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. - Regular Studio with the preview server detached:
previewServerConnectedisfalse. The Studio is effectively read-only, although client-side rendering remains available. - 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.
- Browser Studio: Deployed at
remotion.dev/newand 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
- 60k
- Forks
- 5k
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
studio-mode- Source
- github.com/remotion-dev/remotion