sentry-cli · Sentry

Sentry CLI for AI Agents

Inspect projects and automate Sentry releases, source maps, and deploy records with scoped credentials.

Official toolOperational risk: R0–R3docs-verified

Install for an Agent Report broken data

Agent readiness

84/100

Evidence confidence

docs-verified

Documentation checked

2026-07-10

Independently tested version

Not independently tested

Install for an Agent

Choose an official installation path that matches the runtime. Pin a version for team or CI use, then record the version before the first task.

npmRecommended

macos · linux · windows

$ shell

npm install --save-dev @sentry/cli

Authentication and Minimum Permissions

Grant only the permissions the task needs. Pass credentials through environment variables or a platform secret store, never through prompts, repositories, or logs.

Authentication requiredHeadless authentication supported

Use a token limited to the required organization, project, and release scopes.

Methods: auth token, DSN for some commands
Secret environment variables: SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT, SENTRY_URL
Credential storage: For headless runs, inject SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT, SENTRY_URL from the CI or platform secret manager at process start. For local interactive use, prefer the CLI or operating-system credential store when the official client supports one. Never save values in repository files.

Agent and Environment Compatibility

Confirm shell access first, then check the platform, network boundary, and credential path.

claude-codecodexgemini-clicopilot-cli

Environments: local, ci, container, headless, remote
Platforms: macos, linux, windows

Structured Output for Reliable Automation

Prefer a machine-readable format. Treat stdout as the result channel and stderr as diagnostics so the agent can parse failures separately.

json · text

Use --json where supported and keep diagnostic logs on stderr.

--json

No independently captured output sample

Structured-output support currently comes from official documentation. CLI Finder does not show a guessed example or invented schema before a bounded, non-destructive execution captures stdout.

R0–R3 Command Risk Guide

Risk is assigned per command. R0 is local or remote read-only, R1 is reversible local write, R2 changes remote state, and R3 can be irreversible or production-impacting.

Read-only does not mean public

R0 only means the command does not change local or remote state. A read-only command may still return secrets, identity data, configuration, or production data. Expose only the minimum needed for the task, and never place it in logs, prompts, or commits.

R0List projects

Reads project metadata in the configured organization.

$ shell

npx sentry-cli projects list --json

IdempotentSensitive output

R2Create a release

Creates remote release state in Sentry.

$ shell

npx sentry-cli releases new RELEASE

Confirmation requiredMay repeat a change

R3Delete a release

Deletes Sentry release data and associated artifacts.

$ shell

npx sentry-cli releases delete RELEASE

Confirmation requiredMay repeat a change

How the Agent Readiness Score Is Built

Readiness describes how reliably an agent can operate the tool. It does not make every command safe and it does not replace an independent execution test.

Documentation indicates an agent-readiness score of 84/100. No local execution test has been recorded.

Structured output

Use --json where supported and keep diagnostic logs on stderr.

18/20

Headless operation

Official documentation describes a non-interactive authentication or execution path.

14/15

Safety controls

CLI Finder separates read commands from commands that require confirmation.

11/15

Determinism

Commands use explicit arguments and documented output controls where available.

8/10

Authentication

Use a token limited to the required organization, project, and release scopes.

8/10

Documentation

This entry cites official documentation checked on 2026-07-10.

9/10

Installation

Official installation paths cover macOS, Linux, and Windows.

8/8

Maintenance

An official source repository is linked for release and maintenance review.

6/7

Agent artifacts

CLI Finder can generate registry-derived skills and policies; the tool itself was not credited with shipping them.

2/5

Generate a Skill or Agent Policy

Choose an agent and safety mode to generate a copyable artifact with installation, allowed commands, approval boundaries, and the evidence limitation.

Artifact typeTarget agentSafety mode

Generated artifact preview

SKILL.md

---
name: sentry-cli-agent-workflow
description: Use Sentry CLI for Sentry releases, source maps, deploy records with explicit command risk and evidence boundaries.
---

# Sentry CLI agent workflow

Use this skill when the task needs Sentry releases, source maps, deploy records, project inspection.

## Evidence boundary

- Registry confidence: `docs-verified`
- Documentation checked: `2026-07-10`
- Locally tested version: `not tested`
- Do not describe this CLI as locally verified until its commands have actually been executed in an isolated environment.

## Executed smoke checks

- No local execution record is available.

## Installation

- npm (macos, linux, windows): `npm install --save-dev @sentry/cli`

## Authentication

- Methods: auth token, DSN for some commands
- Secret environment variables: `SENTRY_AUTH_TOKEN`, `SENTRY_ORG`, `SENTRY_PROJECT`, `SENTRY_URL`
- Minimum permissions: Use a token limited to the required organization, project, and release scopes.
- Credential storage: For headless runs, inject SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT, SENTRY_URL from the CI or platform secret manager at process start. For local interactive use, prefer the CLI or operating-system credential store when the official client supports one. Never save values in repository files.
- Never print, persist, or commit credential values.

## Allowed commands (read-only)

- `npx sentry-cli projects list --json` — R0: Reads project metadata in the configured organization.

## Commands requiring explicit approval (read-only)

- None recorded.

## Forbidden commands (read-only)

- R2 `npx sentry-cli releases new RELEASE` — Creates remote release state in Sentry.
- R3 `npx sentry-cli releases delete RELEASE` — Deletes Sentry release data and associated artifacts.

## Execution rules

1. Mode boundary: R0 exact commands may be used; R1, R2, and R3 commands are forbidden.
2. Confirm the selected account, project, context, database, namespace, or environment before any command.
3. Prefer structured output using `--json`.
4. Capture the exact command, exit code, stdout, and stderr separately.
5. A generated prefix policy must prompt unless that exact prefix is explicitly marked suffix-safe; do not infer safety from the executable name.
6. Never broaden credentials or disable safety controls to make a command succeed.

## Official sources

- [Sentry CLI documentation](https://docs.sentry.io/product/cli/)
- [Sentry CLI documentation source repository](https://github.com/getsentry/sentry-cli)

CLI vs MCP vs API for This Task

CLI

Use the CLI on a developer machine, in CI, or in a container when the task should reuse existing shell state, credentials, and scripts and remain directly observable.

MCP

Consider MCP when the agent benefits from controlled tool definitions, delegated identity, or centrally governed server-side access.

API

Use the direct API for persistent application integrations, high-volume requests, or event-driven work where starting a process adds unnecessary overhead.

Read the full CLI vs MCP guide

Verification History and Official Evidence

CLI Finder records documentation review separately from real execution. Installation, help, exit codes, and output cannot be called Verified until they were run.

Current evidence boundary

Official documentation was reviewed, but installation, help output, exit codes, headless behavior, and structured output were not executed locally.