Who contributed to Laravel on August 15, 2026?

11 developers shipped this update, including mo-inkhan, filipposallemi, pushpak1300, joetannenbaum, fideloper, jackbayliss, GrahamCampbell, and xurshudyan, and 3 more.

What were the notable Laravel updates?

[BUG] [0.x] Sum streamed usage across tool-call steps in all provider gateways, [BUG] [0.x] Sum streamed usage across tool-call steps in all provider gateways (#698), and Filter partially-orphaned tool calls when replaying conversation history.

Laravel ai fixes streamed tool-call usage leaks, cloud cli plugs credential bleed · Laravel

Multi-step AI inference was silently dropping usage data from all but the final step, while the Cloud CLI was printing passwords in JSON output and breaking database restore commands entirely.

The Laravel AI package had a critical bug in streamed tool-calling: when a turn involved multiple inference steps with tool calls, only the deepest final step's usage was captured in the `StreamEnd` event [1]. Intermediate steps' usage was discarded because `HandlesTextStreaming` returned early without emitting events when delegating to `handleStreamingToolCalls()`. This fix lands across all provider gateways (Gemini, Anthropic, DeepSeek, Groq, Mistral, Ollama) [2]. A separate fix tackles partially-orphaned tool calls in conversation replay, where interrupted runs or max-step limits could leave tool results incomplete; the store now pairs calls to results one-to-one instead of by ID matching [3] [4].

Cloud CLI shipped four critical fixes. `database-cluster:update` was ignoring every option due to prefix mismatch between form keys and CLI argument names, rendering updates impossible [6]. `database-restore:create` was fataling on every invocation because a typed `Form::$errors` property had no default value [7]. Most alarmingly, credentials were leaking in JSON output: `cache:list --json` printed cache passwords in full, and other DTOs carrying secrets bypassed masking entirely [8]. The CLI also rebranded "hibernation" to "scale to zero" across all user-facing output, with backward-compatible aliases keeping scripts running [9]. Meanwhile, the built binary was locked to the hardcoded `https://cloud.laravel.com` base URL; `CLOUD_BASE_URL` environment variable is now respected [10].

On the framework side, Queue gains a `forward()` method to route jobs from one queue to another, solving the multi-site problem where queues have different names across environments [11]. Laravel now supports Guzzle 8, which brings persistent connections for PHP 8.5+ with ext-curl, exposed via `Http::globalPersistentTransport()` [12]. Process timeouts got clarity: idle timeouts and general timeouts now throw distinct exceptions so you can tell a hung process from one that just needed more time [13]. Gemini's default model bumped to `gemini-3.7-flash` [5].

MCP v1.0.0-beta.1 is a breaking change that aligns the protocol to MCP 2026-07-28, drops the initialize handshake, adds `server/discover`, and requires protocol metadata on every request [14]. The upgrade guide is live [15]. OAuth client registration shifts from Dynamic Client Registration to Client ID Metadata Documents, where your `client_id` points to an HTTPS URL describing your client instead of registering on every redirect [16] [17].

@laravel

LARAVEL AI FIXES STREAMED TOOL-CALL USAGE LEAKS, CLOUD CLI PLUGS CREDENTIAL BLEED

LIVEWIRE 3 JAVASCRIPT HOOKS EXAMPLE BROKEN IN BOOST DOCS

LARAVEL AI SHIPPING OBSERVABLE AGENT RUNS WITH FULL EVENT TRACING

LARAVEL AI FILLS THE TRANSCRIPTION GAP ACROSS GROQ, OPENAI-COMPATIBLE, AND XAIT; NIGHTWATCH SHIPS EXCEPTION FIXES; MCP CLIENT NEGOTIATES PROTOCOL ERAS

LARAVEL SHIPS QUEUE PAUSING AND VITE 3.2.0 IN OVERNIGHT PUSH

OPENHANDS PINS CLIENT DEPENDENCY, ADDS STRUCTURED ERROR HANDLING

LLAMA.CPP OVERHAULS INFERENCE FLAGS, VLLM PATCHES DEEPSEEK SPARSE MLA

DASHBOARD SEO OVERHAUL SHIPS AS PACKAGE TRAIN ROLLS FORWARD

ELIXIR CORE CUTS ALLOCATIONS ACROSS STRING AND AST OPERATIONS