Skip to content
Simulo

Browse and manage assets

Robots, worlds and props live in two catalogs: your organization’s catalog, which holds what you publish, and the Simulo global catalog, which every organization can use. This guide covers finding assets and managing the versions you own. For how references and version pins work, read Asset catalogs & version pinning.

Find assets

Section titled “Find assets”
Terminal window
simulo asset list
simulo asset list --kind robot

simulo asset list shows the first 20 assets. Use --all for every match, --limit N for up to 100, --tag TAG to filter by tag, or --json for automation. JSON output without --limit always holds the complete list.

simulo asset search looks in both catalogs at once and labels each result with its scope. It matches names and descriptions and returns every match, so it has no --all or --limit.

An asset whose latest version is deprecated is hidden from both commands. Add --deprecated to simulo asset list to show those assets too, marked (deprecated).

Inspect an asset

Section titled “Inspect an asset”

Leave off the version to see the latest one, or add :vN for an exact version. Global assets start with simulo/:

Terminal window
simulo asset inspect robot/my-arm
simulo asset inspect robot/my-arm:v1
simulo asset inspect simulo/robot/cartpole:v1

The summary shows the entry file, the package digest, its source, each validation, the facts validation measured, how many jobs use it, and every version. Save the full record or the validation report as files:

Terminal window
simulo asset inspect robot/my-arm:v1 --json > my-arm.record.json
simulo asset inspect robot/my-arm:v1 --report my-arm.validation.json

If the newest version is still validating, --wait watches it until it publishes or fails, then shows the result:

Terminal window
simulo asset inspect robot/my-arm --wait

Press Ctrl-C to stop watching. Validation continues in the cloud. See Asset validation before you use a report as a CI gate.

Download one of your versions

Section titled “Download one of your versions”
Terminal window
simulo asset get robot/my-arm:v1
Downloaded to ~/.simulo/assets/<your-org>/robot/my-arm/v1/ (entry: robot.usda)

The client checks the package against its recorded digest before it writes anything. You can download your organization’s assets. Global catalog assets work in jobs but can’t be downloaded.

Deprecate and reactivate

Section titled “Deprecate and reactivate”

Deprecating a version hides it from list and search, and new submits that use it print a warning. Jobs that already pinned it keep working.

Terminal window
simulo asset deprecate robot/my-arm:v1
simulo asset reactivate robot/my-arm:v1

reactivate undoes a deprecation. Both commands need an exact :vN version. simulo run --strict-assets turns the deprecation warning into an error.

Delete a version

Section titled “Delete a version”
Terminal window
simulo asset delete robot/my-arm:v1

Deleting is permanent, so a plain delete refuses while any job references the version. The refusal says how many jobs use it and suggests the two ways forward: deprecate the version, or pass --force. Deprecate it when you only want to stop new use.

For every option, see the simulo asset CLI reference.