OpenCut-app / OpenCut-app/OpenCut

RFC: local-first agent bridge and approval workflow

Open
#868 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
89.8k
Forks
8.9k
PR merge metrics
No merged PRs in 30d

Description

Hi OpenCut team — I noticed the README says the rewrite roadmap includes an Editor API, MCP server, headless mode, plugins, and scripting.

I drafted a small RFC around a local-first AI agent bridge and human approval workflow. It is documentation-only and intended as a design discussion, not a large implementation PR.

Branch/file:
https://github.com/Laksh-star/OpenCut/blob/codex/upstream-agent-bridge-rfc/rfcs/agent-bridge-rfc.md

The RFC covers:

  • structured edit-plan contracts
  • local-only media boundaries
  • review sessions
  • preview/final approval gates
  • preflight checks
  • how this could migrate toward OpenCut-native Editor API / MCP / headless rendering

I originally tried to open this as a draft PR, but the repository currently limits PR creation to collaborators. Happy to move this wherever you prefer — issue, discussion, Discord, or a maintainer-requested PR later. Feedback on whether this direction fits the rewrite architecture would be very useful.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading rfcs/agent-bridge-rfc.md from the linked branch, then compare its proposed direction with the README rewrite roadmap. Done means the RFC has received maintainer feedback on whether the agent bridge and approval workflow fit the planned Editor API, MCP, and headless architecture.

Written by the indexing model from the issue text.

Assessment

Domain
ai, api, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.