AetherCutChangelogHow it worksPricingOpen the editor

Home / Changelog / v1.7.81

v1.7.81

Review links un-ghosted — public count now 72 tools

AetherCut v1.7.81 shipped on May 22, 2026.

What's new in v1.7.81?

  • Removed review from the ghost-tool registry. The Mongo-backed /api/review/* endpoints (create / get / comment / resolve / status) plus the 5-second-poll cross-device frontend hook have been live since v1.7.46 — the ghost flag was just stale bookkeeping.
  • Bumped TOOLS_PRO 53 → 54 (TOOLS_TOTAL 71 → 72). AI_PRO unchanged at 28 — review is a non-AI Pro tool.
  • End-to-end smoke test passed: create thread, post timecoded comment, toggle resolve, set status approved, cross-device GET, delete comment, _id strip verified.
  • Zero ghost tools remain. The marketing surface and the live editor are now fully in sync.

How to use review now that it counts as a live tool

If you have not touched the review flow since earlier builds, the practical change is not that the feature suddenly appeared in the editor, but that you can now treat it as part of the official tool surface without second-guessing whether it is still “internal.” In day-to-day use, that matters most for teams who review cuts across devices. A simple pattern is to create a review thread on desktop while trimming or timing, then open the same project on a phone or second laptop to verify that comments, resolved state, and approval status stay aligned without manual refresh habits. Because the frontend hook is already polling in the background, the useful habit is to leave one device in playback and use the other as the comment station. That setup makes timecoded feedback much easier when one person is focused on the cut and another is focused on notes.

A concrete example: imagine a short product demo with three spots that need sign-off. On the first pass, you create a thread as soon as the cut is stable enough to share. While watching from the start, drop a comment at the moment the title card feels too fast, then add another where a B-roll transition lands late against the voiceover. If the opener is fixed right away, resolve that item instead of deleting it, because resolution preserves the trail of what changed. Later, when the second note turns out to be caused by a different trim upstream, you can leave the original comment in place, recheck the timing after the trim, and only then decide whether to resolve it. Once the video is clean, set the overall review status to approved so anyone reopening the project sees the state immediately rather than inferring it from a half-empty thread.

The main mistake to avoid is using comments and status as if they mean the same thing. A project can have resolved comments and still not be approved, or it can be approved while a small non-blocking thread remains open for follow-up. Keeping those signals separate prevents confusion when multiple people are involved. Another easy misstep is deleting comments too aggressively. Delete is best for accidental posts, duplicates, or comments attached to the wrong moment. If the note was real and prompted a change, resolve it instead. That keeps the thread readable and avoids the familiar “what changed here?” problem that shows up when feedback disappears with no trace. It also helps when someone joins later and needs to understand why a cut now looks different from the first pass.

There is also a small operational detail hidden in the smoke test notes that is worth understanding: _id stripping means the API responses are shaped for the app’s review experience rather than exposing raw database internals. For most users that simply translates to cleaner payloads and fewer odd edge cases when comments move between create, get, and cross-device refresh cycles. In practice, getting started is straightforward: open a project that is ready for feedback, create a review thread before you invite anyone into nitpicking mode, write comments that describe the issue and the intended outcome, and use resolve and status changes deliberately instead of as rough substitutes for one another. Now that the count and the actual editor behavior are aligned, review can be used like any other supported Pro tool: not as a hidden extra, but as the normal way to turn “looks good to me” into something visible, timecoded, and shared.

How do I get this update?

Open the editor and you have it. AetherCut runs in Chrome, Edge, Safari and Firefox. There is nothing to install, and you can edit without an account. Open the editor or see how it works.

What shipped just before and after?

See all 111 releases · Follow the RSS feed