Beta: The GlitchTip CLI is pre-1.0 software. Commands and options may change between releases.
The GlitchTip CLI is a command-line tool for interacting with GlitchTip. It can upload source maps and debug symbols, manage releases, send test events, and more.
Download a pre-built binary from the releases page.
If you have Rust installed:
cargo install --git https://gitlab.com/glitchtip/glitchtip-cli.git
Log in to your GlitchTip instance:
glitchtip-cli --url https://your-glitchtip.example.com login
By default this prompts you to paste an API token. Use --method oauth for browser-based OAuth authentication:
glitchtip-cli --url https://your-glitchtip.example.com login --method oauth
Credentials are saved to a local .sentryclirc file (or globally with --global to ~/.config/glitchtip-cli/config).
The CLI uses a four-tier configuration system (highest priority first):
--url, --auth-token, --org, --projectSENTRY_URL, SENTRY_AUTH_TOKEN, SENTRY_DSN, etc..glitchtip-cli.rc or .sentryclirc (searched upward from current directory, INI format)~/.config/glitchtip-cli/config (INI format)Key environment variables:
| Variable | Description |
|---|---|
SENTRY_URL |
Your GlitchTip instance URL |
SENTRY_AUTH_TOKEN |
API authentication token |
SENTRY_DSN |
Project DSN (for send-event and monitors) |
SENTRY_ORG |
Default organization slug |
SENTRY_PROJECT |
Default project slug |
Example config file (INI format):
[auth]
token=your-api-token
[defaults]
url=https://your-glitchtip.example.com
org=my-org
project=my-project
Send a test event to verify your setup:
glitchtip-cli send-event -m "Test event from CLI"
Create and manage releases:
# Create a new release
glitchtip-cli releases new 1.0.0 --org my-org --project my-project
# Finalize a release
glitchtip-cli releases finalize 1.0.0 --org my-org --project my-project
# Associate commits with a release (auto-discovers from git)
glitchtip-cli releases set-commits 1.0.0 --auto --org my-org --project my-project
# List releases
glitchtip-cli releases list --org my-org --project my-project
# Delete a release
glitchtip-cli releases delete 1.0.0 --org my-org --project my-project
Record deployments for a release:
glitchtip-cli deploys new 1.0.0 --env production --org my-org --project my-project
glitchtip-cli deploys list 1.0.0 --org my-org --project my-project
Upload source maps for readable JavaScript stack traces:
# Inject debug IDs into source files
glitchtip-cli sourcemaps inject ./dist
# Upload source maps with debug IDs
glitchtip-cli sourcemaps upload ./dist --release 1.0.0 --org my-org --project my-project
Upload debug symbols for native applications (dSYM, PDB, ELF):
glitchtip-cli debug-files upload ./build --org my-org --project my-project
Manage uptime monitors and send heartbeats:
# List monitors
glitchtip-cli monitors list --org my-org
# Run a command and send a heartbeat on success
glitchtip-cli monitors run <ENDPOINT_UUID> -- python manage.py scheduled_task
# Create a monitor
glitchtip-cli monitors create "My Monitor" --url https://example.com --org my-org --project my-project
# Delete a monitor
glitchtip-cli monitors delete <MONITOR_ID> --org my-org
Manage issues from the command line:
# List issues
glitchtip-cli issues list --org my-org --project my-project
# Resolve issues
glitchtip-cli issues resolve --id 123
# Mute issues
glitchtip-cli issues mute --id 456
# Unresolve issues
glitchtip-cli issues unresolve --id 789
Query logs from the command line:
glitchtip-cli logs list --org my-org
Check your current configuration and authentication status:
glitchtip-cli info