Docs · Agents
Named agents,working in front of you.
You write what you want in the Agents panel, and the timeline builds itself before your eyes. Every move shows, sensitive moves wait for your approval, and the whole turn undoes with a single Undo.
Who does what
Each agent has a craft, a vocabulary and its own tools in a module. A conductor receives your request, asks a question if it is unclear, splits it up and delegates. You call them by name.
- The Editor
- Builds and corrects the timeline: logging, shot order, cuts, pace, J-cuts and L-cuts, titles, 16:9 and 9:16 formats.
- The Colorist
- Grades: Rec.709, log, skin tones, LUTs, consistency between shots.
- The Sound designer
- Foley, ambiences, sound effects, locked to picture.
- The Mixer
- Levels, voices, ducking music under speech, broadcast standards (-14 LUFS for the web, -23 for television).
- The Retoucher
- Crops, corrects, cuts out: thumbnails, posters, social formats.
- The Composer
- Composes: BPM, scales, patterns by style (afrobeat, mbalax, amapiano, lo-fi), kora, sabar, balafon.
- The Motion designer
- Writes a HyperFrames composition from a brief and the client's brand book, renders it, places it over the shot.
They have no magic wand: they use the same tools as you, through the same path as the mouse. That is why you see the app move, and why you can take back control at any moment.
The Agents panel
⌘J opens the Agents panel, a tab of the right block in Edit. The dot at the top right of the window says where things stand: grey when no service is connected, green when the agents are ready, breathing blue when an agent is working, red on an error. A click on it opens the panel.
You write in plain English, as you would speak to someone on the team: "make me a fifteen-second teaser with the drone shots, the kora music and an opening title". For a long request, the agent first answers with a short plan; you change it or say "go". For a short request, it acts.
- Every call shows
- Cut at 00:00:04:00, place this clip on V2, add a twelve-frame fade: you read what it does as it goes, and the timeline shows it at the same time.
- Sensitive moves wait
- Deleting a shot, overwriting an export: a card asks for your approval, with the real parameters. You accept, you refuse, or you trust it for the session.
- One turn, one Undo
- Everything the agent did for one request fits in a single undo step, named "The Editor: …". "Undo this turn", or ⌘Z, puts the timeline back as it was. Redo does it again.
- A budget per turn
- An agent has a number of calls per request. It does not loop forever.
What leaves, what stays
The agents reason on a server, your footage stays on your machine. What leaves so they can understand: the state of the timeline as text, a transcript when one is needed (it is made on your machine, by Whisper), a thumbnail when the agent asks to see an image. Never the whole video. Without a connection, no agents, and nothing else in KoraCut needs the network.
What is still to come
The app is free and open source, without agents: the version you compile yourself has neither the panel nor the connection to the service. The agents are a subscription service, and that service is not open. Today, the Editor really edits inside the app, but on a test service, without an account; the KoraCut account, the subscription and the video count arrive with the launch, with no date announced. The other agents follow their modules.