Official Sentry CLI for releases, deploys, sourcemaps, debug files, issue and log inspection, and cron monitor check-ins.
$curl -sL https://sentry.io/get-cli/ | sh
Agent Compatibility
JSON Output
Agent Skill
MCP Support
AI Analysis
Sentry CLI is Sentry's command-line tool for release management, build artifact uploads, manual event sending, log inspection, and cron monitor check-ins. It is most useful in CI or scripted delivery flows that need to talk to Sentry without opening the web app.
What It Enables
- Create, finalize, archive, delete, and inspect releases, then attach deploy records and commit metadata from local git or configured repositories.
- Upload sourcemaps, debug symbols, source bundles, ProGuard mappings, and mobile build artifacts so Sentry can symbolicate errors and releases correctly.
- List issues, events, logs, projects, repos, and monitors; send manual events; and wrap scheduled jobs so Sentry records monitor check-ins.
Agent Fit
- Works well in CI when org or project defaults and auth tokens are supplied non-interactively;
monitors runis especially shell-friendly because it wraps a command and exits with that command's status. - There is real structured output, but it is uneven:
debug-files check,debug-files find, andinfo --config-status-jsonemit JSON, while many inspect commands print tables andreleases listonly offers raw text. - Browser-assisted
loginand Sentry's separate newer interactive CLI make this a better fit for release and artifact automation than for broad day-to-day incident triage by agents.
Caveats
- Useful unattended use assumes auth tokens and org or project context are already configured.
- Official docs now point users seeking the newer interactive human or agent CLI to
cli.sentry.dev, sosentry-clishould be positioned here as the build and release automation tool.