Native Mac editor · Agent-ready by design
Direct the edit. Approve every change.
Plan transcript cuts, B-roll, layouts, and durable timeline markers with an agent. Review the exact proposal in the same local Mac editor before anything changes.
Local projects · Human approval · Bring your own agent
From cleanup queue to directed edit
Stop handing meaning-changing edits to a black box.
Repetitive cleanup should be automated. Editorial judgment should remain visible, named, and reversible.
PilotCut proposes. You approve. The timeline becomes the durable record.
The usual AI pass
- A prompt disappears into chat
- Changes execute before review
- Intent vanishes when the session ends
The approval loop
Review the edit like a code change, not a magic trick.
A ranged marker anchors the request to footage. The proposal names each operation, previews the timeline delta, and leaves a readable receipt after commit.
Human marker · 02:10–02:45
Tighten the explanation. Keep the pricing example. Add a short product close-up.
Proposed operations
- 1Remove 3 filler spans · 4.8 s
- 2Close dead-air gap · 1.6 s
- 3Create B-roll slot · 8.0 s
Confidence 0.94 · expected revision 128
Before · 00:35.0
After · 00:28.6
Committed after human approval
History receipt · 3 named operations · marker resolved
Frame peek verified at 02:18, 02:27, and 02:39
Local, deterministic, open
The editor is the runtime. Your agent is the planner.
PilotCut exposes the same project state and editing primitives to the native interface and compatible command-line agents. There is no second hidden timeline.
Provider note: prompts, transcript text, and any rendered frames you ask an agent to inspect follow the provider you choose. Raw footage and project files stay local unless you explicitly use a separate upload or sharing feature.
Markers outlive the conversation
Timeline markers preserve what should change, who requested it, and whether it was resolved—even after the chat session is gone.
Bring the agent you already use
Work through Claude Code, Codex, Gemini CLI, or another compatible CLI. Use your own provider relationship instead of a mandatory PilotCut credit balance.
Three-step workflow
Direct, inspect, commit.
The workflow separates intent, review, and execution so speed does not require blind trust.
- 01
Mark or describe the intent
Pin a ranged marker to footage or describe the outcome in your agent.
- 02
Review the proposal
Inspect named operations, timing deltas, confidence, and the affected region.
- 03
Commit and verify
Approve the mutation, read the history receipt, and inspect rendered frames.
Shipped mechanics
A real editing runtime, not a scripted demo.
The current product already exposes approval gates, durable project state, practical editing operations, and local agent access.
Safe mutation
Proposal and commit gates, dry runs, expected-revision checks, and coordinated mutations.
Inspect and verify
Timeline markers, a 250-entry readable history, and rendered frame-peek verification.
Creator-video operations
Transcript cuts, silence cleanup, B-roll lifecycle, and scene-layout tools.
Local agent access
A 40+ tool MCP surface plus CLI access to the live native editor or headless projects.
Tool counts change. The durable claim is that the native UI, CLI, and agents operate the same project model.
Buyer research
Choose the workflow, not the category label.
Three focused guides for comparing local-first agent editing with phone-first and professional NLE workflows.
Questions before download
Clear boundaries build trust.
What stays local, what agents can change, how approval works, and what current beta access means.
Does PilotCut keep my footage local?
Yes. Footage and PilotCut project bundles stay on your Mac. If you use an external agent provider, prompts, transcript text, and any rendered frames you ask it to inspect follow that provider; raw footage and project files are not uploaded for editing.
Can I approve edits before they change the timeline?
Yes. Agent mutations can run as proposals or dry runs first. You can inspect the named operations, approve them, adjust the request, or reject the proposal before commit.
Which agents can work with PilotCut?
PilotCut supports bring-your-own-agent workflows through Claude Code, Codex, Gemini CLI, and other compatible command-line agents that can use its local MCP and CLI surface.
Do I need to buy PilotCut AI credits?
No. Bring-your-own-agent editing uses your own agent and model subscription, so PilotCut does not add a mandatory credit meter to that workflow.
Can I see what an agent changed and undo it?
Yes. Named edit operations are recorded in project history, and timeline markers preserve the intent behind the work. You can review the receipt and use the editor's history controls to reverse changes.
What can agents edit today?
Current tools cover transcript cuts, silence and dead-air cleanup, markers, B-roll proposals and acceptance, scene layouts, project inspection, history, and rendered-frame verification. The changelog tracks the current surface.
Is PilotCut free?
Current macOS beta access is free. That describes the beta available today, not a permanent pricing promise. Download the app to use the current release.
Who is PilotCut built for?
PilotCut is for creators of tutorials, courses, product demos, and long-form talking-head, screen, and B-roll videos who want tedious first-pass work handled without giving up editorial control.