Early access · Internal beta Unsigned CEP build

Social Cut Commander

Three Premiere Pro 2026+ CEP panels that read your active sequence and turn it into a project-aware review-marker plan — editorial beats, a deliberate creative-effects pass, and a read-only sequence audit. It never touches your clips, media, or effects. It only writes markers, and only the ones it owns.

Request early access No purchase flow — this build isn't signed or sellable yet.

What "early access" means here

This is an honest status, not a marketing label:

Publisher: Trident Social · Bundle ID: com.tridentsocial.socialcutcommander · Version 0.3.0

The three panels

All three read the active sequence for context. None of them apply an effect, cut a clip, or touch media automatically.

Cut Blueprint

Editorial review markers

Reads the active sequence name, track layout, and playhead, then builds a marker blueprint for narrative, interview, event, montage, or cinematic structure — story beat, key claim, peak moment, and so on.

Creative Pass Builder

Effects review cues

Builds a deliberate cue pass for motion, transitions, sound design, graphics, color, and finish. It flags where to make a creative decision — it never applies one for you.

Edit Sentinel

Read-only sequence audit

Reports track, clip, marker, and owned-review-cue coverage on the active sequence. It has no marker-write or clear capability at all — audit only.

Local Pacing Review

Optional silence detection

Runs local ffmpeg silence analysis against a media file you pick yourself, then proposes pacing-review markers. Nothing is uploaded — it never leaves your machine.

Headless verification we actually ran

Everything on this page that's checked is checked by an automated script you can run yourself — npm test and node scripts/validate.cjs inside social-cut-commander/.

13/13
unit tests passing
Marker-plan builders, the CEP↔ExtendScript host bridge, sequence auditing, and ffmpeg silence-output parsing — all tested in isolation with a stubbed Premiere host.
11
required files present
Manifest, all three panel HTML files, styles, and every JS/JSX module are confirmed to exist and pass Node's own --check syntax validation.
manifest well-formed & consistent
CSXS/manifest.xml parses as valid XML, targets Premiere Pro 2026+ (CSXS 12), and its bundle ID/name match this page and the README exactly.
no AE automation, owns its markers
The host script is scanned to confirm it never calls into After Effects and that every marker it writes carries the [EIS] ownership prefix.

What this does not prove

None of the checks above open Premiere Pro. We have not confirmed the panels render correctly, that the ExtendScript host bridge actually talks to a live Premiere session, or that markers get written to a real sequence. That proof requires a clean-machine install and a manual pass inside Premiere — which hasn't happened yet. If you request access and try it, what you find is genuinely useful signal for us.

Product boundary

Premiere Pro CEP only — no After Effects automation, no other host apps.
No network calls, cloud analysis, credentials, or telemetry. Everything runs locally.
Effects are never auto-applied. The suite creates reversible, project-scoped review markers only.
Cleanup removes only its own [EIS]-prefixed markers (plus legacy [SCC] markers from earlier internal builds) — your other markers are never touched.

Requirements for early-access testers

RequirementDetail
Host appAdobe Premiere Pro 2026 or later (CSXS 12 runtime)
OSmacOS (install script targets ~/Library/Application Support/Adobe/CEP/extensions/)
Debug modeUnsigned extension — requires defaults write com.adobe.CSXS.12 PlayerDebugMode 1
Local media analysisOptional — Local Pacing Review needs ffmpeg on your PATH

Want to try it before anyone else?

Tell us your Premiere version, OS, and what you cut. We'll send the install steps and want your honest notes back — that's what early access is for.

Request early access