MarketOS v2.4.1: video downloads, carousel review, and rebuilt desktop packages
The latest MarketOS desktop package turns generated video output into something you can review, compare, save, and ship. Multiple clips now behave like first-class assets instead of a pile of links.
The first video release proved the core pipeline: send a prompt to a video-capable provider, wait for the job to complete, and render the returned clip in the MarketOS result panel. v2.4.1 is the follow-through release. It focuses on the part that matters once the model finishes: what happens to the videos in your hands.
TL;DR. v2.4.1 adds a video carousel for multi-output results, clearer current-video downloads, a desktop save-all action for video batches, fullscreen review, keyboard navigation, and rebuilt macOS/Windows release packages.
Why this release matters
AI video is rarely a single perfect output. A useful prompt often returns several candidates: one with stronger pacing, one with a better opening frame, one with cleaner product movement, one that fits the ad concept but needs a caption pass. The interface has to support comparison, not just playback.
That is what changed. MarketOS now treats multi-video output the way a marketer expects to work with it: one focused preview at a time, fast navigation across variants, direct save actions, and enough context to know which clip you are looking at.
Multi-video carousel
When a provider returns more than one video, the result panel becomes a carousel with previous/next controls, dots, and a visible current item count.
Current-video download
The primary save action follows the active clip, so you download the exact video you just reviewed instead of guessing from a list of URLs.
Save all on desktop
Desktop users can save every returned clip from a batch. Mobile keeps the safer single-video flow to avoid browser popup blocking.
Fullscreen review
Videos can be opened into a larger preview when you need to inspect motion, framing, text legibility, or end-card behavior.
Downloads are now built for real provider URLs
Generated videos often come back as remote HTTP(S) URLs. Some providers return signed URLs, some return content endpoints, and some return direct files. The new downloader handles that reality more gracefully.
When the browser allows it, MarketOS resolves the remote video into a blob download so the file saves cleanly. When the remote host blocks that path through CORS or signed-link behavior, MarketOS falls back to opening the video URL directly. That keeps the save action useful without hiding provider constraints behind a broken button.
On mobile, MarketOS uses the current-video path rather than firing multiple downloads at once. That is intentional. Mobile browsers are aggressive about popup and background-download blocking, so the reliable behavior is to open the selected video and let the user save it from the native share/download flow.
The desktop package was rebuilt
The download package now points at the v2.4.1 production release. That includes current macOS and Windows artifacts, plus the updater metadata files used by the desktop app.
| Platform | Package | Use case |
|---|---|---|
| macOS Apple Silicon | MarketOS-2.4.1-arm64.dmg | M-series Macs. |
| macOS Intel | MarketOS-2.4.1-x64.dmg | Intel Macs and compatibility installs. |
| Windows | MarketOS-Setup-2.4.1.exe | Windows desktop installs and updates. |
| Updater metadata | latest.yml, latest-mac.yml | Desktop update discovery. |
Nothing about this changes the BYOK model. The release package is the app shell and orchestration layer. Your video provider keys, prompts, and generated assets are still controlled by your provider setup and your local workspace.
What this unlocks in day-to-day use
The practical win is speed. You can generate a batch of videos, scrub through the set, fullscreen the strongest clip, save just that one, or keep the whole batch for later review. That fits the actual creative workflow better than forcing every output into a one-off result card.
- Ad variation review: compare several hooks or scene treatments without leaving the result panel.
- Client handoff: save the whole set on desktop and send a clean folder of options.
- Mobile inspection: open the selected clip and save through the native browser controls.
- Prompt iteration: keep track of which candidate is worth regenerating from, instead of losing context after the provider returns multiple URLs.
Production checks before release
This release shipped after the video carousel and downloader were covered by focused component and service tests, followed by a full app test run and production build. The release workflow also rebuilt the platform packages and published the current installer assets.
For users, that means the new behavior is not a prototype sitting behind a dev flag. It is in the desktop package, wired through the same result panel that already handles images and other generated media.
Next read: for the provider side of the workflow, read BYOK video generation in MarketOS. It explains how OpenRouter, Gemini/Veo, async jobs, and multi-output video assets fit together.
How to get it
Download the current MarketOS desktop package from the product site, or update from the app if your install is already configured for desktop updates. The version to look for is v2.4.1.
If you generate video regularly, this is the update to install. The model does the generation, but the app now gives you a cleaner way to manage the results once they exist.