Iterate on videos with your agent, frame by frame.

telestrator turns your feedback on a video into notes your AI agent can act on. Pause on any frame, pin or draw what's wrong, and write a line. Claude Code, Codex, Cursor or any agent gets the exact frame and fixes it.

Paste it into your agent. It sets everything up.

telestratorlaunch-v7.mp4Connect agentSound on

s3 · The problems4 · The product1920×1080 · 30 fps

Relay

Standups,
without the
meeting.

Async updates your team
actually reads.

Try Relay freeSee how it works

Today12 updates · 3 blocked

Maya ChenShipped onboarding v2Shipped

Tom OkaforWaiting on API keysBlocked

Ana RuizPricing page, ready to reviewIn review

Leo ParkRelease notes draftedShipped

4.5 hoursa week, lost to status meetings.

00:00:03:1000:00:07:2200:00:10:1500:00:12:04 / 00:00:38:00

00:00:00:0000:00:10:0000:00:20:0000:00:30:00

s3 · The problem

s4 · The product

s5 · Get started

Comments1✎ 2

Notes1 open2 open1 open · 1 closedShow resolved

00:00:03:1000:00:07:2200:00:10:1500:00:12:04s3 · The problems4 · The product

◎ spot 408, 703 ×✎ Drawing · 1 mark ×

What should change here?Tagline is too small on mobileCards should slide in one by one

Add note

100:12:04ACKNOWLEDGEDRESOLVED×

Tagline is too small on mobile

◎ spot 408, 703

AGENTTagline 43 → 58px in product.html:42. Re-rendered, checked the frame.

200:12:04ACKNOWLEDGED×

Cards should slide in one by one

✎ circled 1185,257 719×654 (pink)

ClearCopy for agent

Write in the sidebar · P point · D draw on the frame · drag the filmstrip for a range · N write a note · Space play · H markersrenders/launch-v7.mp4 · 38.0 s · 1920×1080 · 30 fps · 5 scenes

Pause, point, write. Your agent picks it up, fixes it, and resolves it.

Start with one command

$ npx telestrator path/to/video.mp4

A project folder works too: it opens the newest render. The review opens in your browser, and notes stay on your machine.

$ npx telestrator init

Once, to connect your agent: Claude Code, Codex, Cursor, VS Code, Gemini CLI, Windsurf and more. Then ask it to “check the video feedback”.

What your agent gets

## 1. 12.13s (frame 364) · The product
- Feedback: tagline too small on mobile
- Narration there: “Async updates your team actually reads.”
- Pointing at: #s4 > p.tagline
- Source: scenes/product.html:42
- Styles now: font-size 43px; color #5f5a52
- Element box: 98,645 490×116 (in 1920×1080)

Plus the frame itself, with your pin or drawing on it, as an image.

How it works

Pause on the frame. Step frame by frame with the arrow keys.
Point at something (P), draw on it (D), or drag the filmstrip for a range.
Write one line. The note lands at the playhead.
Your agent fixes the source, re-renders, checks the frame, and resolves the note. If it's unsure, it asks you under the note.

For agents

An MCP server your agent talks to. It reads and writes the same notes you see, so replies show up in your review as they happen.

`get_feedback`	Open notes, with each note's frame as an image
`watch_feedback`	Waits for your notes while you review: hands-free
`get_frame`	Any frame, to check a fix after a re-render
`acknowledge`	“Seen it, working on it”
`reply`	Asks you a question under the note
`resolve` · `dismiss`	Closes the note, saying what changed or why not
`add_note`	The agent critiques the render and leaves its own notes

Works with what you render

HyperFrames	Pointing names the exact element on that frame, with its source line and styles
Remotion	Points at the spot in the frame; scenes and captions from a sidecar file
Any MP4, MOV, WebM	The spot, the time, the frame, and captions from a `.srt` or `.vtt`

Questions

Is it free?: Yes. It's MIT licensed.
Does my video leave my machine?: No. It runs locally, and notes are JSON files next to your video in .telestrator/. Commit them if you want the feedback in git.
Which agents work?: Any agent that supports MCP. init sets up the ones you have. Without MCP, use “Copy for agent” and paste.
Do I need HyperFrames?: No. Any video works. With a HyperFrames composition, pointing also knows which element you mean and where it's written.
Something isn't working?: Run npx telestrator doctor. It checks Node, ffmpeg, your agents, and what your video resolves to.
Where's the code?: On GitHub. Issues and pull requests are welcome.

Set up telestrator so I can review my rendered videos and you can act on my feedback.

1. Connect yourself to the telestrator MCP server. Run `npx telestrator init`, or add an MCP server named "telestrator" with command `npx` and args `["-y", "telestrator", "mcp"]`. If I need to restart this session to load the tools, tell me.
2. Find my latest render (check ./renders, ./out and the project folder; ask me if there are several) and open the review for me: `npx telestrator <video or project folder>`. For a HyperFrames project, make sure the composition is found; if it isn't, pass `--composition <path to index.html>`.
3. Run `npx telestrator doctor` and fix anything it flags.

Then, whenever I say "check the video feedback":
- Call get_feedback and read every open note, including its frame image.
- acknowledge each note as you pick it up.
- Fix the source. Each note gives the time and frame, the scene and its file, what's being said, and for pointed elements the source file:line and current styles.
- Re-render, check your fix with get_frame at the note's time, then resolve the note with one line on what you changed.
- If a note is unclear, reply with a question instead of guessing. If you won't change something, dismiss it with the reason.

If I say "watch mode", call watch_feedback in a loop and handle my notes as they arrive.
If I ask you to critique the render, step through it with get_frame and leave your own notes with add_note.

see telestrator on github ↗
made by @itsloukman ↗