Everything you need to tame noisy error queues

Framework agnostic

Use it in Laravel, Symfony, or any PHP project. The CLI ships with zero-config defaults that just work.

Actionable TODOs

Pull unresolved issues into a human-friendly TODO file, prioritized by frequency and user impact.

Bulk resolution

Resolve dozens of issues in one shot. Every action is logged so your team stays aligned.

Token diagnostics

Validate Sentry tokens and scopes without touching production. Ideal for CI checks and onboarding.

Install in your dev stack

Keep the package in dev dependencies so production deployments stay lean and secure.

1

Add the package

composer require --dev programinglive/sentry-resolve
2

Publish config (Laravel)

php artisan vendor:publish --tag=sentry-resolve-config
3

Configure environment

SENTRY_TOKEN=your-sentry-api-token
SENTRY_ORG=your-org
SENTRY_PROJECT=your-project

CLI commands that make Sentry manageable

From daily triage to final resolution, the CLI keeps your team in sync with Sentry without leaving the terminal.

sentry:pull

Fetch unresolved issues and generate SENTRY_TODO.md.

./vendor/bin/sentry-resolve sentry:pull --limit=10 --sort=freq

sentry:resolve

Resolve a batch of issues after fixes merge.

./vendor/bin/sentry-resolve sentry:resolve ISSUE-1 ISSUE-2

sentry:debug

Inspect current configuration and token scopes. Perfect for CI health checks.

./vendor/bin/sentry-resolve sentry:debug

sentry:test-token

Validate tokens before sharing them with collaborators.

./vendor/bin/sentry-resolve sentry:test-token <token>

Suggested dev workflow

  1. Pull issues at stand-up: run sentry:pull and review SENTRY_TODO.md together.
  2. Fix & test locally: each issue links back to Sentry for context, so developers can iterate fast.
  3. Resolve post-merge: once patches deploy, mark the batch resolved with sentry:resolve.
  4. Audit logs: use the built-in rotating logs to track who resolved what and when.

Built for developer happiness

Sentry Resolve removes the friction of context switching between dashboards and the CLI. Automate the busywork, keep your focus on impactful fixes, and leave production untouched until you are ready to ship.

Why dev-only?

The package automates corrective actions and writes diagnostic logs. Keep it confined to development, staging, or dedicated maintenance servers where you orchestrate Sentry clean-up without risking production throughput.

FAQs

Does this replace the Sentry dashboard?

No. It complements the dashboard by scripting common maintenance flows so you can stay in your terminal.

Can I automate with CI?

Yes! Run the CLI in scheduled jobs to enforce hygiene. Use read-only tokens for pull operations and write-enabled tokens for resolution.

Is Laravel required?

Not at all. Laravel users get an artisan integration, but the CLI works in any PHP project.

Where do I report issues?

Open a ticket on GitHub Issues or start a discussion thread.