Every editor has a folder that looks like this: promo_final.mp4, promo_final_v2.mp4, promo_final_v2_client-changes.mp4, promo_FINAL_real.mp4.
Nobody chose that system. It's what happens when versions have no home except the filename.
Code solved this decades ago. You branch, try something, compare, and go back if it was a bad idea. Video mostly didn't get the memo, so we built it into Arsaze and called it Timgit.
What Timgit is
Timgit is Git for timelines. Arsaze is an AI-native video editing OS from Sidhilynx, and Timgit is its versioning layer: you can branch an edit, keep every version, and never overwrite anything.
The important word is timelines. Git tracks files. Timgit tracks the edit itself, meaning which clips, in what order, cut where. A new branch is another arrangement of the same footage, so trying an idea doesn't cost you the version you already had.
Say the client approved the 60-second cut and now wants to see a punchier 30. You branch and cut the 30 there. The 60 stays untouched. If the 30 is worse, you drop the branch and nothing happened. If it's better, you compare the two and merge or roll back.
The other half of the problem
Versioning is only part of what makes client work painful. The rest is feedback.
Feedback usually arrives as a message. "At 0:42 the logo feels small." "Can we lose the breath before the last line?" Then someone scrubs to 0:42 and works out which thing was meant. Then you re-export, re-upload, send a new link, and the loop starts over, with round one's notes already buried in a different thread.
Remarker
Remarker is a shareable page that shows your versions from Timgit. Send the client a link. They open it, watch a version, and mark it up right on the video. Draw on the frame with a pen. Drop a comment on the exact moment. The same works on the audio waveform, so "the music is too loud here" points at a place instead of a paragraph.
There's no re-uploading and no re-linking. Feedback is pinned to a frame or a spot in the audio, so nobody translates a timecode someone typed into a chat.
Where the AI comes in
Because notes are attached to specific moments, an agent can read them and act on them. Remarker can apply fixes from client feedback automatically.
Timgit and Remarker sit on the same API and MCP surface as everything else in Arsaze. So an agent connected over MCP can branch an edit, read the review notes, and make the changes, with no human copying comments into a prompt.
The fix comes back as a version. You look at it next to the last one, then keep it or throw it out. The AI does the mechanical pass and you keep the decision.
Who this is for
Anyone who answers to a client. Agencies, freelancers, in-house teams with a stakeholder who always has one more note. The bigger the pile of revisions, the more it saves you.
What I'm not claiming
It won't tell you what the client meant. "Make it pop" is still "make it pop."
What it does is make the notes precise and the versions safe, which removes a surprising amount of the misery.
Try it
Cut a video, branch it, and send the link to someone with opinions. Let them draw on it. Then see whether that feedback is easier to act on than your last email thread.
Arsaze is live at
https://www.arsaze.com
"We wrote about the AI-first design behind Arsaze here: https://medium.com/@arshadazeezm/cursor-for-video-editing-what-changes-when-a-timeline-is-something-an-ai-can-read-baa039dc048e?sharedUserId=arshadazeezm"
Top comments (0)