spatie/flare-cli

A standalone CLI tool for Flare error tracking and performance monitoring.

0.0.1 2026-02-12 15:49 UTC

Requires

• php: ^8.4

Requires (Dev)

• illuminate/http: ^12.17
• larastan/larastan: ^3.0
• laravel-zero/framework: ^12.0.2
• laravel/pint: ^1.25.1
• mockery/mockery: ^1.6.12
• pestphp/pest: ^3.8.4|^4.1.2
• pestphp/pest-plugin-arch: ^3.0|^4.0
• phpstan/extension-installer: ^1.4
• phpstan/phpstan-deprecation-rules: ^2.0
• phpstan/phpstan-phpunit: ^2.0
• spatie/laravel-openapi-cli: ^0.0.1

MIT

• Alex Vanderbist

• cli
• monitoring
• flare
• spatie
• error-tracking

README

A command-line tool for Flare — interact with the Flare API from your terminal.

Installation

composer global require spatie/flare-cli

Make sure Composer's global bin directory is in your PATH. You can find the path with:

composer global config bin-dir --absolute

Usage

Authentication

# Log in with your Flare API token
flare login

# Log out
flare logout

Get your API token at flareapp.io/settings/api-tokens.

Commands

Every Flare API endpoint has a corresponding command. Run flare <command> --help for details on a specific command.

flare list-projects
flare create-project --field name="My App" --field team_id=1 --field stage=production --field technology=Laravel
flare delete-project --project-id=<id>

flare list-project-errors --project-id=<id>
flare list-error-occurrences --error-id=<id>
flare get-error-occurrence --occurrence-id=<id>
flare get-project-error-count --project-id=<id> --start-date=<date> --end-date=<date>
flare get-project-error-occurrence-count --project-id=<id> --start-date=<date> --end-date=<date>

flare resolve-error --error-id=<id>
flare unresolve-error --error-id=<id>
flare snooze-error --error-id=<id>
flare unsnooze-error --error-id=<id>

flare get-team --team-id=<id>
flare remove-team-user --team-id=<id> --user-id=<id>
flare get-authenticated-user

Agent Skill

This repository includes an agent skill that teaches coding agents how to use the Flare CLI.

Install

npx skills add spatie/flare-cli

Testing

composer test

Releasing a new version

1. Build the PHAR:

   php flare app:build flare --build-version=1.x.x

   This bakes the version into builds/flare. If you omit --build-version, it will prompt you (defaulting to the latest git tag).

2. Commit and push:

   git add builds/flare
   git commit -m "Release v1.x.x"
   git push origin main

3. Create a release in the GitHub UI — this creates the tag, triggers Packagist, and automatically updates the changelog.

Users install or update with composer global require spatie/flare-cli.

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Alex Vanderbist
• All Contributors

License

The MIT License (MIT). Please see License File for more information.