A few weeks ago, we introduced a new integration with GitHub that makes it possible to:
-
create a GitHub issue directly on a Flare error
-
associate a GitHub issue with a Flare error by mentioning a Flare URL in the GitHub issue
-
automatically resolve an error on Flare when you close the GitHub issue
-
automatically close a GitHub issue when you resolve an error in Flare
In the stream below, our developers Ruben and Freek will show you how you can use this integration and how it works under the hood.
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
