FrameJam adds timestamped feedback for agent-made video edits

• FrameJam turns agent-made video review into frame-specific feedback: moritzkremb's launch post says users can point at a frame and send an automatically timestamped screenshot to Claude Code, Codex, or another harness.
• The tool is presented as free and open source, with a local MCP server that connects the editor to compatible agents moritzkremb's FrameJam post.
• One demonstrated production stack used Opus 5.5 as orchestrator, Suno v6 for music, Hyperframes, Seedance 2.5, Cursor's image generator, and FrameJam for iteration moritzkremb's workflow breakdown.
• A separate Codex pipeline took a reel through preparation, text-feedback review, Buffer publishing, live verification, and receipt archiving AmirMushich's publication engine.

FrameJam's [project page]FrameJam project page describes a local MCP server beside the chat, while the MCP architecture docs explain the host, client, and server handoff behind that connection. The practical trick is moritzkremb's feedback-layer reply, which turns a clicked frame into a precise revision request instead of a paragraph trying to describe a timestamp.

FrameJam's core loop is short. The linked project page FrameJam project page lays it out as:

1. Choose a visual style, including its colors, fonts, and motion language.
2. Ask an agent to create a video, such as a short launch teaser.
3. Click the exact frame or element that needs changing. FrameJam captures the timestamp and screenshot.
4. Finish the review, and the agent applies the notes to produce Version 2 in the same tab.

The creator says the tool also works with MP4s made elsewhere, so the review layer can sit on top of an existing render rather than owning the entire production pipeline FrameJam project page.

The creator describes FrameJam as “an easy feedback layer on top” of an agent harness moritzkremb's reply. That makes the project an interface for the costly part of generative video work, the repeated review and revision cycle, rather than a replacement for Claude Code, Codex, or Cursor.

The project page says FrameJam runs locally, requires no account, keeps data in ~/.framejam, and does not upload footage FrameJam project page. Its local MCP server exposes the editing surface to agents. The official MCP architecture guide describes the same pattern as an AI host connecting through an MCP client to a tool server.

That local-first design also lets the tool stay useful across different renderers. Hyperframes, the framework named in the creator's demo, describes itself as an open-source system that turns HTML, CSS, media, and seekable animations into deterministic MP4s Hyperframes.

The public demo started with a prompt to Claude to make a video about what it feels like to be European, followed by a finished montage the next day moritzkremb's finished video. The production breakdown listed six parts:

1. Orchestration: Opus 5.5.
2. Music: Suno v6.
3. Video framework: Hyperframes.
4. Generated video: Seedance 2.5.
5. Images: Cursor's built-in image generator.
6. Iteration: FrameJam moritzkremb's build breakdown.

The making process included researching the topics, writing lyrics, generating music, creating images and video with external tools, then stitching the pieces together. The creator said FrameJam handled much of the iteration moritzkremb's process reply. Another related demo appeared from gregisenberg's demo, though that post did not include a written workflow breakdown.

The project sits in a growing set of coding-agent video tools. video-use takes raw footage in a folder and returns final.mp4 through a Claude Code conversation, while FrameJam focuses on the human review gesture between renders.

Frame-level review can also be part of a publishing pipeline. AmirMushich described a Codex-based engine that made and published an Instagram Reel with zero manual actions claimed AmirMushich's publication engine. Its stages were:

• Input: project context and an automated screencast.
• Prepare: vertical reel, headline, music, intro footage, cover, and caption.
• Review: text feedback, revision, then approval.
• Publish: the agent sends the finished asset to Instagram through the Buffer API.
• Verify and archive: check the live post, save the MP4, caption, and render settings, then record the post URL and delivery receipt.

FrameJam handles the frame-precise feedback step in a comparable loop, while AmirMushich's files show what happens after approval: the rendered asset and its verification record remain part of the project archive AmirMushich's publication engine.

The current workflow is organized around choosing a style. The project page also lists a beta live player for clicking exact elements inside a video and support for reviewing any MP4 FrameJam project page.

The creator said presets and templates are planned so users can start from specific video types rather than only from broad visual styles moritzkremb's reply about presets.