Insights
Meet the new projects overview with error trends and favourites
Up until a few days ago our projects overview only showed you the name of the project, some basic error counts and when the latest error came.
A few days ago we launched a vastly improved version of the project overview. You'll immediately notice that for each project we now display the trend of incoming error occurrences.
Here's what it looks like (screenshot taken from our own account, I've blurred out client projects).

Using the graph you can quickly see which projects are currently sending more errors than usual.
A second new feature we've introduced is the ability to mark a project as favourite. You can do that by clicking the little star icon at the end of a row in the list. When you favourite a project, it will appear at the top of the list in a separate card.
Here's what that looks like:

Of course, you can favourite as many projects as you like.
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