- How do I install the Filament command palette package?
- Run composer require usamamuneerchaudhary/filament-command-palette, then register FilamentCommandPalettePlugin::make() inside the ->plugins([...]) array of your panel provider. Optionally publish the config with php artisan vendor:publish --tag=command-palette-config. There are no migrations, queues or extra services to wire up, so a staging install is typically a half-day job.
- Which Laravel and Filament versions does this package support?
- It requires PHP 8.2+, Laravel 11 or 12, and Filament v5. That Filament v5 constraint is a hard gate: if your panels are still on Filament v3, the package is a non-starter today. Check your composer.lock for the installed filament/filament major before you commit to adoption.
- Can the palette search Eloquent records and resource actions, or only navigation?
- The README documents navigation items plus your own custom commands, while the package blurb also claims fuzzy search across records and actions. Treat the README as the spec and read the source before promising record search to stakeholders. If record results do exist, confirm every result path is policy-gated and tenant-scoped, otherwise restrict the palette to navigation-only until patched.
- How do I add custom commands to the command palette?
- Define entries in the custom_commands array in config/command-palette.php, each returning a CommandItem object via a closure. This is the documented extension point for things like "Create user" or links to external tools. Because they are user-defined, keep the list short and label each item clearly so results stay scannable.
- Why do my custom commands break after running php artisan config:cache?
- Laravel's config caching cannot serialize closures, and custom_commands expects closures that return CommandItem objects. A deploy that runs php artisan config:cache can therefore fail or silently drop your commands. Register custom commands from a service provider at runtime instead, and add a CI step that runs config:cache to catch the break early.
- How do I change the Cmd+K or Ctrl+K keyboard shortcut?
- The package ships configurable key_bindings, so you can rebind the palette away from the default mod+k. Pick a convention that does not collide with Filament's own global search or with browser and OS shortcuts, then document it in your admin onboarding. Also set include_publish_views_command to false in production so end users cannot trigger the publish-views action.
- Can I register the palette on a single Filament panel, for example admin only?
- Yes. The plugin is registered per panel in that panel's provider, so you can enable it on the admin panel and leave a customer-facing panel untouched. You can also register it conditionally, for example only when the current user has a given role. No global middleware or shared UI layer is required.
- Is it safe to use with multi-tenancy and Filament policies?
- Only if every result path is authorization-aware. A palette that surfaces records or actions a user cannot open is an ACL leak and a compliance finding, so review the source before adoption. Confirm that results respect policies and tenant scoping; where they do not, limit the palette to navigation and custom commands you control.
- Can I customize or translate the palette's Blade views?
- The Blade views are publishable, so you can restyle the modal and adjust markup to match your panel. There are no documented i18n hooks, so strings are likely hardcoded; wrapping them in trans() after publishing is roughly a day of work for a non-English admin. Cache the views and config in your deploy pipeline once you have customised them.
- How actively is this package maintained, and what are the alternatives?
- It is MIT-licensed with a low star count and a single-maintainer signal, so treat it as a buy-not-build shortcut with an exit plan. Filament major-version churn, not feature work, is its dominant maintenance axis, so budget time for upgrade breakage each cycle. If upstream stalls, fork it into your own namespace rather than building a Spotlight palette from scratch, which is typically two to four weeks of design, frontend and accessibility work.