Mux adds a dashboard playground for testing Robots video workflows

Mux has launched a playground in its dashboard for running its Mux Robots AI workflows against a customer's own video before any code is written. The company announced it in a blog post on October 1, 2026.

Robots are AI workflows that run against video. Mux says they can summarize an asset, pull out key moments, translate captions or moderate content, each with a single API call. Until now, Mux says, finding the best workflow for a piece of content meant running each through the API or dashboard jobs, tuning parameters and reading JSON output.

The playground, found in the dashboard under Robots, then Playground, lets a user pick an asset from a dropdown of recent ones or paste an asset ID. The user then chooses a workflow and sets its parameters and output steering. Mux says the results are rendered next to the video rather than as raw JSON: key moments appear as cards with transcript cues and optional thumbnails, and the transcript follows playback.

Mux says the tool is not a demo. Jobs run through the real Robots API, are kept in the jobs list for 30 days and use the same units as API-created jobs. A running total of units used in the session appears at the top of the page, in units and dollars.

What is new is the tuning loop. A Compare view shows two runs side by side with the parameters and steering behind each. Mux gives the example that a Find Key Moments job with a selection_strategy of product_moments can return very different results from one using story_beats. Mux also describes an Instant clips option for making a clip from a key moment, and a way to correct a mislabeled speaker in Premium Captions, with the corrected track replacing the old one on the asset.

For production use, each workflow card has a Copy agent prompt option. Mux says it copies instructions for a coding agent covering the endpoint, parameters, steering and webhook to handle, so the tuning session can serve as the specification.

What is confirmed and what is not: every detail above comes from Mux's own announcement. Guth News found no independent coverage of the playground and has not tested it, so how well the comparison and clipping features work is unverified. Per-workflow unit costs are published in a Mux guide that this article does not cite.

It matters because AI video workflows are sensitive to settings, and a way to compare runs before committing code could save developers time and unit spend. That benefit is Mux's claim, not an independently measured result.

Revised 16 October 2026: Guth re-read the original sources and rewrote this article. The earlier version remains available as revision 1.