Here is what it looks like in practice.
We asked Claude Code to add travel-vlog style titles to footage shot on a rainy day in Maizuru. On the left is the conversation with Claude Code; on the right is FrameGleam. At the end it also exports a vertical version for TikTok.
Just ask, and it edits the video for you.
The FrameGleam repository ships with instructions for Claude Code (a skill). When you ask Claude Code to edit a video, Claude reads them first, learns how FrameGleam works, and then gets to work.
Claude turns your footage into stills and looks at them to decide what to keep. It checks the result the same way, with stills and a preview, so all you do is ask and wait.
Before rendering the final video, it shows you the preview and asks whether to go ahead. If you want changes, tell it in words or make them yourself in the editor.
Join the Arashiyama clips in footage/ in the order they were shot. Fade to black between clips, put “Arashiyama” at the start and “Fin” at the end.
- Read the FrameGleam skill
- Import the clips and sort them by recording time
- Look at stills taken every 2 seconds and cut shaky or overlong parts
- Add fades between clips and titles at the start and end
- Check the fades and titles on stills that match the final render
- Render a preview and check that no cut freezes
I've rendered a preview (1:58). I cut the shaky first 3 seconds. Shall I render the final video?
Edit side by side with Claude, in the same editor.
Ask Claude to join the clips, fade between them and add a title, watch it happen in the editor, and fix whatever bothers you as it goes. If you want a bigger rework, ask AI again. Both kinds of edits build up in the same project.
- Work at the same time as Claude
- Keep the editor open while Claude works. Its edits show up on screen as they happen, and you can step in and fix things yourself. Whoever made an edit,
undotakes it back one step at a time, so letting Claude try something costs you nothing. - AI checks its own work
- Stills that match the final render (
snapshot) and a check that no cut freezes (check) let AI judge the result by looking at it. The bundled skill tells Claude to ask you before rendering the final video. - Premiere-style shortcuts
- J/K/L to play, I/O for in and out points, Q/W, Ctrl+K, Ctrl+D and more, so your hands already know the editor.
- Extend it with one Ruby file
- Add effects, transitions, titles, commands and menu items without touching the core. You can ask AI to write extensions too.
Missing a feature? Add it yourself.
Define the parameters once, and FrameGleam builds the command-line key=value options, a JSON Schema for AI, and the input fields in the editor.
effect test applies your extension to sample footage and returns three stills. AI can write the extension and check it too.
Extensions live in your project's extensions/ folder, so updating FrameGleam won't break them.
FrameGleam.effect :warm_tone do
label "あたたかい色", en: "Warm Tone"
param :strength, :float, default: 0.1,
range: 0.0..0.5, description: "強さ",
description_en: "Strength"
filter do |p, ctx|
"colorbalance=rm=#{p.strength}:bm=#{-p.strength}"
end
end
What's included
| Editing | Import (reads recording time), sort by recording time, cut, extract, split, ripple delete, move |
|---|---|
| Effects | Basic Correction, DeNoise, Chroma Noise Reduction, Video Stabilization, Volume |
| Transitions | Dip to Black |
| Graphics | Text (titles), Image (logo / watermark) |
| Audio | An extra audio track (A2) for sound effects and more |
| Export | MP4 (H.264 / H.265), 720p previews, partial exports. Hardware encoding with NVENC, QSV and AMF. Unchanged parts aren't re-rendered, so later exports are faster |
| Languages | English and Japanese |
Requirements
| OS | Windows, or WSL (Ubuntu) on Windows |
|---|---|
| Ruby | 4.0 |
| ffmpeg | ffmpeg.exe for Windows (not included) |
| mpv | For playback with sound in the editor (optional) |
| AI | Claude Code (other AI tools work too if they can run commands) |
FrameGleam is at version 0.1 and still in development. Details may change.
A note from the developer
FrameGleam is made by one independent developer. It started because I was tired of joining family videos in shooting order and adding titles by hand every time, so I made it something I could ask AI to do.
The paid plans exist so I can keep doing these things:
- Keep the core open source and free to use
- Keep it free of ads
- Keep shipping updates and bug fixes
You never have to subscribe: the released versions stay free. If FrameGleam turns out to be useful to you, support then would mean a lot.
masao (System Ya Masoo, a sole proprietorship in Maizuru, Japan)
The Discord community is coming soonPricing
FrameGleam hasn't been released yet, and pricing is still being decided. The plan: FrameGleam is open source, with free versioned releases. A free Discord community is also planned and is still being set up. Paid plans will add access to the in-development repository and members-only Discord channels. We'll announce the details on this page.
Open source
Free
MIT License
- Versioned releases (tar.gz)
- Modify and redistribute freely
- Join the Discord community (news, questions, sharing videos and extensions)
Standard
To be decided
An early-subscriber discount is planned
- Access to the private in-development repository
- Switch to any version
- Try new features first
- Standard-only Discord channel (early builds, bug reports)
Supporter
To be decided
For people who want a say in development
- Everything in Standard
- Supporter-only Discord channel to discuss requests and design with the author
- Weigh in on what gets built next
Payments will be handled by Polar (polar.sh), and you'll be able to cancel any time. The Discord questions channel will be a place for users to help each other; answers from the author won't be guaranteed. Replies in the Supporter channel will have no set response time.