Docs

How FrameJam works

FrameJam is a small local app that runs next to your coding agent. It doesn't make videos: your agent does, with any tool. FrameJam does the two jobs chat does badly: picking a style and giving precise feedback on the rendered video.

What runs where

One Node program, framejam, does three things:

  • Serves the web UI and a REST API on http://localhost:2400. Open it in your agent app's browser pane.
  • Speaks MCP over stdio when started with --stdio. This is how Cursor, Claude Code and Codex connect.
  • Speaks MCP over streamable HTTP at http://localhost:2400/mcp, for other MCP clients.

Reviews, versions and comments are JSON files in ~/.framejam. If several agent windows each start their own copy, the first one hosts the UI and the rest share the same folder, so a review you finish on the page reaches whichever agent is waiting.

The loop

  1. Optionally pick a playbook and a style. Name them in your request, or type /framejam:playbook or /framejam:style and your agent opens a page where you choose and press Start. A playbook is how the video gets made, a style is the look; both are defaults your request can override.
  2. Your agent builds and renders. It makes the video with any tool and renders a new mp4 per version. With Hyperframes, it writes the composition in HTML and GSAP and runs npx hyperframes lint first.
  3. It opens a review. open_review returns a URL, and the page plays the rendered video.
  4. You comment. Pause and type, click to pin a spot, or drag across the filmstrip for a range. Enter adds the comment.
  5. You press Finish review. That locks the version. The agent has been blocked in wait_for_feedback (for up to about 10 minutes), so it gets every comment at once: timestamps, pin positions and frame images with your pin drawn on the spot you clicked. If it stopped waiting, your comments are saved: say "apply my FrameJam feedback". Changed your mind? Edit comments reopens the round.
  6. Version 2 arrives. The agent calls add_version with a one-line note, and the page moves to it by itself.

The same loop works for a storyboard of still panels, before anything is animated. Every part of the page is explained in Review videos with your AI agent.

If your agent wasn't listening

Once an agent ends its turn, nobody is waiting. Your comments are saved, and the page shows one line to paste into the chat. The agent then calls get_feedback, which picks up whatever hasn't been delivered yet.

Try it

After you install FrameJam, open localhost:2400 and ask your agent:

Make a 7-second launch teaser with FrameJam and open it for review.

Limits worth knowing

  • The UI lives in whichever process got port 2400. If that window closes, start another or run npx -y framejam start.
  • Frame thumbnails need ffmpeg and a rendered mp4.
  • There is no auth. It binds to 127.0.0.1 by default; be careful with tunnels.

Something not working? See Troubleshooting. Coming from another editor? Compare AI video editor alternatives and Remotion vs Hyperframes.

How to edit videos with Claude walks through it step by step, with a video. More in Guides.