We've just released the Flare CLI: a command-line tool that lets you manage your errors, projects, and performance data without ever leaving your terminal.
You can install it globally via Composer:
composer global require flareapp/flare-cli
After authenticating with your API token, you get access to all the things you'd normally do in the Flare dashboard: triaging and resolving errors, viewing occurrence details, browsing performance metrics for your routes, jobs, queries, and more.
flare errors:list
flare errors:show {id}
flare errors:resolve {id}
flare performance:routes
The CLI was built almost entirely from our OpenAPI specification using our latest package: spatie/laravel-openapi-cli. My colleague Freek share more about that process in a separate post on his blog. The result is a tool that stays in sync with our API automatically.
One thing we're especially excited about: the CLI also ships with a skill for AI coding agents. That means tools like Claude Code can access your Flare data directly, helping you investigate and fix errors without switching context. We'll dive deeper into that in an upcoming post.
The Flare CLI is available now. Give it a spin and let us know what you think.

Continue reading
A minimal "Last used" login option indicator with Alpine.js
Flare's login page now remembers which sign-in option you used last time. Built on Alpine's $persist plugin and just about 25 lines of code.
Alex
How Flare handles Livewire v4's single file components
Single file components are a great addition to Livewire v4, but their compiled output makes debugging harder. Here's how we taught Flare to map hashed file paths and line numbers back to your actual source files.
Ruben
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates