In popular project and source control systems, like GitHub, you can assign a person who should take care of a particular issue.
Now you can do this at Flare as well. In our latest release we've added support for assigning an error to a user of your team.
Let's dive into a quick demonstration of how you can achieve this:
Filtering errors
To navigate through errors, you can now filter them based on the assigned users. While typing, a list of users who have been assigned is shown, with the total number of assigned errors to this user.
Additionally, there's a filter available to display all unassigned errors.
Customize your settings
Don't want to be notified when assigned or unassigned? You can tweak your notification setting too.

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