Insights
You can now give team members access to specific projects
On most projects, you're probably not working alone. That's why Flare has been team-based from day one. Everybody invited to your team on Flare can see all the projects you have in your account.
For small teams, this mostly works fine. When you have a bigger team, people often don't need access to all projects in your Flare account but only a few specific ones they are working on.
That's why we've now added the ability to give team members access to specific projects. In the team settings, you can specify which projects each of your team members should be able to see.

Remember that Flare, as an error tracker, contains potentially sensitive information. So it's also good practice to only expose that information to people who really need to see it.
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