Weave Code
Laravel Loop Filament Laravel Package
kirschbaum-development/laravel-loop-filament
Filament panel integration for Kirschbaum's Laravel Loop package. Adds admin resources so you can browse, run, and manage your Loops directly inside Filament, with tables, forms, and actions wired up out of the box. Drop it into an existing panel for visibility into Loop activity without writing cus...
Filament MCP Server for Laravel Loop
Frequently asked questions about Laravel Loop Filament
- What is kirschbaum-development/laravel-loop-filament?
- It is a Filament panel integration for Kirschbaum's Laravel Loop package. It registers admin pages and components so you can browse, run, and manage Loops inside an existing Filament panel, with tables, forms, and actions wired up out of the box. It is a thin presentation-layer adapter over laravel-loop and does not add agent logic itself.
- How do I install laravel-loop-filament?
- Install it with Composer into a Laravel application that already has laravel-loop and Filament installed. Then register the plugin on your Filament panel and publish the config. Because it is a bridge package, adopting it on a stack that does not already host both dependencies pulls in a second framework and inverts the buy-versus-build math.
- Which Laravel and Filament versions does laravel-loop-filament support?
- The package targets Laravel applications using laravel-loop and Filament, and release 0.1.5 is described as a Filament v4 dependency-compatibility patch. The exact constraint shape is ambiguous: it may widen to allow v3 and v4 or hard-bump to v4 only. Check composer.json and run composer why-not on your project before committing to an upgrade.
- Does laravel-loop-filament work with Filament v3?
- Only if the 0.1.5 constraint is a widened disjunction like ^3.0|^4.0 rather than a hard ^4.0 bump. Filament cannot install two majors at once, so a hard bump drops v3 support mid-0.x and forces a co-upgrade. Verify with composer why-not on a v3 project and pin to an earlier tag if needed.
- How do I register laravel-loop-filament on a Filament panel?
- Register the plugin in your target Filament panel's provider configuration, then publish the package config. That config covers navigation group, icons, labels, and authorization behavior, and the underlying pages are standard Filament resources you can override. Run a panel smoke test afterward to confirm the pages, tables, and agent-triggering actions appear as expected.
- Is laravel-loop-filament safe for production use?
- At 0.1.x there is no compatibility promise and no LTS, and a patch release may legitimately carry a breaking constraint change. It is acceptable for internal operator tooling recorded as an accepted risk with a named owner. It is not appropriate for SLA- or compliance-bearing surfaces, and you should pin versions and review every tag.
- How do I restrict who can run Loops in the Filament panel?
- Use Filament panel scoping together with policies and gates on the pages and on any agent-triggering actions. This is a security control rather than a nicety, because Loops can invoke tools with side effects. Restrict the plugin to admin panels and verify permissions on run actions before exposing it to operators.
- Can I use laravel-loop-filament without a Filament admin panel?
- No. It is a Filament presentation layer, so it is off the critical path for headless Loop usage, queued jobs, API-only agents, or non-Filament admin tooling. On those stacks you should decline it without further analysis rather than adopting it because it is inexpensive.
- How much work is the 0.1.5 upgrade?
- Budget roughly half a day per application for a validated upgrade: a constraint edit plus a panel smoke test. The release is described as having no product-facing change, but the real unknown is whether the Filament constraint widened or narrowed. If it is a hard v4 bump, the work becomes a co-upgrade with the rest of your Filament plugin tree.
- Is laravel-loop-filament actively maintained, and what are the alternatives?
- It comes from a boutique agency with a small contributor base and no stated support window, so treat every tag as reviewable and pin accordingly. The main alternative is building custom Filament pages against laravel-loop yourself, which is exactly the recurring request this package removes. Because the adapter is small, vendoring or forking it is a realistic contingency that caps the downside.
Weaver
How can I help you explore Laravel packages today?