Hand the Mux assets to a companion
Your Mux, worked while you do something else: 2 reads to go through it, 2 writes to change it, and a card in front of every one of those changes.
Open the asset. Check it against something else. Write the change. Move to the next one. That is the Mux afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a asset until you approve it.
What it can do is exactly what Mux exposes to an account you authorise and nothing beyond it: 4 operations, 2 reads and 2 writes. In practice that means it can create an asset and create an asset track, and work across the assets, asset or livestream ids and asset tracks.
The Mux API stops at Mux. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the assets or ask you for them?
2 of the 4 operations are reads.
Your account, not a guess at it: a companion can get an asset and get asset or livestream ID, and the full list below is the whole list, with nothing inferred from Mux's documentation.
The assets are what most of this inventory is about, alongside the asset or livestream ids. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Mux admin becomes a queue you review.
- Get Asset
- Get Asset or Livestream ID
What happens before it can create asset?
All 2 write operations wait for you.
A companion can create an asset and create an asset track, and each one is staged on an approval card first: you see the asset, the field and the new value before it lands in Mux.
Nothing in Mux is sent, changed or deleted on your behalf without that click, and a rejected card leaves the asset exactly as it was. The gate is the same one on every surface, described at security.
- Create Asset
- Create Asset Track
Does the asset sweep have to be asked for every time?
Yes.
Saved as a routine, the Mux assets pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the busywork, the Mux assets sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents