Download the PHP package orchestratexr/botman-chat-sdk without Composer
On this page you can find all versions of the php package orchestratexr/botman-chat-sdk. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download orchestratexr/botman-chat-sdk
More information about orchestratexr/botman-chat-sdk
Files in orchestratexr/botman-chat-sdk
Package botman-chat-sdk
Short Description Drop-in chat-widget UI and multi-channel adapter framework on top of the Laravel AI SDK.
License MIT
Homepage https://github.com/AccessVR/SuperBotMan
Informations about the package botman-chat-sdk
SuperBotMan
A Laravel package that gives any host app a drop-in chat-widget UI plus a thin multi-channel adapter framework on top of the Laravel AI SDK.
SuperBotMan is the evolution of the prior orchestratexr/botman-chat-sdk package. The widget UI carried over; the LLM back-end (previously a hand-rolled BotMan + LLPhant integration) has been replaced by laravel/ai. See CHANGELOG.md for the full break-down — anything BotMan- or LLPhant-related is gone.
What you get
- A bundled Vue chat widget (beacon + popup/docked iframe) that drops onto any Laravel page with one Blade directive.
- A
Channelabstraction so the same agent code can serve the Web widget today, and Slack / Discord / your-transport-of-choice tomorrow, without the agents needing to know. - An
AgentRegistryso registering an agent and getting auto-mounted routes (POST endpoint, conversation list/show/delete) is three lines in yourAppServiceProvider. - A CLI (
php artisan super-botman:chat {slug}) for testing a registered agent end-to-end without a browser, complete with--continue/--conversation-id/--systemflags.
What it isn't
- Not an LLM framework. Agents, tools, providers, structured output, streaming — all of that is
laravel/ai's job. SuperBotMan is the integration shell around it. - Not opinionated about persistence. Conversation history lives in
laravel/ai'sagent_conversations/agent_conversation_messagestables. SuperBotMan just exposes them through HTTP endpoints the widget understands. - Not a multi-tenant agent marketplace. It's a tool for the host app's own developers to wire up agents. There's no UI for end-users to register their own.
Installation
Publish the package's config, views, and built JS/CSS assets, then run migrations:
Add an Anthropic (or other Lab provider) key to your .env:
The 3-line host-app integration
Drop these in AppServiceProvider::boot():
That auto-registers:
| Method | URL | Purpose |
|---|---|---|
POST |
{mount}/chat |
Agent endpoint (the widget posts here) |
GET |
{mount}/chat/conversations |
List the current user's conversations |
GET |
{mount}/chat/conversations/{id} |
Fetch a conversation's messages (for resume) |
DELETE |
{mount}/chat/conversations/{id} |
Delete a conversation |
{mount} defaults to /chat and is configurable in config/super-botman.php.
Drop the widget onto any Blade page:
Define your agent as a normal laravel/ai Agent class:
Customizing user identity
Most apps will want to override how SuperBotMan identifies the visitor — for naming the echo channel, for scoping conversation history, and for telling laravel/ai which user owns the conversation. Extend the default configurator and bind your subclass:
If your User model uses a non-standard primary key column, that's already handled — SuperBotMan wraps the user in a ConversationParticipant adapter before handing it to the SDK.
Anonymous visitors
Two patterns are supported out of the box:
- Your app already authenticates every visitor as a real
Userrow (e.g. an "Anonymous User" account that unauthenticated sessions get). OverrideagentUser()to returnAuth::user()and you're done. SuperBotMan never touches its own anonymous table. - Your app has no anonymous-user concept. The default configurator will get-or-create a row in
super_botman_anonymous_userskeyed by a session UUID and return that. When the visitor signs in, your app can run a "claim" step to reassign theiragent_conversations.user_idfrom the anonymous row to the real user (helper to follow).
The Laravel AI SDK requires agent_conversations.user_id to be non-null and reference a real Authenticatable; this design is the workaround.
Multi-channel
The package ships only WebChannel today. To add Slack / Discord / etc., implement OrchestrateXR\SuperBotMan\Contracts\Channel:
Then register an agent with that channel:
The same agent code runs over either transport.
Configuration
config/super-botman.php (after publishing) covers the widget's appearance + the route mount prefix. The agent registry — which agents exist, what URL they live at, what channel serves them — is populated by your code calling SuperBotMan::registerAgent(...), not by config.
Testing
Contributing
See CONTRIBUTING.
Security
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
Credits
- Aaron Collegeman
- All Contributors
License
The MIT License (MIT). See LICENSE.
About OrchestrateXR
OrchestrateXR is the easiest way to create and deploy XR content. Use your web browser to create for mobile, tablets, PCs and XR devices.
All versions of botman-chat-sdk with dependencies
illuminate/auth Version ^11.0|^12.0
illuminate/contracts Version ^11.0|^12.0
illuminate/database Version ^11.0|^12.0
illuminate/http Version ^11.0|^12.0
illuminate/routing Version ^11.0|^12.0
illuminate/support Version ^11.0|^12.0
illuminate/view Version ^11.0|^12.0