sentry-cliSentry.io error monitoring via sentry-cli. Use when working with Sentry releases, source maps, dSYMs, events, or issue management. Covers authentication, release workflows, deploy tracking, and debug file uploads.
Install via ClawdBot CLI:
clawdbot install iAhmadZain/sentry-cliInteract with Sentry.io for error monitoring, release management, and debug artifact uploads.
# macOS
brew install sentry-cli
# npm (cross-platform)
npm install -g @sentry/cli
# Direct download
curl -sL https://sentry.io/get-cli/ | bash
# Interactive login (opens browser)
sentry-cli login
# Or set token directly
export SENTRY_AUTH_TOKEN="sntrys_..."
# Verify
sentry-cli info
Store tokens in .sentryclirc or environment:
[auth]
token=sntrys_...
[defaults]
org=my-org
project=my-project
# Create release (usually git SHA or version)
sentry-cli releases new "$VERSION"
# Associate commits (links errors to commits)
sentry-cli releases set-commits "$VERSION" --auto
# Finalize when deployed
sentry-cli releases finalize "$VERSION"
# One-liner for CI
sentry-cli releases new "$VERSION" --finalize
# Mark release as deployed to an environment
sentry-cli releases deploys "$VERSION" new -e production
sentry-cli releases deploys "$VERSION" new -e staging
sentry-cli releases list
sentry-cli releases info "$VERSION"
Upload source maps for JavaScript error deobfuscation:
# Upload all .js and .map files
sentry-cli sourcemaps upload ./dist --release="$VERSION"
# With URL prefix (match your deployed paths)
sentry-cli sourcemaps upload ./dist \
--release="$VERSION" \
--url-prefix="~/static/js"
# Validate before upload
sentry-cli sourcemaps explain ./dist/main.js.map
# Inject debug IDs into source files (modern approach)
sentry-cli sourcemaps inject ./dist
sentry-cli sourcemaps upload ./dist --release="$VERSION"
# Upload dSYMs from Xcode archive
sentry-cli debug-files upload --include-sources path/to/dSYMs
# From derived data
sentry-cli debug-files upload ~/Library/Developer/Xcode/DerivedData/*/Build/Products/*/*.app.dSYM
sentry-cli upload-proguard mapping.txt --uuid="$UUID"
sentry-cli debug-files check path/to/file
sentry-cli debug-files list
sentry-cli send-event -m "Test error message"
sentry-cli send-event -m "Error" --logfile /var/log/app.log
# List unresolved issues
sentry-cli issues list
# Resolve an issue
sentry-cli issues resolve ISSUE_ID
# Mute/ignore
sentry-cli issues mute ISSUE_ID
# Wrap a cron job
sentry-cli monitors run my-cron-monitor -- /path/to/script.sh
# Manual check-ins
sentry-cli monitors check-in my-monitor --status ok
sentry-cli monitors check-in my-monitor --status error
- name: Create Sentry Release
uses: getsentry/action-release@v1
env:
SENTRY_AUTH_TOKEN: ${{ secrets.SENTRY_AUTH_TOKEN }}
SENTRY_ORG: my-org
SENTRY_PROJECT: my-project
with:
environment: production
sourcemaps: ./dist
export SENTRY_AUTH_TOKEN="$SENTRY_TOKEN"
export SENTRY_ORG="my-org"
export SENTRY_PROJECT="my-project"
VERSION=$(sentry-cli releases propose-version)
sentry-cli releases new "$VERSION" --finalize
sentry-cli releases set-commits "$VERSION" --auto
sentry-cli sourcemaps upload ./dist --release="$VERSION"
sentry-cli releases deploys "$VERSION" new -e production
| Flag | Description |
|------|-------------|
| -o, --org | Organization slug |
| -p, --project | Project slug |
| --auth-token | Override auth token |
| --log-level | debug/info/warn/error |
| --quiet | Suppress output |
# Check configuration
sentry-cli info
# Debug upload issues
sentry-cli --log-level=debug sourcemaps upload ./dist
# Validate source map
sentry-cli sourcemaps explain ./dist/main.js.map
# Check connectivity
sentry-cli send-event -m "test" --log-level=debug
Generated Mar 1, 2026
A development team automates Sentry release creation and source map uploads during their CI/CD pipeline. They use sentry-cli to create releases with version tags, associate git commits, and upload JavaScript source maps for error deobfuscation, ensuring accurate error tracking in production deployments.
A mobile app team uploads dSYM files for iOS or ProGuard mappings for Android to Sentry after each build. This allows Sentry to symbolicate crash reports, providing readable stack traces for debugging issues in native mobile applications across different environments.
Operations engineers use sentry-cli to query and manage issues in production systems. They list unresolved errors, resolve or mute issues based on severity, and send test events to verify integration, helping maintain system reliability and quick incident response.
A data analytics company integrates sentry-cli monitors to track scheduled cron jobs. They wrap scripts with sentry-cli to automatically check in and report status, enabling alerts for failed jobs and ensuring data pipelines run smoothly without manual oversight.
Sentry.io offers tiered subscription plans based on event volume, features like release management, and support levels. Revenue is generated from monthly or annual fees paid by organizations for error monitoring and performance insights across their applications.
Large enterprises purchase custom licenses for Sentry with advanced features, on-premise deployment options, and dedicated support. Revenue comes from high-value contracts tailored to specific security, compliance, and scalability needs of large-scale operations.
Sentry provides a free tier with basic error tracking and limited features to attract individual developers and small teams. Revenue is generated by upselling to paid plans that include advanced capabilities like release management, source maps, and higher event quotas.
💬 Integration Tip
Set up environment variables for SENTRY_AUTH_TOKEN, SENTRY_ORG, and SENTRY_PROJECT in CI/CD pipelines to automate releases and source map uploads without hardcoding credentials.
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
Command-line tool to manage Google Workspace services including Gmail, Calendar, Drive, Sheets, Docs, Slides, Contacts, Tasks, People, Groups, and Keep.
Runs shell commands inside a dedicated tmux session named claw, captures, and returns the output, with safety checks for destructive commands.
A modern text-based browser. Renders web pages in the terminal using headless Firefox.
Write robust, portable shell scripts. Use when parsing arguments, handling errors properly, writing POSIX-compatible scripts, managing temp files, running commands in parallel, managing background processes, or adding --help to scripts.
NotebookLM CLI wrapper via `node {baseDir}/scripts/notebooklm.mjs`. Use for auth, notebooks, chat, sources, notes, sharing, research, and artifact generation/download.