Remocn Studio
for your desktop.

That's the normal first-launch check for a downloaded app. Confirm the Gatekeeper prompt (or right-click the app and choose Open). It only asks once.

Studio runs on your own agent subscription, so the agent's CLI has to be signed in once. Open a terminal and run claude, codex login, copilot login, or grok login for the agent you use, sign in with that subscription's account, then send your message again.

Being signed out is the one thing that locks the composer — it unlocks by itself once you're in.

When a folder opens, Studio checks its environment and lists anything wrong right above the composer: the folder isn't a Remotion project, dependencies aren't installed or disagree with the lockfile, no entry point is registered, or no composition is named Main. Missing dependencies can be installed straight from that card — when every check passes, the card disappears.

Studio uses your project's own package manager, detected by its lockfile — package-lock.json means npm, yarn.lock yarn, pnpm-lock.yaml pnpm, bun.lock bun — and never mixes in another one. If that manager isn't installed on your machine, the environment card says so and offers an Install button that runs the official installer.

Older builds could report the sidecar as starting forever — that's fixed. Update to the latest version from this page; if it ever shows up again, the composer offers a Restart button that brings the sidecar back without relaunching the app.

Exports render through your project's own Remotion, honoring its remotion.config.ts. Make sure the project's dependencies are installed and its @remotion/* packages are on the same version — the environment card above the composer flags a mismatch.