getting started
How extynt works
Most AI tools for After Effects have the model write a script and run it. No error counts as success. extynt has no script tool.
A script that runs without an error has not necessarily done the right thing. It might have hit the wrong layer, set a value After Effects quietly clamped, or skipped a comp. In a real project you find out later, usually at render time.
The loop
- Read. extynt reads the project first: comps, layers, effects, expressions and what is installed on this computer. Plans are built on what is there, not on guesses.
- Plan. The change becomes a list of typed operations, such as “add an effect” or “keyframe a property”, each with exact targets and values.
- Apply. Just before applying, extynt checks that your project is still the one the plan was built on. If it has changed, nothing is applied and the plan is built again. Each batch is one named undo group.
- Verify. After applying, extynt reads the project again and checks every operation against the plan, then reports the result.
Compared with script-running tools
| Script-running AI tools | extynt | |
|---|---|---|
| How changes are made | The model writes a script and it runs | Typed operations, checked before they run |
| Before anything changes | Often runs straight away | A plan you can read, apply or cancel |
| After it runs | No answer beyond success or an error | The project is re-read and compared with the plan |
| If it is wrong | Restore a saved copy of the whole project | Undo just that plan, or its last step |
| What the model can touch | Anything a script can reach | Only operations extynt knows how to check |
When something cannot be confirmed on your version of After Effects, extynt says so before it runs and asks you. Nothing is reported as done unless it was checked. When a check fails, you get the reason, not a green tick.
The same rules apply when Claude, Codex or another MCP client is doing the work. They get the same typed operations and the same checks, and they cannot run raw scripts in your project.
Panel or MCP
The extynt panel and outside MCP clients such as Claude and Codex are both first-class. They write the same typed plans, which pass the same checks and leave the same receipts.
Before a job counts as finished, extynt checks the request against the project: every feature the request names has to be there, and nothing may sit off-frame or clipped. The panel does this itself and sends the work back when something is missing. An MCP client asks for the same check with ae_check_request.
Where it has been checked
Before a release, a test kit runs every operation on real After Effects. Kit 0.9.8t ran on After Effects 25.6.6 and 26.5.0 on Windows in October 2026: 752 of 756 cases passed on 25, and 756 of 756 on 26. The other 4 on 25 are effects that version does not have. A run on macOS is being prepared, so we do not claim macOS is verified yet.
On 14 October 2026 a title ident and a rocket orbit, both built from scratch, were completed on real After Effects 25 and 26 in the panel, and on 26 over MCP. We checked each run against a dump of the scene and rendered frames, not the model’s own report.