73 /100
Good for release automation, but auth tokens and artifact uploads need tight controls.
Structured output 72/100
Whether the CLI can return JSON, YAML, or stable machine-readable output.
Non-interactive use 78/100
Whether common workflows can run predictably without an interactive prompt.
Safety boundaries 56/100
Whether read-only, dry-run, scoped auth, and destructive command boundaries are clear.
Install options
npm
$ npm install -g @sentry/cli Homebrew
$ brew install getsentry/tools/sentry-cli Common commands
List releases · safe
$ sentry-cli releases list --org my-org Inspects release history.
Upload sourcemaps · requires review
$ sentry-cli sourcemaps upload ./dist Changes release artifact state.
Agent usage examples
Codex CLI
Use Sentry CLI to inspect release state and upload sourcemaps only after build artifacts are verified. Safety notes
- Release creation and sourcemap upload change production observability state.
- Agents should inspect releases before creating or finalizing new ones.
What agents can use it for
Sentry CLI helps agents inspect release state, connect commits, and upload verified sourcemaps.
Best fit
Use it in deployment pipelines where observability artifacts need to match a shipped release.