Framework agnostic
Use it in Laravel, Symfony, or any PHP project. The CLI ships with zero-config defaults that just work.
Everything you need to tame noisy error queues
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.
AI Workflow
Built-in detection for @programinglive/dev-workflow-mcp-server standardizes how AI assistants fix issues.
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-projectCLI 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
sentry:resolve
Resolve a batch of issues after fixes merge.
./vendor/bin/sentry-resolve sentry:resolve ISSUE-1
sentry:debug
Inspect current configuration and token scopes.
./vendor/bin/sentry-resolve sentry:debug
sentry:test
Validate tokens before sharing them.
./vendor/bin/sentry-resolve sentry:test-token
Suggested dev workflow
01
Pull issues at stand-up
Run sentry:pull and
review SENTRY_TODO.md together.
02
Fix & test locally
Each issue links back to Sentry for context, so developers can iterate fast.
03
Resolve post-merge
Once patches deploy, mark the batch resolved with sentry:resolve.
04
Audit logs
Use the built-in 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.
Why dev-only?
"Keep it confined to development, staging, or maintenance servers where you orchestrate Sentry clean-up without risking production throughput."
Frequently Asked Questions
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.
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 join the community.