Opus 5.5 writes perfect HyperFrames_ videos here's everything we learned so far from studying its model behavior

Figma for video editing doesn't exist for a reason. At my company, we're building a video editor for AI. But I've been eyeing this space for years. "Figma for X" has been a popular startup pitch since 2019. And serious founders have certainly tried, with millions in funding, to make it happen for video editing. But by 2026, it's obvious that there must be a reason why none of those startups survived. Here's what I uncovered: 1. The professional video space is fragmented. Unlike in design, today's post-production teams stitch together multiple highly specialised tools: - Premiere Pro for editing - DaVinci Resolve for color grading - Frame io for feedback and review - LucidLink for sharing footage No player has managed to build an all-in-one solution because video is REALLY, REALLY HARD. A Figma for video editing would need to be competitive in all these individual segments to win. But that's a technical challenge, and it can certainly be solved with enough talent. I believe there are stronger reasons. 2. It's a vitamin, not a painkiller. I'm sure plenty of video editors would consider real-time collaboration a cool feature. But is that need strong enough to make them switch from a trusted, robust editing tool to something experimental? Probably not. And that's not hard to imagine. Take software development: that space hasn't moved to real-time collaboration either, even though solutions exist. It just doesn't improve the development workflow enough. 3. A shared timeline is a shared bottleneck. Video editing decisions are tightly connected. One editor performs a ripple delete, and suddenly the clips another editor is working on shift underneath them. Editors need room to experiment independently without disrupting each other's work. A shared timeline doesn't solve that. But there is hope! At this point, it's painfully obvious: the next generation of NLEs will store edits in a codebase instead of a structured database. If the project is saved as code, video editors can suddenly use the same tools developers have spent decades refining, starting with Git. This opens up enormous possibilities for video editing: - Open-source video projects - Iterating in branches - Safely merging the work of multiple editors - Reusing code and video compositions I'm convinced this type of collaboration fits modern post-production far better and points to an exciting future for collaborative video editing.