logo
Docs

Projects & Collaboration

OpenFork uses a GitHub-style version control system for video projects. Every project has a timeline of scenes, and you can branch, fork, and propose changes collaboratively — just like code repositories.

Projects & Timelines

A project is a collection of scenes arranged on a timeline. Each scene is a generated video clip, image, or audio track produced by one of the AI models.

The timeline is your primary editing surface. From here you can:

  • Drag and drop scenes to reorder them
  • Clone a scene or insert a new one between existing scenes
  • Edit scene details (prompt, model, duration) in the side panel
  • Play back the full sequence with synchronized audio
  • Generate new scenes directly using any supported AI model
  • Attach audio tracks: TTS, music, video-to-audio synthesis

Projects can be Public (visible and forkable by anyone) or Private (members only). Public projects can be edited inline by any logged-in user — OpenFork creates a temporary branch and draft pull request automatically.

Branches

Every project starts with a main branch. Additional branches let you explore alternative edits, try a different scene order, or experiment with models without touching the main timeline.

Branches work exactly like Git branches:

  • Create a branch from the Branches tab in the project header
  • Switch between branches at any time — each has its own independent timeline
  • A branch can have its own default model and style settings
  • Branches can be merged back via a pull request
  • The branch creator can manage their branch; project owners have full access
When a non-member edits a scene on a public project, OpenFork silently creates a temporary branch and a draft pull request. The original project is never modified until the owner accepts the PR.

Forking

Forking creates a fully independent copy of any public project under your own account. You can change anything — add scenes, swap models, remix the entire timeline — without affecting the original.

  • Forks are instant — scene storage is shared, not duplicated
  • New generations you make in your fork create new files only
  • Your fork is a completely separate project with its own branches and settings
  • You can fork a project or a specific branch

To fork: open any public project → click Fork. The copy appears in your dashboard immediately.

Pull Requests

A pull request (PR) is a proposal to merge changes from one branch into another — your feature branch into main, or a fork back into the original project.

The PR diff view shows a side-by-side timeline comparison: scenes added, removed, or reordered are clearly highlighted. Project owners can review and accept or reject the proposal.

Open

Awaiting review

Merged

Changes accepted

Closed

Declined or withdrawn

Scene-level comments and votes are supported on any scene in a PR or the main timeline.

Scripts

The Scripts tab stores the narrative script or shot list for a project alongside the timeline. Scripts help keep story intent visible while editing scenes — useful for multi-collaborator projects where context can get lost.

A project can have multiple script versions, one per branch.

History

The History tab shows a full audit log of all changes to a project: scene additions, deletions, reorders, and branch merges. You can browse the full evolution of any project over time.

Access Control

RoleReadEditPropose Changes
Anyone (public project)✓ (auto-PR)
Collaborator
Owner / Creator
Anyone (private project)