Back to Playlist · VidFarm Walkthrough Tutorial
Part 4 of 33Introduce VidFarm5 min read
The concept

Agentic video editing — edit by chatting

You describe the outcome in plain English and an AI director does the editing on a real timeline. Here's how it works, the three paintbrushes it paints with, and when to hand the heavy lifting to a local coding agent.

Copies the whole guide — prompts, next steps & all — for your AI agent
Watch this chapter
A single forked short, edited entirely by chat: rewrite a caption, swap a scene, add a motion-graphic beat — the copilot applying each change live on the timeline.

Key takeaways

  • The Trackpad Editor is a real timeline (like Premiere/DaVinci) with an AI copilot you chat with.
  • You steer with words — the copilot drives edits directly on the live timeline via a declared action verb set.
  • Every shot is sourced from one of three paintbrushes: raw clips, HTML/JS hyperframes, or pure AI generation — cheapest to most expensive.
  • Two surfaces, same brushes: the web copilot for quick edits, a local coding agent for full rebuilds and batch work.

Editing without dragging clips

Traditional editors make you do the work: scrub the timeline, trim each clip, nudge keyframes, hunt for the right transition. Agentic editing flips that around. You say what you want — "shorten the intro to two seconds and rewrite the hook" — and the AI director makes the edit for you, on a real timeline you can still see and touch.

The surface is the Trackpad Editor: a timeline with tracks and layers, plus an AI copilot riding shotgun in a chat dock. When you describe a change, the copilot translates it into concrete edit actions and applies them to the live composition. You watch it happen, then iterate. No blank canvas, no manual dragging — just a conversation that produces frames.

The Trackpad Editor full view: a video canvas up top, a multi-track timeline of layers below, and an AI chat dock on the right mid-conversation where the user asked to replace scene 2 with a product demo.
The Trackpad Editor — a real timeline with an AI copilot in the chat dock. You describe the edit; it applies the change to the live composition.

How every shot is sourcedThe three paintbrushes

Whatever you ask for, the director builds each shot with one of three tools. Understanding them is the single most useful mental model in VidFarm, because it maps directly to cost — and the director always reaches for the cheapest brush that does the job.

How VidFarm creates videos — three approaches (Clip Library, HTML-to-video, AI generation) layered on one timeline.
Every finished video is the three brushes layered on one timeline — raw clips, HTML/JS graphics, and AI generation.
The three paintbrushes — broad-stroke Clip Library, mid-fine HTML-to-video, super-fine AI-generated video.
Think of them as brushes, coarse to fine: Clip Library lays down the base, HTML paints the on-screen graphics, and AI generation fills the finest details.
All video styles powered by all three approaches — talking-head, text-on-footage, explainer, cinematic b-roll, animated, and screen capture, each a different mix.
Every style is just a different mix of the three brushes — a talking-head recap leans on raw clips, an explainer on HTML graphics, an animated short on AI generation.
What it costs This ordering is why a caption swap costs almost nothing while an AI-video scene costs the most: a recaption reuses raw footage (brush 1), a title card is a hyperframe (brush 2), and only a fully generated shot spends on brush 3. More on the money side in Free vs paid & BYOK perks and your wallet explained .

Manual walkthroughEdit by chatting (the web UI)

Here's the loop in the browser. It's the same whether you're swapping one caption or restructuring a few scenes — you just keep describing changes and the copilot keeps applying them.

  1. Open a forked composition in the editor

    From a template you've forked, you land in the Trackpad Editor . The timeline shows every layer; the chat dock is on the right (jump straight to it with /editor#chat).

  2. Describe the edit in plain English

    Type what you want: "Replace scene 2 with my product demo and shorten the intro to 2 seconds." Be concrete about which layer or scene and what the outcome is — the copilot targets the exact layer and edits it in place.

  3. Watch it apply, then iterate

    The copilot applies each change live on the timeline. If it's not quite right, say so — "make the hook bigger", "cut the last beat" — and keep going until it looks right. Small, specific asks land best.

  4. Know when to go bigger

    For a full multi-scene re-theme, the copilot will proactively recommend handing off to a local coding agent — it can even save a Markdown handoff brief to your My Files . That's your cue to move the heavy job local (next section).

Close-up of the editor's AI chat dock: a user message reading 'swap the footage in scene 2 and recaption the hook', and the copilot's reply confirming it retargeted the layer and applied the caption change to the timeline.
The chat dock in action. You describe the change; the copilot names the layer it touched and applies it — no dragging required.

Web copilot vs local coding agentTwo surfaces, same three paintbrushes

Agentic editing runs on two surfaces. They paint with the same three brushes, but they have very different powers — and knowing which is which saves you a lot of frustration.

The web copilot lives in the editor chat dock (also Chat and the Library assistant). It edits the live timeline directly, but it has no shell and no filesystem — and the web editor strips <script> on save, so browser-round-tripped compositions stay declarative (CSS, Ken Burns, transitions, animated captions). It's ideal for short-to-medium edits: caption swaps, a scene or two, a single generation, adding captions, approving and scheduling.

The local coding agent — Claude Code or Codex driving the vidfarm devcli — has a real shell and filesystem, the full edit verb set, JS animation adapters, and free local rendering. It's the one for full rebuilds, batch or scripted work, and render-and-critique loops where the agent grades its own output and tries again.

Illustration
In the browser Web copilot
  • Live timeline via chat
  • Caption swaps, a scene or two
  • Approve & schedule
  • No shell / filesystem
vs
Claude / Codex + devcli Local coding agent
  • Full shell + filesystem
  • Full re-builds, batch work
  • JS animation, free local render
  • Render-critique loops
Two surfaces, one director: the web copilot for quick edits, a local coding agent for heavy builds.
Heads up Don't grind a huge transformation one layer at a time in a single web chat turn — it hits context, turn, and timeout limits. When a job is big, move it local. And an honest copilot never claims it ran code or touched files it can't reach — the web surface simply can't.

Claude Code, OpenAI Codex, Gemini CLI, OpencodeDesktop agents — the preferred way

Desktop agents are the preferred way to use VidFarm. A desktop agent is an AI coding agent running on your own machine — Claude Code, OpenAI Codex, Google Gemini CLI, Opencode — driving the vidfarm devcli with a real shell, a real filesystem, and free local rendering.

The best part is the economics: these agents run on the flat-rate subscription you probably already pay — the ~$20/month plan from Anthropic or OpenAI. All the thinking, planning, and editing loops the agent does are covered by that subscription, so you save money and never spend more than your $20/month on the agent side. Your VidFarm wallet is only touched when a job genuinely needs it (an AI generation, a cloud render) — the conversation itself costs you nothing extra.

Tip Pick whichever agent matches the subscription you already have, install the vidfarm skill (below), and every workflow in this post runs from your terminal at no extra per-token cost.
▤ Agent skill Install vidfarm

Copy the full REST + CLI playbook into your agent, or grab the one-line install command from the ⋮ menu.

Tip You never have to leave the app to learn more — deeper director knowledge is a load_skill(...) call away in-place for an installed agent. New to installing the skill? That's the register & setup chapter.

Where to go next

Now you know the model: chat to edit, three brushes cheapest-first, two surfaces for small vs big. From here, set up your account and try the gentlest first edit:

Try editing by chat

Open a template, fork it, and tell the copilot one thing to change. The three paintbrushes and two surfaces make more sense the moment you watch an edit land on the timeline.

Open the Discover feed