A full AI assistant inside After Effects. It reads the composition you already opened, works through real AE tools, and previews every change before it touches the project.
Windows · macOS · AE 2026 · MIT
live replica
Demo of AEPilot docked inside After Effects: a conversation adds an Appear animation to the Logo layer and reveals the AEPilot wordmark character by character. After approval, the monitor preview and timeline playhead loop together.Every turn stays in one transcript: visible tool traces, assistant reasoning, a reviewed mutation, and the applied result.
Every turn begins with visible read-only tool traces against the open project. You can see what AEPilot inspected before it proposes a change.
AEPilot explains the intended result, then renders the same pending mutation card used by the real panel — target, scope, and review state included.
I prepared a reviewed entrance animation for the Logo and AEPilot layers. Both use matching fade, upward motion, and blur reduction; the text reveals by character.
After approval, pending controls disappear and the turn records an Applied Change with its rollback state. The transcript remains the source of truth.
I prepared a reviewed entrance animation for the Logo and AEPilot layers. Both use matching fade, upward motion, and blur reduction; the text reveals by character.
A final tool trace re-reads the project and reports the observable result beside the applied change, using the same compact disclosure pattern.
I prepared a reviewed entrance animation for the Logo and AEPilot layers. Both use matching fade, upward motion, and blur reduction; the text reveals by character.
Write normally, type @, and choose a real composition, layer, or folder. AEPilot keeps the reference inside the sentence, so “this logo” always means the right logo.
Comps, layers, and folders come from the live project index, so the picker can only offer things that actually exist in the .aep.
The reference stays inside the sentence as a chip — “this logo” still resolves three messages later.
Two layers called BG in different comps carry their parent comp, so the model never guesses which one you meant.
AEPilot talks to providers straight from your machine. Keys never leave the local keystore — there is no AEPilot account and no proxy.
stored locally · never synced
These are tasks from AEPilot’s real After Effects evaluation set. The useful proof is the scope it inspects and preserves, not a made-up productivity counter.
I’ll inspect the current project state first, then prepare a bounded change for review.
The trust model is architectural, not a promise on a landing page.
Keys are written to a local keystore file and never synced; requests travel straight from your machine to the provider. Point it at Ollama or LM Studio and the whole stack runs offline.
Every tool call runs over the local CEP/ExtendScript bridge inside AE itself, so the project file never leaves the machine. There is no AEPilot server in the loop to breach, rate-limit, or deprecate.
Every change is previewed in a review card first, then applied as a single undo group, so one Ctrl+Z restores the exact prior project state. Experiments stay cheap because rollback is never a rebuild.
The core is MIT-licensed and every transcript exports as plain .md or .jsonl, so your prompts, tool traces, and checkpoints remain yours. If AEPilot disappeared tomorrow, your workflow wouldn't notice.
Windows and macOS · After Effects 2026 · Bring your own key.