Launching today
OpenChatCut
Open-source AI agent video editor with a real timeline
137 followers
Open-source AI agent video editor with a real timeline
137 followers
OpenChatCut is an open-source ChatCut alternative: local-first AI video editing where Codex, Claude, and MCP agents work on a real multitrack timeline. Free, editable exports, AGPL.
OpenChatCut
@etiennegarcia Exactly — the goal is to keep AI-generated work editable rather than turning it into a dead-end export. You should always be able to refine, rearrange, or undo what the agent did. Thanks so much for the support!
finally something that doesn't lock my edits behind a paywall or a cloud upload, the local-first setup with claude actually tweaking the timeline felt surprisingly natural and the agpl license is a huge plus.
OpenChatCut
@saliha489828 That’s exactly what we hoped the experience would feel like: your project stays local and under your control, while the cloud helps with the heavy lifting. Really glad the workflow felt natural to you — and thank you for appreciating the AGPL choice!
finally an editor that doesn't fight me on the timeline, and the local-first angle means i can actually trust it with rough cuts. genuinely impressed it stays free under AGPL.
OpenChatCut
@nuraypzdp Really appreciate that, Nuray. Making the timeline feel predictable and trustworthy is exactly what we wanted. And yes, staying open and free under AGPL is an important part of the project.
The part I'd poke at is how the agent addresses clips through MCP. Every time we've handed an agent a stateful document as tools, state drift is the thing that bites: it reasons over a snapshot it read a couple calls back, so 'trim the third clip to 5s' hits the wrong clip once the timeline moved underneath it. Are the edits keyed to stable clip IDs it can re-reference, or to positions and timecodes that shift when tracks change?
The 'edits proposed for review before applied' loop on a real timeline is what makes this feel usable rather than a black box. When an external agent works over MCP (say Claude Code), does it get the full timeline state as context each turn or just a diff of the current edit, and where do those proposed-but-unaccepted edits live — in the project file on disk I could version in git, or app-internal state until I accept? I'm trying to gauge whether the whole editing history stays reproducible outside the app.
The "real multitrack timeline" part is what makes this stand out to me — most AI video tools spit out a black-box render you can't touch, so having the agent edit an actual editable timeline (and local-first) is a much saner workflow. Love that it's AGPL too.
Quick question: since it works with Claude/Codex/MCP agents — do I bring my own API key/model, or is there a local-model option for people who want it fully offline?
i cut short product demos for social every week and the timeline is always where ai tools fall apart. they generate clips but you can't nudge anything after. agents on a real multitrack timeline over mcp is the missing piece. can claude code drive it today or do i need your chat ui?