Share a Cut with Your Client Without Exporting

Gnarles here. Let's talk about the worst part of the job.

It's not the cutting. It's the part where the cut is good enough to show somebody and you have to figure out how to put it in front of them.

You used to export a watermarked MP4. Three minutes of render. Drop in Dropbox. Paste a link in Slack. Wait for them to open it on the bad couch laptop with the buzzing speaker. Then they message back: "yeah looks great except the part around like 1:34?"

Around 1:34. Around. Around.

You scrub to 1:34. To 1:33. To 1:36. Nothing wrong at any of those. You ask: "what specifically?" Forty minutes later: "oh sorry I meant 1:24 lol." You scrub to 1:24, see the cut, fix it in twelve seconds, re-render, re-upload, re-paste, wait.

We built a button for this. The cut never left the app. The render never ran. The "around 1:34" never happened.

"Look at 1:34" failed because the timecode was the only thing the medium could carry.

What you actually wanted to send was a frame, the clip that frame belonged to, the timeline state — playhead, selection, panel — and the thought you had when you paused. You wanted your client to receive that in the same room you were standing in.

Email couldn't carry the room. Slack couldn't either. Loom carried a video of the room, but the room wasn't openable. Frame.io carried the room — and charged a per-seat tax to do it, and lived outside the editor.

We had a different idea. The room was already the editor. Your client was already a row in the database, because you'd already added them to give notes. The deep link from the editor to itself already existed for the universal app to bounce between phone and Vision Pro. We just had to wire those three facts together.

The share dialog was that wiring.

Press the share button and you got a dialog called Share this view. At the top: a preview card with the current frame's thumbnail, a magenta badge with the timecode, a cyan badge with the selected clip's name, and one short line of the AI-generated description for that part of the footage. Share this cut with a teammate

That preview wasn't decoration. It was the receipt — the system telling you what was going in the envelope.

What actually went in the envelope, captured live the moment you pressed share:

• The project ID and title.
• The playback time to three decimals.
• The selected clip ID, every clip ID in your current selection, plus the selected video and track.
• The chat tab you had open — AI or shared — and the timeline thread or edit artifact you were attached to.
• The right panel state — which tab, open or closed.
• The chat panel state — collapsed, fullscreen, pixel height.
• The timeline zoom, the in point, the out point.
• A preview bundle — project title, clip title, thumbnail URL, AI-generated frame description.

The preview bundle was the part that turned a deep link into a message. Your recipient didn't have to log in to see what you wanted them to look at. The thumbnail and description rode along inside the email and chat card.

The default note in the textbox was "Please take a look at this part of the edit." You usually overwrote it. One sentence. "Hold on the laugh a half second longer?" The system carried the rest.

Below the note: two checkboxes, both on by default. Push now fired a notification at every device they were signed in on. Email if unopened after 5 minutes held an email in the queue and only sent it if they hadn't clicked the push. One nudge, not three.

Below those: a recipient list — every collaborator on the project, with avatar and email. Click one. Click three. Click Everyone. Leave it empty and the default was everybody but you, which was right for "team, look at this."

Press Share. Dialog closed. Deep link on your clipboard before the toast finished. The shared chat had a new card. Their phone buzzed. The email was scheduled. You went back to cutting.

::

If they didn't pick up the push within five minutes, the email landed.

The "from" line read Gnarles from VibeChopper. Not a no-reply. A person, a coach, who showed up only when something needed looking at. The subject line was your name, the verb, the project: "Marisol mentioned you in Wedding — Bayfront Hotel."

The email was themed in the same palette as the editor — magenta accent, cyan rim, VHS-black background, chrome panels. When your client opened it, the room they walked into already looked like the room you wanted them to walk into next.

Inside the email, in order: an eyebrow reading "VibeChopper collaboration," a title — "Marisol shared a view with you," your note, the thumbnail, a panel titled What they are looking at with the AI-generated description, a single button reading Open the exact view, a metadata footer with project name and recipient name, and a closing line that read: "This link opens the project, timeline position, selected clip, and shared chat context inside VibeChopper."

That closing line was a contract. They knew before they clicked exactly what was about to happen. They weren't going to land on a generic dashboard. They were going to land where you stood when you wrote the note.

If the universal app was installed on whatever device they opened the email on — iPhone, iPad, Mac, Vision Pro — the link bounced them straight in. If not, they landed in the browser editor and the same restoration code ran. Same room. Same time. Same selected clip.

One template engine rendered every email VibeChopper ever sent you — sign-in codes, export-complete pings, share notifications, daily DATA Remediation reports — sharing one HTML shell and one text shell. The visual language was the same across every inbox arrival, so when one landed, you already knew it was the app. The build notes are in the themed email templates dev post.

The share didn't end at the email. The share opened a thread. Open the share dialog

Every share posted a card to the project's shared chat — a second chat tab in the editor, sitting next to the AI chat. The shared chat wasn't a list of system notifications. It was a real thread. Avatars, names, reply buttons. Every message lived inside the project, attached to view contexts, rendered in the same synthwave skin as the rest.

A share card looked like a regular message with an extra panel underneath. Thumbnail, timecode badge, clip name, one-line description, an Open view button. Hit the button and you opened the project at the same view the sender was on. A hundred shares stacked across a long project meant scrolling the thread and walking through them one at a time.

Replies were where the air went out of the "look at 1:34" loop. Your client opened the email, clicked Open the exact view, landed on the frame, switched to the shared chat tab, and typed back: "Yes. Hold the laugh longer. Maybe try a 0.4 second extend?" Their reply lived under your share card. You didn't have to copy a timecode anywhere. You didn't have to ask "what did you mean by 1:34." You jumped to the same view, made the change, maybe shared that view back at them.

One small detail: when you opened a share from a push or email, the message you clicked got highlighted in the thread with a soft cyan ring for the first second. After the fourth share in a long project, that highlight was the difference between "where was the note we were talking about" and "oh, there."

::

Run a full one. Wedding shoot. Thirty-second highlight reel almost cut. The bride's mom is the client. You want her opinion on a held shot of a laugh.

You scrub to 1:34. The wide shot of the laugh fills the player. You select the clip. The right panel is on Properties. The AI chat is collapsed.

You press share. The dialog opens. The preview shows the thumbnail, a magenta 1:34 badge, a cyan badge reading Wide shot — laughter, and the AI's description from when you uploaded the shoot two weeks ago: "Wide shot — bride and her father laughing during the first dance, ballroom lighting."

You click only the bride's mom in the recipient list. You leave both notification checkboxes on. You type: "Hold the laugh longer here? Currently 1.2 seconds — I can stretch to 1.8. Want me to?" You press Share.

The dialog closes. The toast confirms: "Posted to shared chat, pushed now, and email is scheduled if they do not open it." Your clipboard has the deep link in it.

The bride's mom is at brunch. Her phone buzzes. The push reads: "Marisol mentioned you in Wedding — Bayfront Hotel." She taps it. The universal app opens on her phone. The editor loads at 1:34, the wide shot selected, your note already in the shared chat tab. She watches it three times. She types back: "Longer. 1.8. Yes."

Your phone buzzes. You see the reply without leaving the project. You pull the clip's out-point right by 0.6 seconds. You scrub. The laugh holds.

You don't render. You don't export. You press share again. The new preview already reflects the edit. "Like this?" Send. The bride's mom watches. "Yes. Perfect. Thank you." Four minutes since the first share — her email never sent because the push got opened in time.

Three exchanges. Zero exports. Zero "around 1:34." The cut moved. The client felt heard. You shut the laptop.

Two things to be straight about.

One: this only worked with people already shared on the project. The recipient list was the project's collaborator list. To add someone new, you added them as a collaborator first. Public review links live in a different threat model than collaborator notes — we didn't want a forwarded email leading to an open URL anyone could land on. The share carried weight because the recipient was named, signed in, and accountable. If you needed to see why an AI move happened on a share, the tool-trace cards lived in the same project view your collaborator landed on.

Two: it didn't replace the final delivery. If your client said "yes, ship it," you still had to hand them an MP4 they could put on Instagram. That's what Export was for — MP4, MOV, WebM, FCPXML, EDL.

The share dialog ate the review cycle — the round-and-round of "look at 1:34, no I meant 1:24." That's the cycle that turned a one-day project into a one-week project. Export happened once, at the end, when everyone agreed. The middle of the project — the thinking — happened in the room. Same room. Same playhead.

An export is a snapshot. You burn one in, you ship it, and the moment your client comes back with a note, that snapshot is stale. So you re-render. So it's stale again twelve minutes later. Every cycle is a small expensive lie about where the cut actually is.

A deep link is the opposite. It's a pointer. Whatever you do to the timeline between sending and opening, they see the latest. If they bookmarked the share email and clicked three days later, they'd land on the current project, not a frozen render. The pointer survived your edits.

The small shift: editing software for twenty years treated the export as the product. It wasn't. The export was the receipt. The product was always the thinking — "hold the laugh longer," "swap that B-roll," "this needs to breathe." The share dialog put the thinking inside the room where the cut actually lived.

Your client's note arrived attached to the frame it was about. Your reply landed on the same frame. The frame, meanwhile, kept being part of a live project. Notes and cut were the same artifact, not two artifacts you had to keep syncing.

Burnout's not a character flaw. It's a tool problem. One of the heaviest tools in the pile was the export-and-link review cycle. We took it out of the box.

Next rep: open a project, scrub to a moment you're not sure about, press share, type one sentence, send it to one person, put the laptop down for the afternoon. Let the room do the carrying. Sleep when the reply comes back.

See you on the timeline.

— Gnarles