Palmier Pro: video editor, in which the AI agent works directly in the timeline
Main chat
A chat for vibe coders: news, guides, live cases, marketplace, and finding executors.
Palmier Pro is a new open-source video editor for macOS that builds AI work not around a separate chat window, but around the timeline itself. It can mount regular video, generate images and video clips within the project, and connect an external agent through MCP.
For a motion designer, this is an interesting interface shift. Instead of “first writing a prompt in one service, then downloading a file and manually spreading it along the tracks,” the agent gets the context of the project and can work with editing next to the person.
What is Palmier Pro
Palmier Pro is written in Swift and designed for Apple Silicon with macOS 26 Tahoe. According to the team, this is a full-fledged editor in the spirit of Premiere Pro, but with AI functions built into the workflow. The editor itself, the MCP server and the agent chat are open in the repository; generative AI processing remains a closed part of the product and requires a subscription account.
This is an important distinction. Palmier Pro should not be perceived as a completely local replacement for cloud video generators. Open source allows you to learn and use the editor, timeline automation and integration with agents, and media generation remains a service function.
How an agent gets into a timeline
When the application is running, Palmier Pro picks up the local MCP server at http://127.0.0.1:19789/mcp. It can be connected to Claude Code, Codex or Cursor. The official codex project instruction uses a command:
codex mcp add palmier-pro --url http://127.0.0.1:19789/mcpAfter that, the agent can work not with an abstract description of the video, but with the project opened in the editor. In the real process, this is suitable for repetitive operations: decompose prepared clips, assemble a draft sequence, create structure variants, or make batch changes after comments. The final decision on rhythm, drama, color and quality is still left to the designer.
The local address here is principled. The integration works within the machine on which the Palmier Pro is open, so an agent’s access to the timeline does not automatically turn into public access to the project. But the rights of a particular agent and the list of his tools still need to be checked before working with client materials.
Generating directly in the installation process
Palmier Pro claims built-in work with Seedance, Kling and Nano Banana Pro models: the user does not need to leave the editor to get a rough frame or an asset. This approach is especially useful early on: you can quickly test the editing idea, the pace of the scene or the transition without spending time preparing each material perfectly.
There is a practical limitation here. A generative frame can be a good layout for a composition, but not always a ready-made final asset: you need to separately evaluate the stability of details between clips, the consistency of light, the rights to use the model and the client’s requirements for the origin of media. Therefore, a reasonable scenario is to use generation for storyboarding, animating and finding direction, and then replace successful workpieces with approved production material.
Where the tool might come in handy
The Palmier Pro looks most appropriate in three scenarios:
- Fast animator. The agent helps to assemble a draft clip of references, test generation and screen recordings to discuss the rhythm before expensive production.
- Serial content. For short videos with repeatable structure, you can automate the preparation of versions, tracks and editing options.
- Designer and developer in the same cycle. MCP turns timeline into another working context for an agent tool: along with code, Figma file and repository.
The project is currently limited to macOS 26 on Apple Silicon. Teams on Windows, Linux or earlier versions of macOS should see it as a category direction rather than an immediate replacement for the stack.
How to check out Palmier Pro without risking your main project
It is better to start with a short test video and a copy of the materials. Open the project, connect the MCP only to the selected agent and formulate a small task: for example, create a draft sequence of several clips or prepare two versions of the order of scenes.
For the first test, you should check four things:
- does the agent understand the structure of the timeline and the selected tracks;
- how predictably it changes the existing installation;
- is it convenient to roll back and compare options;
- does the bundle speed up work on a specific video format, not just the demonstration.
Such a test will quickly show the limit of usefulness. A good agent editing tool saves time on mechanics and options, but does not relieve the author of the responsibility for the final directorship.
Why the Palmier Pro should be watched
Palmier Pro is interesting not only as another AI video editor. It shows a more mature model: generation, installation and agent automation end up in the same workspace, rather than being linked by a chain of exports between different services.
For the motion design market, this means that in the nearest tools, it will be important not only to choose a generation model. Equally important will be the agent’s access to the project structure, manageability of changes, version history, and the ability to quickly regain control of the outcome. The Palmier Pro is still early and platform limited, but these are the questions it poses very accurately.
