/issue

Examples

List issues

# List issues in a specific project
sentry issue list my-org/frontend

# All projects in an org
sentry issue list my-org/

# Search for a project across organizations
sentry issue list frontend

ID            SHORT ID    TITLE                           COUNT   USERS
123456789     FRONT-ABC   TypeError: Cannot read prop...  1.2k    234
987654321     FRONT-DEF   ReferenceError: x is not de...  456     89

**Filter by status and search:**

# Show only unresolved issues
sentry issue list my-org/frontend --query "is:unresolved"

# Show resolved issues
sentry issue list my-org/frontend --query "is:resolved"

# Sort by frequency
sentry issue list my-org/frontend --sort freq --limit 20

# Sort by Sentry's "recommended" relevance ranking (the default on sentry.io;
# self-hosted instances default to "date" and require a recent Sentry version
# to accept --sort recommended)
sentry issue list my-org/frontend --sort recommended

# Multiple filters (space-separated = implicit AND)
sentry issue list --query "is:unresolved level:error assigned:me"

# Negation and wildcards
sentry issue list --query "!browser:Chrome message:*timeout*"

# Match multiple values for one key (in-list syntax)
sentry issue list --query "browser:[Chrome,Firefox]"

:::caution[Search syntax] Sentry search uses **implicit AND** — space-separated terms are all required. **AND/OR operators are not supported** for issue search. Use alternatives:

• `key:[val1,val2]` — in-list syntax (matches val1 OR val2 for one key)
• Run separate queries for different terms
• `*term*` — wildcard matching

Full syntax reference: [Sentry Search Docs](https://docs.sentry.io/concepts/search/) :::

Magic selectors

Use `@latest` and `@most_frequent` to target issues without knowing their ID:

# View the most recent issue
sentry issue view @latest

# Explain the most frequently occurring issue
sentry issue explain @most_frequent

# Generate a fix plan for the latest issue
sentry issue plan @latest

Common mistakes

• **Don't use the issue command name as an issue prefix** — `sentry issue explain issue-1` is parsed as project `issue` + suffix `1`. Use a real project prefix: `sentry issue explain FRONT-1` or a numeric ID: `sentry issue explain 123456789`.
• **Issue short IDs use uppercase prefixes** — `CLI-G`, not `cli-g`. The CLI tolerates lowercase input in most commands, but agents should prefer the canonical form.
• **`org/project` targets use slugs, not numeric IDs** — `sentry issue list my-org/6775615880` fails when `6775615880` is a project ID copied from a URL. Run `sentry project list my-org/` to find the slug (e.g. `frontend`).
• **Prefer auto-detect over guessing slugs** — omit the target when possible; the CLI resolves org/project from DSNs, `.env` files, and your working directory.

List events for an issue

# List recent events for an issue
sentry issue events FRONT-ABC

# Filter events by search query
sentry issue events FRONT-ABC --query "browser:Chrome"

# Show full event details
sentry issue events FRONT-ABC --full

# Limit results and filter by time period
sentry issue events FRONT-ABC --limit 50 --period 24h

# Paginate through results
sentry issue events FRONT-ABC -c next

View an issue

sentry issue view FRONT-ABC

# Multiple issues in one invocation (space-separated, not commas)
sentry issue view FRONT-ABC BACK-2

Issue: TypeError: Cannot read property 'foo' of undefined
Short ID: FRONT-ABC
Status: unresolved
First seen: 2024-01-15 10:30:00
Last seen: 2024-01-20 14:22:00
Events: 1,234
Users affected: 234

Latest event:
  Browser: Chrome 120
  OS: Windows 10
  URL: https://example.com/app

# Open one or more issues in the browser (up to 5 tabs by default)
sentry issue view FRONT-ABC BACK-2 -w

# Explicitly allow more than 5 tabs
sentry issue view FRONT-ABC BACK-2 API-3 WEB-4 IOS-5 OPS-6 -w --force

# GitHub-style identifiers work too (the "#" replaces the final slash)
sentry issue view my-org/my-project#FRONT-ABC
sentry issue view my-project#FRONT-ABC

**JSON output for agents and scripting:**

`--json` returns the issue fields at the top level plus the latest event under `event`, the resolved `org` slug, related `replayIds`, and `trace` context. Prefer this over the human output when parsing programmatically. One issue ID still returns a single object; multiple IDs return an array of those objects.

# Full JSON (issue fields + latest event + trace/replay context)
sentry issue view FRONT-ABC --json

# Multiple issues: JSON is an array of the same objects
sentry issue view FRONT-ABC BACK-2 --json

# Select specific top-level fields to keep output small
sentry issue view FRONT-ABC --json --fields shortId,title,culprit,count,userCount,permalink

# Pull named fields off the latest event instead of the whole `event` object —
# the event's `request` entry can include live session data (cookies, headers,
# body), so extract only what you need
sentry issue view FRONT-ABC --json --fields event.id,event.title,event.dateCreated

Common `jq` shapes for the `--json` output. The latest event's data lives under `event.entries[]`, each tagged with a `type` (`"exception"`, `"request"`, `"breadcrumbs"`, …) and a `data` payload — not as top-level `event.request` / `event.exception` keys:

# Issue summary
sentry issue view FRONT-ABC --json | jq '{shortId, title, count, userCount, permalink}'

# Latest event id + culprit
sentry issue view FRONT-ABC --json | jq '{event: .event.id, culprit}'

# Just the request URL and method (avoids the full request/session blob)
sentry issue view FRONT-ABC --json | jq '.event.entries[] | select(.type == "request") | .data | {url, method}'

# Exception type and value from the latest event
sentry issue view FRONT-ABC --json | jq '.event.entries[] | select(.type == "exception") | .data.values[0] | {type, value}'

Explain issues with Seer AI

# A