Getting started
From nothing to a narrated demo
Six steps. The first four are setup you do once; the last two are the part you will repeat every time you ship something worth showing.
macOS 15 or later · Apple Silicon
Before you start
- ✓A Mac on Apple Silicon, running macOS 15 or later
- ✓Claude Code, or another agent that loads Claude Code plugins
- ✓Whatever your demo happens in — a browser, a terminal, your own app
Create your account
Sign in at corgy.ai with Google, or with a link emailed to you. A new account starts with 1,000 credits, which is enough to plan, narrate and voice a first demo without deciding anything about money.
Credits are only spent on the parts a model does for you — planning a recording, writing the narration, voicing it. Cutting clips and exporting are free, however many times you redo them. See what things cost.
Install Corgy for Mac
The recorder is a Mac app. It drives a real cursor across your whole desktop — a browser, a terminal, an editor, a native app — which is why a demo of a terminal and a browser can be one video rather than two.
macOS 15 or later · Apple Silicon
Drag Corgy into Applications, open it, and sign in with the account from step one. Then open Settings → Command line → Install, which puts a corgy command on your PATH. Your coding agent needs that name to drive a recording; the app and the command are the same program.
Grant the two macOS permissions
Corgy needs Screen Recording, to capture the run, and Accessibility, to move the cursor and read the labels on screen. macOS will ask the first time.
macOS attaches these permissions to whatever launched Corgy, not to Corgy itself. Started from the app, that is Corgy.app. Driven from an agent session, it is your terminal — so that terminal is what has to be ticked in System Settings, and it has to be restarted afterwards for the grant to take. This is the single most common reason a first recording does nothing.
Add the demo skill to your coding agent
The planner ships as a Claude Code plugin. Run these two commands once, in any project.
>/plugin marketplace add stormkit-io/agent-skills>/plugin install corgy@stormkit
That adds /corgy:demo, which reads the repository you are standing in — the router, the real URLs, the labels as they are actually rendered — and plans the demo against screens that exist rather than ones it guessed.
Describe the demo, then read the plan
Change into the repository of the thing you want to show, and say what the demo is for in one sentence.
>/corgy:demo "a 60-second onboarding demo for new users"
Back comes the demo as scenes: what each take proves, the screen it starts from, roughly how long it runs. Nothing records yet. Push back — drop a scene, reorder them, ask for one cut instead of four — and when it looks right, say go. Corgy records the takes one at a time, walking each flow once to prove every target resolves before it rolls.
No Mac yet? The skill still plans the demo and writes the narration prompt without the recorder — you just cannot record from it.
Edit, narrate, export
The takes land in the editor as a timeline that is already cut into clips.
Trim what dragged, freeze a frame where something needs explaining, and let Corgy write the narration — it is written against what the recorder actually clicked, not guessed from pixels. Pick a voice, render, and you have an mp4 and a link to share.
Open the editorWhen something does not record
- The run starts and the screen never changes.
- The permissions in step three are attached to the wrong application. Tick the one that launched Corgy — usually your terminal — and restart it.
- corgy: command not found
- The app is installed but its name is not on your PATH. Open Settings → Command line → Install in the Mac app. If you also build Corgy yourself, the two can fight over the same link — the pane says when it points somewhere else.
- A step aims at something that is not there.
- The plan named a label that does not match what the page renders. Tell the agent the label as it actually appears, in the words on screen, and ask it to re-plan that scene.
- It installs and then will not launch.
- The disk image is Apple Silicon only. On an Intel Mac it looks like a broken build, but the machine is the problem.
Still stuck, or want to see how we use it ourselves? Read the blog.