News

Palmier Pro and the Rise of Timeline-Native Generative Editors on Mac

ยท RenderBob team

Palmier Pro generates clips on a macOS timeline with Seedance, Kling, and Nano Banana Pro, and opens the project to Claude, Codex, and Cursor over a local MCP server.

A Mac timeline with a generated clip sitting on its own lane beside a preview of the same shot.

A Mac editor category is forming around one interaction: generation happens on the timeline, in the same session as the cut. Palmier Pro is the clearest public example. It is free, written in Swift, and open source under GPLv3, with the generative processing pipeline kept closed.

The clip lands where you are already editing

The public README describes a timeline editor that generates video and images with Seedance, Kling, and Nano Banana Pro inside the project. You are not exporting from a separate generator and dragging the file back in. Model choice and the cut share a session. The repo also exposes a local MCP server at http://127.0.0.1:19789/mcp while the app is open, so Claude, Codex, or Cursor can read the project and edit it.

Apple Silicon, and only that, for now

Palmier's own notes limit the app to macOS 26 on Apple Silicon. Intel Macs, Windows, and Linux are out for the moment, and the founders have said they are staying on the Mac core before widening support. The GitHub repo was created on 7 April 2026. On 23 September 2026 the public API reported 14,451 stars and 1,124 forks. That is a lot of attention for a timeline-native generator, and it is still a single-platform tool.

The closed layer is the product decision

The editor, the MCP server, and the in-app agent chat are open. The generative pipeline is not. Model orchestration, any local-versus-cloud routing, and reference conditioning live in that closed part. An editor that picks local Apple Silicon inference or a cloud model per clip, from the job's memory and quality needs, is answering the same timeline pattern with a different production rule.

People are already cutting this way. The remaining job is making the local-or-cloud choice feel like part of the edit. RenderBob is built around that choice: generated clips on their own timeline lane, local when the machine can carry the preview, cloud when the shot needs it.

More from the blog

All posts