Why AEPilot exists
Motion designers often know the result they want but still have to search menus, rebuild repetitive animation, or translate a visual idea into expressions and scripting syntax. AEPilot works inside the composition that is already open: it reads the project state, uses explicit tools, previews mutations, and verifies the outcome.
The interaction model is closer to a careful collaborator than a prompt box. You can reference exact compositions, layers, and folders; the agent inspects relevant state before acting; and applied changes remain inside an honest After Effects undo or recovery boundary.
Who it is for
- Motion designers who want to create, continue, or refine work through conversation.
- After Effects power users who need prompt visibility and predictable tool execution.
- Studios that prefer user-owned credentials, local endpoints, and local project execution.
Product principles
- Inspect before changing. Live project state outranks a stale index.
- Keep the user in control. Review mode previews mutations before approval.
- Stay provider-neutral. The open-source core is BYOK-first and local-endpoint capable.
- Verify outcomes. A completed turn explains the resulting project state.
AEPilot is developed openly under the MIT License. The current site describes a private preview rather than a generally available release. Compatibility and model claims are published only after the relevant automated and real-host evidence exists.
Explore the source repository, read the privacy model, or use the contact page for preview access and support.