Msty Studio 2.7.0 introduces Media Studio, a major Turnstiles vNext upgrade, and an Enterprise Desktop version.
I was waiting for this one.
Yesterday was Msty Claw 0.4.0. Today is Studio 2.7.0. The team has been in one of those weeks where Slack is mostly build links, bug screenshots, and “can someone try this on Windows?” messages. Not a bad week.
Since 2.6.0, a lot of Studio work has been the unglamorous kind: stability, cleanup, bug fixes, and sanding down rough edges that only show up after you use something every day. 2.7.0 has some of that too, but it also has two things I have been impatient to get into people’s hands.
Quick version:
- Media Studio for image and video generation inside Msty Studio
- Turnstiles vNext with loops, checkpoints, conditions, and a refreshed builder
- Enterprise Desktop for enterprise customers
- Context Message Limit restored from 1.x
- New media model support, including GPT-Image-2, xAI image/video, and select Ollama-compatible local image models
Media Studio
Adam built Media Studio end to end, which is my favorite sentence in this post.
He doesn’t come from a traditional programming background. He had the idea, kept pushing through the ugly middle, and shipped the feature. I’m mentioning that up front because it says more about the current AI tooling moment than most benchmark charts do. The tools help, sure. But the useful part is still taste, stubbornness, and being annoyed enough by a missing workflow to build it.
Media Studio is for the part of media generation that gets messy after the first prompt.
A single prompt box would have been too thin here. In real use, you make one image, notice the weird bit, mark it up, try again, compare versions, maybe turn the best one into a video, then lose track of which output came from which attempt. The feature is built around that loop:
- use image and video models already configured in Studio
- start from a base image, document, or PDF
- crop or annotate a frame before asking for a change
- compare before and after
- turn an image into a video
- keep generated media in the Attachment Manager
The demo example is goofy in the right way: generate an image, draw an arrow on it, ask the model to add a cow at the end of the arrow, compare the before and after, then animate the result.
I like demos like that because the silliness exposes the workflow. A perfect prompt demo can hide all the product problems. A cow-at-the-arrow demo has no dignity to protect. You can see whether the app lets you keep moving.
Turnstiles vNext
I worked on the other big feature: Turnstiles vNext.
Turnstiles started as repeatable message sequences. Useful, but mostly linear. With 2.7.0 they can turn around, wait, and choose a path instead of marching through a fixed script:
- loops
- checkpoints
- conditions
- a refreshed flow builder
I’ve been joking internally that Turnstiles are Turing complete now. I should probably stop saying that before someone asks me to prove it.
The less dumb version: loops and checkpoints let a Turnstile stop being only a saved sequence. You can use it for retries, staged review, branching prompts, and repeated refinement without babysitting every step.
For example, a writing workflow can draft, critique, revise, and pause for approval at a checkpoint. A research workflow can collect sources, reject weak ones, loop until it has enough, then move into synthesis. A support workflow can classify the issue, ask for missing details, and only escalate after a few attempts fail.
I wanted Turnstiles to feel less like a macro and more like a little workbench inside the conversation. A separate automation product bolted onto chat would miss the point.
The small fixes are not small
The boring part of the changelog is also worth reading. I know, thrilling sentence. But this is the stuff that decides whether a feature survives contact with daily use.
2.7.0 cleans up:
- missing Command Palette features
- Knowledge Stacks compose performance
- Watch mode detecting changes made while Studio was closed
- attachment ordering
- Split Chat persona, turnstile, and shadow persistence
- Vibe CLI Proxy duplicate provider issues
- enterprise session and sharing flows
- clearer remote tunneling errors
None of those will get a dramatic launch video. They do make the app feel less haunted when you are trying to get work done.
If I strip out the release-note language, 2.7.0 is about fewer dead ends.
Media Studio gives generated media somewhere to keep evolving. Turnstiles give a workflow somewhere to loop, pause, and continue. Attachment Manager, Split Chat, Knowledge Stacks, and the rest of the cleanup remove a bunch of papercuts I am happy to never think about again.
Enough for me. Not every release note needs to pretend it changed computing. Some releases just save you clicks, preserve your state, and make the next step obvious. For a desktop app, that is most of the game.
Full notes here: Msty Studio changelog.