In our UI, you can see a nice summary of all your projects. The project list mentions the number of errors in the past 30 days and how many are unresolved. Here's how that list looks like for all projects of the Spatie team. The project names are considered sensitive information, so we've rendered them illegible in the screenshot.
We think that most users won't visit this project list too often. Most of the times, you'll use Flare and access the app to handle a specific error.
We decided to email the project overview to each user every month. This is how that mail looks like. Notice that we also include links to what's new at the Flare blog.
If you don't want to receive this monthly mail, you can opt out at your user profile page.
You can see other improvements we recently made on our changelog. Do you have an idea to improve Flare? Let us know!
Continue reading
Why we removed AI solutions from Flare
AI generated solutions are dead, long live AI generated solutions! We removed the old one-shot fixes from a model that could only see the stack trace. It simply couldn't compete with modern agentic AI. In their place, Flare works with the agentic AI tools you already use: an MCP server that handles real triage, a CLI with an agent skill, quick Copy for AI prompts in the UI and docs served as markdown. Hosted agents are in the works too.
Alex
Flare now uses OAuth for MCP, the CLI, and API
Connect MCP clients like Claude and Cursor to Flare by logging in from your browser, no more copying API tokens. Every connection gets its own permissions, so you can give your AI read-only access to a single project. The CLI signs in the same way, and new personal access tokens with scopes and expiry cover scripts and CI.
Alex
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
