Prompting an agent with Laravel AI is already easy:
$response = (new ResearchAgent)->prompt('Research our competitors and write a brief.');
That is the engine. It talks to the model, runs the tool loop, and hands you a response.
The trouble starts when the work does not fit in one request. Say the agent has to read fifty pages, call a few APIs, write a document, and get sign off before publishing. While it runs, any of this can happen:
- Someone closes the browser and comes back after lunch.
- A deploy restarts the queue worker mid run.
- A rate limit forces a retry ten minutes later.
- The publishing tool succeeds, then the worker dies before recording that it did.
- The agent pauses for approval and gets an answer the next morning, from a different process.
- The frontend drops the connection after event 42 and needs the ones it missed.
- The run passes its cost ceiling and has to stop without corrupting anything.
Laravel AI covers a lot of ground already: agents, conversations, tools, streaming, queues, approvals, sub agents, MCP, structured output, and provider abstraction. What it deliberately leaves alone is the runtime that owns the whole lifecycle of that work.
So every application ends up writing the same layer. Session and run tables. Queue orchestration and execution locks. Status transitions and audit history. Stream persistence and reconnect logic. Approval endpoints and continuation jobs. Checkpoints, crash recovery, tool idempotency, cancellation, budgets, usage accounting, artifact storage, tenant isolation, redaction, and the commands to inspect all of it.
Clutch is that layer, written once.
| Question | Answered by |
|---|---|
| Which model should answer this prompt? | Laravel AI |
| Which tools can the model call? | Laravel AI and your application |
| What conversation context does the model get? | Laravel AI |
| Who owns the run after the HTTP request ends? | Clutch |
| What happens when the browser or worker disconnects? | Clutch |
| Has this tool already performed its side effect? | Clutch |
| How does an approval resume in another process? | Clutch |
| What happened, in what order, and at what cost? | Clutch |
Laravel AI runs the agent. Clutch is the harness that keeps it running safely across requests, workers, and deploys. It is not another model abstraction or agent framework, and it is built on Laravel’s own queues, events, broadcasting, storage, policies, database, container, and testing fakes.