Synapse is a browser-based development dashboard for Laravel AI SDK agents. It discovers agent classes and lets you run the real agent in a chat playground, then inspect tool calls, replies, token usage, and errors. It is an inspection and debugging aid—not an AI model or an agent framework.
What Synapse adds to a Laravel AI SDK workflow
Laravel describes agents as the fundamental building blocks for interacting with AI providers in its SDK. An agent is a PHP class that can define instructions, conversation context, tools, and an optional output schema. Synapse provides a browser interface for discovering those classes and exercising them while developing.
As an Amazon Associate I earn from qualifying purchases.
That makes it relevant when you are already building with laravel/ai and want to shorten the loop of sending a prompt, checking how tools were invoked, and diagnosing a reply. Synapse does not replace the SDK, your provider configuration, or your agent code.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →How Synapse finds and describes agents
According to the Synapse overview, there is no manual registration step: it scans configured directories on each request. Its defaults are app/Ai/Agents, the location used by the SDK’s make:agent command, and app/Agents. You can add directories through discovery.paths and exclude named classes with discovery.ignore.
#1 Best Overall
Agent cards identify the class, provider, model, and tools. An information panel shows resolved settings, including temperature, maximum tokens, maximum steps, tool choice, the system prompt, and tool JSON schemas. This can help you check what the configured agent is set to use without manually tracing each setting through the code.
What you can do in the browser playground
The playground sends messages to the actual agent and streams its replies. The overview says it accepts image, document, and audio attachments and retains them for follow-up messages in that conversation.
Try a different model for one message
A per-message selector lets you run the next message with a different model without changing the agent class. The choice resets after you leave the page, and Synapse records the model used on the message.
Handle structured output and conversation context
For agents using structured output, Synapse runs the request without earlier messages and displays the result in a JSON card. For agents implementing the SDK’s Conversational contract, it supplies the thread from Synapse’s own stored history. According to the overview, this does not touch the application’s conversation tables. A stateless agent instead receives each message independently, as it would in production.
Rank #3
Inspect tool calls, errors, and prior replies
Tool-call cards appear in sequence and show the tool name, status, duration, arguments, and result. Provider tools, such as web search or a code interpreter, receive separate card treatment. Anthropic and OpenAI use different status terms; Synapse maps them to common pending, success, and error states, while the provider’s original status remains available on hover.
If a tool or agent throws an exception, an error card includes the exception class, message, and stack trace. The overview also describes searchable and filterable conversation history, with options to rename or replay conversations. Per-reply usage details include token counts for cache reads, cache writes, and reasoning.
Rank #4
Install Synapse and open the dashboard
The published installation instructions are:
composer require redberry/synapse --dev
php artisan synapse:install
After installation, open /synapse in the browser. The package overview says its compiled frontend ships with the package, so a separate npm build step is not required. It reads existing provider and API-key settings from config/ai.php. Laravel’s AI SDK documentation separately describes provider configuration through config/ai.php or environment variables.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Conversation storage and cleanup
Synapse stores its conversations in its own tables. The overview documents this cleanup command:
Best Value
php artisan synapse:prune --days=7
It also documents SYNAPSE_AUTO_PRUNE=true to schedule a daily prune. These details concern Synapse’s conversation storage; they should not be mistaken for the Laravel AI SDK’s own conversation storage. Review the package’s current documentation and your application’s data-handling requirements before deciding how to retain or remove dashboard conversations.
Check compatibility before adding it to a project
A Packagist result listed Synapse v0.1.4, released September 18, 2026, with requirements of PHP ^8.3, laravel/ai ^0.9|^0.10|^0.11, and Laravel Framework ^12.0|^13.0. These are a dated registry snapshot, not a promise that the same release or constraints remain current. Check the current package metadata and project documentation before installing, especially if your PHP, Laravel, or SDK version differs.
The feature and command descriptions above come from the Synapse overview; they have not been independently tested here. The available descriptions establish a development and inspection workflow, but do not establish security posture, production suitability, telemetry behavior, deployment compatibility, or privacy guarantees. Consult the current project documentation for those questions.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




