Weave Code
Torch Filament Laravel Package
lara-zeus/torch-filament
A Filament plugin for Torch that brings AI chat and assistant capabilities into your Laravel admin panel. Connect providers, manage conversations, and add LLM-powered workflows to Filament resources with minimal configuration.
Infolist component to highlight code using Torchlight Engine
Frequently asked questions about Torch Filament
- What is lara-zeus/torch-filament and what does it actually do?
- It is a Lara Zeus Filament plugin that provides ready-made Filament resources and pages so you can manage Torch data inside a Filament panel instead of building custom admin screens. It plugs into Filament navigation, authorization, and styling for a consistent admin experience. Be aware that the public metadata is inconsistent: some descriptions call it an Infolist component for syntax-highlighted code via Torchlight, while others describe a broader Torch AI toolkit with providers, models, prompts, and conversations. Read composer.json and the source tree before adopting so you know which package you are actually installing.
- How do I install lara-zeus/torch-filament in a Laravel application?
- Install it with Composer using composer require lara-zeus/torch-filament, then register the plugin in your Filament panel provider. The integration is described as a panel plugin with no separate service layer to operate. Confirm whether your installed version publishes config or migrations, then clear cached config and Filament caches after registering.
- Which Laravel and Filament versions does lara-zeus/torch-filament support?
- The package targets Filament panels, and its major versions appear to be pinned in lockstep with Filament majors, meaning 3.x lines up with Filament 5. Treat PHP, laravel/framework, filament/filament, and livewire/livewire as a single validated set, because a mismatch usually surfaces as a Composer resolution failure rather than a runtime bug. Check composer.json for exact constraints before planning any Filament upgrade.
- How do I register the torch-filament plugin in a Filament panel provider?
- Add the plugin to the plugin() method of your panel provider, such as AdminPanelProvider, the same way you register other Filament plugins. Because it hooks into Filament navigation, routes, and styling, you normally do not need separate service provider wiring. After registering, clear config and route caches so the new pages appear in the panel.
- Can I customize navigation labels, groups, and routes for the Torch resources?
- Yes, the package is described as supporting configurable navigation labels, groups, and routes so the resources fit your existing panel structure. Configuration is typically done through the plugin's configuration methods or a published config file. Verify the exact option names in the source before relying on them, since the documentation is thin and the package scope is ambiguous.
- Does torch-filament respect Filament authorization and policies?
- It is designed to work with Filament authorization and policies, so access to the Torch pages is governed by the same panel gates and model policies that already protect your other resources. The package adds no meaningful authorization surface of its own beyond what Filament enforces. Make sure policies exist for the underlying models and test access with a non-super-admin user before shipping.
- Is lara-zeus/torch-filament safe to use in production?
- The blast radius is small: it is presentational, contained to one entry type or set of pages inside one panel, and easy to remove. The risks are vendor thinness (a single-maintainer ecosystem, few stars, no known dependents, and a one-line changelog for 3.0.0) and major versions pinned to Filament majors, which reopens the dependency on every Filament upgrade. Confirm that a highlighting failure degrades gracefully to plain preformatted output rather than throwing and turning the page into a 500. Pin the version and review changes before upgrading.
- Does torch-filament call a hosted Torchlight API or can it run self-hosted?
- That depends on the underlying highlighter and must be verified in the source, because Torchlight can be consumed as a hosted API or self-hosted. If it is hosted, your code snippets leave your infrastructure, an API key must be managed, rate and availability limits apply, and an outage can degrade or break page rendering. For internal admin tooling that is often acceptable, but in regulated or air-gapped environments it is disqualifying unless the self-hosted path is real and supported. Confirm this with whoever owns information security before the build-versus-buy decision.
- How do I test the Torch Filament resources in my application?
- Because there is no domain logic, persistence, or queue work described, testing is mostly Filament-level: assert that the panel registers the plugin, that routes resolve, and that pages render for authorized users using Filament and Livewire testing helpers. Add a test that covers behavior when highlighting is unavailable so you know whether the page degrades or errors. Run the suite against your exact Filament major in CI to catch compatibility drift early.
- What are the alternatives to torch-filament, or should I build custom Filament resources?
- Because the package is narrow and solves a low-differentiation readability problem, a small custom Filament resource or a custom Infolist entry is a reasonable alternative when you need full control. If the hosted highlighting dependency is a problem, you can highlight server-side with a local PHP library or simply render preformatted text. Weigh those options against the ongoing burden of a thin, single-maintainer package whose majors move with Filament.
Weaver
How can I help you explore Laravel packages today?