Command reference

Every command and flag is documented in the CLI's built-in help, which is always in sync with the installed version:

bugsee-cli --help              # top-level command list + global flags
bugsee-cli <command> --help    # full options for one command

This page maps the command tree to the guides in this section.

Global flags

Flag	Environment variable	Description
--app-token <APP_TOKEN>	BUGSEE_APP_TOKEN	App token. Required by the upload commands; ignored by the resolvers.
--endpoint <ENDPOINT>	BUGSEE_ENDPOINT	API endpoint (default https://api.bugsee.com). Used only by upload commands.
-h, --help	—	Print help.
-V, --version	—	Print the CLI version.

See Configuration for details.

Commands

Command	What it does	Guide
debug-files upload	Discover, package, and upload debug information files (ProGuard, ELF, dSYM, source maps).	Debug files
sourcemaps inject	Inject deterministic debug IDs into JS bundles and their .map files.	Source maps
upload build	Register a build and upload its artefact (single-PUT or chunked).	Builds
upload build-info	Upload per-build metadata sidecars in one bundle.	Builds
pack	Build the normalized upload ZIP locally, without uploading.	Builds
xcode post-action	Run the whole iOS build-publish flow from an Xcode post-action.	iOS build publishing
vcs-metadata	Resolve VCS metadata (provider, commit, branch, PR, repo).	Metadata resolvers
ios-deps collect	Collect the iOS dependency graph from lockfiles + linked frameworks.	Metadata resolvers
build-env xcode-version	Resolve the dotted Xcode version.	Metadata resolvers
build-env machine-label	Emit the CI-aware host label.	Metadata resolvers
build-env read-plist	Read an Info.plist's scalar keys as JSON.	Metadata resolvers
dsym uuid	Extract Mach-O UUIDs from a dSYM bundle or binary.	Metadata resolvers
dsym slices	Same as uuid, with per-slice architecture.	Metadata resolvers
update	Self-update the binary (same-major).	Updating the CLI

Exit codes

Upload commands follow a structured exit-code contract; resolvers exit 0 and signal "no result" through their JSON output shape.