Hand the Frame.io assets to a companion
Hand a companion the outcome. It reads the Frame.io assets, does the 4-operation version of the job, and stops for your click on anything that changes a record.
Open the asset. Check it against something else. Write the change. Move to the next one. That is the Frame.io 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 Frame.io exposes to an account you authorise and nothing beyond it: 4 operations, 1 read and 3 writes. In practice that means it can create a project, create a comment and create an asset, and work across the assets, comments and projects.
The Frame.io API stops at Frame.io. 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.
Where do the assets come from?
1 of the 4 operations is a read.
Your account, not a guess at it: a companion can search assets, and the full list below is the whole list, with nothing inferred from Frame.io's documentation.
The assets are what most of this inventory is about, alongside the comments. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Frame.io admin becomes a queue you review.
- Search Assets
Which assets wait for your approval?
All 3 write operations wait for you.
A companion can create a project, create a comment and create an asset, and each one is staged on an approval card first: you see the asset, the field and the new value before it lands in Frame.io.
Nothing in Frame.io 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 Project
- Create Comment
- Create Asset
What does the recurring assets pass look like?
Yes.
Saved as a routine, the Frame.io 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 documents, the Frame.io 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