- How do I install kauffinger/livewire-chat-kit in a Laravel app?
- Install it with Composer as kauffinger/livewire-chat-kit, then publish its config and views and mount the chat component on a route in your application. You will also need to wire up your Prism provider credentials and add authorization around the chat surface. Because the repository currently ships no README, treat the source code as the public contract and read the component classes before you mount anything. The mechanical adoption is low ceremony and should be a matter of days for a proof of concept.
- Which Laravel and Livewire versions does livewire-chat-kit support?
- The package targets a modern stack: Laravel 12, PHP 8.4, Livewire 4, Flux UI 2, Tailwind 4, and Prism for LLM calls. That alignment with an existing Laravel 12 / Livewire 4 application is its strongest argument, since it avoids introducing a separate JavaScript or SPA runtime. The main caveat is that anything built against Livewire 4 inherits a fast-moving API surface, and streaming behavior has historically churned across major versions, so pin minor versions deliberately.
- Does livewire-chat-kit require Flux Pro or does Flux Free work?
- This is ambiguous from the documentation and must be verified before you write any code. The package is described only as built with FluxUI, which could mean either the free or the paid edition. If the chat components depend on Pro-only components, adopting it implies a paid per-project license plus a design constraint on your UI. Check the Blade views for specific Flux component names and confirm which edition provides them.
- Does the package ship migrations, models, and policies for conversations and messages?
- Probably not in full. The kit appears to be a UI and streaming layer rather than a complete application domain layer, which means conversation persistence, retention rules, tenancy, and quotas are likely your responsibility. Those are the real cost center of a chat feature, not the presentation components. Confirm by inspecting the package for migrations, Eloquent models, and policy classes before estimating the work.
- What streaming transport does livewire-chat-kit use?
- The supplied documentation does not state whether it streams via Livewire streaming, server-sent events, or polling. That distinction materially changes both the user experience and your infrastructure plan. Long-lived streamed responses interact poorly with PHP-FPM output buffering, reverse proxies that buffer responses, request timeouts, and worker pool sizing. Test the streaming path against your actual deployment topology, whether FPM or Octane, before committing.
- How are Prism providers and models configured in livewire-chat-kit?
- The intended integration keeps Prism credentials, model selection, and provider switching inside your existing Laravel configuration and secret management story, which is a genuine architectural advantage. What is not documented is whether providers and models are set per component, through a published config file, or hardcoded in the kit. Read the source to confirm, and avoid hardcoding model names in views if you plan to switch providers. Prism supports multiple providers, so configuration is the natural place for that decision.
- Is kauffinger/livewire-chat-kit production ready?
- Treat it as pre-adoption. Signals include roughly 54 stars, zero dependents, a single apparent maintainer, a repository name that differs from the Composer package name, and no README, API reference, or upgrade guide. There is no evidence of a second maintainer or a deprecation policy, which raises long-term maintenance risk. It is a reasonable proof-of-concept choice; for production, budget for forking or wrapping it, or evaluate building the chat surface directly on Livewire 4 and Prism.
- Can I use it for multi-tenant or scoped conversations?
- There is no evidence that the kit handles multi-tenant scoping out of the box. You will likely need to add tenant scoping yourself through your own models, global scopes, and policies around whatever conversation and message records you persist. Confirm whether the kit supports multiple concurrent conversations and multi-turn threads, since a single-thread chat surface is much less useful for support or assistant use cases. Authorization must be added explicitly regardless of what ships.
- How do I test a Livewire chat component built with this kit?
- Plan to write your own tests rather than lean on the package. Your existing stack fits well: Pest 4 and PHPUnit 12 with Livewire component tests let you assert rendering, message dispatch, and authorization on the mounted component. Mock or fake the Prism calls so streaming tests stay fast and deterministic. Also add a small integration test that exercises the real streaming transport against a staging environment.
- Does livewire-chat-kit support markdown rendering, attachments, and tool or function calling?
- This is unverified and likely bring-your-own. Prism itself supports tool and function calling, but whether the kit exposes it in the UI, and how it handles attachments, markdown output, and sanitization, is not documented. Since LLM output rendered as HTML is an XSS risk, confirm output escaping and sanitization in the Blade views before you ship. If any of these features are requirements, budget for building them on top of the kit rather than assuming they exist.