Insights
You can now easily see if an error came from the web, CLI or queue
When an error comes in, it might be handy to know in which type of environment it was thrown. On each error card in our UI, you can now see the "type" of error.
This type can contain "web", "cli" or "queue". Sure, it's a small change, but we think this a useful one.
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
