Share feedback
Answers are generated based on the documentation.

sbx kit inspect

DescriptionShow kit artifact details
Usagesbx kit inspect REFERENCE [flags]

Experimental

This command is experimental.

Experimental features are intended for testing and feedback as their functionality or design may change between releases without warning or can be removed entirely in a future release.

Description

Load and display details about a kit artifact.

The reference can be a local directory, ZIP file path, OCI registry reference, or git repository.

Pass --kit-arg to preview how the kit resolves with a given set of arguments; the output shows the substituted content.

--offline skips the daemon-backed kit policy (kit.allowedSources, kit.allowLocalKits, kit.requireSignature) so the command needs neither sandboxd nor a signed-in session; it only accepts a local directory or ZIP reference, since those are the only ones this check applies to.

Options

OptionDefaultDescription
--formatOutput format: table, json or yaml
--jsonOutput in JSON format
--kit-argexperimental Value for an argument the kit declares, as name=value for every kit or kit.name=value for one (can be repeated)
--kit-args-fileexperimental File of name=value kit arguments, one per line (can be repeated); --kit-arg overrides
--offlineSkip the daemon-backed kit policy check; local directory or ZIP references only

Global options

OptionDefaultDescription
--cloudDispatch to Docker Cloud Sandboxes API instead of local sandboxd (supported by a growing set of verbs — run 'sbx --cloud --help' for the current list)
-D, --debugEnable debug logging

Examples

sbx kit inspect ./my-kit
sbx kit inspect ghcr.io/myorg/my-kit:1.0

# Machine-readable output
sbx kit inspect ghcr.io/myorg/my-kit:1.0 --format json

# Inspect without sandboxd running or a Docker sign-in
sbx kit inspect ./my-kit --offline