In our previous post we introduced the Flare CLI. Today we want to highlight one of its most powerful features: the AI agent skill.
With a single command, you can give AI coding agents like Claude Code, Cursor, or Codex direct access to your Flare data:
flare install-skill
That's it. No MCP server to configure, no separate processes to manage. The skill file gets added to your project and your agent picks it up automatically.
Once installed, your agent can look up errors, analyze stack traces against your local code, triage and resolve issues, and review performance data for your routes, jobs, and queries, all without you leaving the terminal or copy-pasting from a dashboard.
It works the other way too. Ask your agent to review the performance of your app, and it'll pull in the data from Flare and give you actionable suggestions.
Install the Flare CLI, run flare install-skill in your project, and see what your agent can do with it.
Continue reading
One core, many clients: the new Flare JavaScript client architecture
We recently reshaped the Flare JavaScript client from a single browser library and a few thin framework specific packages into a small family of packages built on a shared, platform-agnostic core. This post explains why we did it, what the core package exposes, how the browser and Node SDKs are built on top of it, why the React, Vue, and Svelte packages sit one level higher, and how anyone can use the same core to write a Flare JS client for a platform we do not ship ourselves.
Dries
Logging is here!
Logging is now available for all Flare users! Send any log from your app to Flare and use our polished interface to filter and search your logs in real-time.
Jimi
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
