Commands

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

Available Commands

Command	Description
alert	Manage Sentry alert rules
attribute	Explore span, log, and metric attributes
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
dsn	Find Sentry DSNs
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
token	Manage org auth tokens
integration	Work with Sentry integrations
issue	Manage Sentry issues
event	View, list, and send Sentry events
explore	Query aggregate event data (Explore)
feedback	Manage User Feedback
log	View Sentry logs
mcp	Start a local Sentry MCP server
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	Print instructions for a coding agent to set up Sentry
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 take an optional <org>/<project> target as their first positional argument, or as a prefix of an ID (e.g. my-org/my-project/<trace-id>).

Target	Meaning
(omitted)	Auto-detect the org and project from config, DSNs, or the directory name
https://<org>.sentry.io/...	A Sentry web URL. Selects the org and project in the URL, or the whole organization when it names no project
<org>/<glob>	Entities in that organization whose names match the glob, e.g. <org>/web-* (list commands that filter by name)
<glob>	Entities whose names match the glob, in the auto-detected organization (list commands that filter by name)
/<glob>	Same as <glob>
<org>/<project>	That project in that organization
<org>/<project>,<project>	Several projects in the same organization (commands that accept several projects)
<org>/<Project Name>	A project in that organization whose display name matches. A target with a space is a name, not a slug
<org>/	The whole organization
<name>	A project named <name> in any accessible organization. If no project matches, commands that accept an organization use the organization named <name>. When both exist, the project wins: add the trailing slash (<name>/) to select the organization
/<name>	Same as <name>
<Project Name>	A project whose display name matches, in any accessible organization

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