Postwright Release Note: Clips That Finish

The shorts pipeline was shipping clips that cut off before the point. Every short is now read against its transcript and dropped if it doesn't land.

2 min readBy Matthew Stublefield
White and black typewriter on green grass

A thirteen-second clip went out with my face on it. In it I explain what the video isn't about, build toward "so let me tell you why," and then it ends. No why. All setup, no delivery, and Postwright had picked that clip, rendered it, and scheduled it with nothing standing in the way.

That's the failure mode of automated clipping. One long video yields a dozen or more candidate shorts, and the ones that look good as timestamps aren't always the ones that land in thirty seconds. This release puts a second pass between picking a clip and rendering it.

What changed

  • Clips get screened before they render. Every proposed short is now read against the actual transcript inside its window – the words a viewer would really hear, not the title or the hook line – and dropped if it doesn't deliver something. Survivors snap to real sentence boundaries, so a clip opens and closes on a complete thought instead of mid-breath. If everything gets rejected the video stops and waits for you rather than quietly producing nothing. It's new, so I'll know more after a few more videos, and the strictness is a setting if it's wrong for your material.
  • The shorts pipeline's three Claude skills now ship with it. They were always required and never bundled, so the packaged version couldn't run the pipeline at all. The installer only writes files you don't already have, so your own edits win.
  • An unconfirmed LinkedIn post stops instead of retrying. The same video went to my feed four times in one hour, because a confirmation wait far too short for video made a live post look failed. Now nothing retries after the Post click. This shipped in the packaged release, so if you send video to LinkedIn through Postwright, it's the one to update today.
  • An optional deploy hook per site. A webhook stopped firing with no error anywhere, so pages never went live and Postwright correctly refused to email links to pages that didn't exist. It still waits for your normal deploy, and fires the hook only if that wait times out.

I build these to run a one-person firm and then ship the ones worth shipping, so every fix here exists because the bug got me first, in public, on my own accounts.

Postwright lives at postwright.app if you want it.

Own your publishing stack.

Postwright is a local-first authoring and publishing platform – write markdown on your own machine and publish to your blog, newsletter, and social channels with your own API keys.

Get Postwright