Skip to main content

​
sentry cli feedback

Submit feedback about your experience with the Sentry CLI. All text after feedback is sent as your message.

​
Usage

sentry cli feedback <message...>

​
Arguments

  • message (required) - Your feedback message (all remaining arguments are joined into a single message)

​
Examples

​
Positive Feedback

sentry cli feedback I love this tool

​
Feature Request

sentry cli feedback Please add support for searching issues by tag

​
Report Confusion

sentry cli feedback The issue view is confusing, needs better formatting

​
Multi-word Messages

sentry cli feedback The upgrade command worked perfectly on macOS
No quotes needed—all arguments are automatically joined into a single message.

​
How It Works

  1. Your feedback is sent to Sentry via the @sentry/bun SDK’s captureFeedback() method
  2. The CLI waits up to 3 seconds to ensure the feedback is sent before exiting
  3. Feedback is associated with your CLI version and platform for context

​
Telemetry Requirement

Feedback requires telemetry to be enabled. If telemetry is disabled: 
$ sentry cli feedback This is great
Feedback not sent: telemetry is disabled.
Unset SENTRY_CLI_NO_TELEMETRY to enable feedback.

​
Enabling Feedback

To enable feedback, unset the SENTRY_CLI_NO_TELEMETRY environment variable: 
# Temporary (current session)
unset SENTRY_CLI_NO_TELEMETRY

# Permanent (add to ~/.bashrc, ~/.zshrc, etc.)
# Remove this line if present: export SENTRY_CLI_NO_TELEMETRY=1

​
Success Confirmation

When feedback is successfully sent: 
$ sentry cli feedback This is great
Feedback submitted. Thank you!

​
Network Timeout

If the feedback cannot be sent within 3 seconds (network issues): 
$ sentry cli feedback This is great
Feedback may not have been sent (network timeout).
The CLI does not retry automatically. Try again when you have a stable internet connection.

​
Empty Messages

Empty or whitespace-only messages are rejected: 
$ sentry cli feedback
Error: Please provide a feedback message.

​
Privacy

Feedback submissions include:
  • Your feedback message
  • CLI version (e.g., 0.5.0)
  • Platform/OS (e.g., darwin, linux, win32)
  • Timestamp
Not included:
  • Authentication tokens
  • Project/organization data
  • File paths or code from your machine
  • Personal information (unless you include it in your message)

​
Use Cases

​
Report Bugs

sentry cli feedback The issue list command crashes when using --period flag
Note: For detailed bug reports, consider opening an issue at https://github.com/getsentry/sentry-cli/issues

​
Suggest Features

sentry cli feedback Add support for exporting issues to CSV

​
Report Confusion

sentry cli feedback Not sure what --follow mode does in issue list

​
Express Appreciation

sentry cli feedback The auto-detection of projects from DSN is amazing

​
Feedback vs. GitHub Issues

Feedback CommandGitHub Issues
Quick, one-line thoughtsDetailed bug reports
Feature ideasFeature proposals with use cases
General impressionsReproducible steps
Anonymous (no GitHub account needed)Public discussion
Sent to Sentry teamCommunity + team visibility
When to use feedback:
  • Quick thoughts or impressions
  • Don’t need a response
  • Want to remain anonymous
When to use GitHub issues:
  • Need detailed troubleshooting
  • Want to track progress
  • Need to share logs, screenshots, or code

​
Exit Codes

  • 0 - Feedback sent successfully (or telemetry disabled)
  • 1 - Validation error (empty message)

​
External Resources

Build docs developers (and LLMs) love

Get started for freeTalk to us