Commands

The Sentry CLI provides commands for interacting with various Sentry resources.

Available Commands

Command	Description
alert	Manage Sentry alert rules
auth	Authenticate with Sentry
build	Manage mobile build artifacts
cli	CLI-related commands
code-mappings	Manage code mappings for stack trace linking
agent-conversation	List and view agent conversations
dart-symbol-map	Work with Dart/Flutter symbol maps
debug-files	Work with debug information files
dashboard	Manage Sentry dashboards
docs	Search and query current Sentry documentation
org	Work with Sentry organizations
platform	List valid Sentry platform identifiers
project	Work with Sentry projects
proguard	Work with ProGuard/R8 mapping files
react-native	Upload React Native sourcemaps from build steps
replay	Search and inspect Session Replays
release	Work with Sentry releases
repo	Work with Sentry repositories
team	Work with Sentry teams
issue	Manage Sentry issues
event	View, list, and send Sentry events
explore	Query aggregate event data (Explore)
feedback	Search and inspect User Feedback
log	View Sentry logs
monitor	Work with Sentry cron monitors
snapshots	Manage and compare snapshots
sourcemap	Manage sourcemaps
span	List and view spans in projects or traces
status	Check Sentry service status
trace	View distributed traces
trial	Manage product trials
init	Initialize Sentry in your project (experimental)
info	Print configuration and verify authentication
local	Sentry for local development
api	Make an authenticated API request
schema	Browse the Sentry API schema
wasm-split	Add build ids to WebAssembly modules and split out debug data

Global Options

All commands support the following global options:

• --help - Show help for the command
• --version - Show CLI version
• --log-level <level> - Set log verbosity (error, warn, log, info, debug, trace). Overrides SENTRY_LOG_LEVEL
• --verbose - Shorthand for --log-level debug

Targeting Organizations and Projects

Many commands accept an optional <org>/<project> target, either as the first positional argument (list commands) or as a prefix of an ID (e.g. my-org/my-project/<trace-id>). When you omit it, the CLI auto-detects the org and project (see Resolution Priority).

Target	Meaning
(omitted)	Auto-detect org and project
<org>/<project>	That project in that organization
<org>/	The whole organization (trailing slash)
<name>	A project named <name> in any accessible organization. If no project matches, commands that accept an organization use the org named <name> instead

When a project and an organization share the same slug, the bare form selects the project. Add the trailing slash (my-org/) to target the organization explicitly.

JSON Output

Most list and view commands support --json flag for JSON output, making it easy to integrate with other tools:

sentry org list --json | jq '.[] | .slug'

Opening in Browser

View commands support -w or --web flag to open the resource in your browser:

sentry issue view PROJ-123 -w