RepoJournal
Vercel

@vercel

Next.js + the Vercel platform - frontend infrastructure for the web

Keep up with Vercel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

VERCEL AI FIXES XAI PROVIDER BUGS BREAKING MULTI-STEP TOOL CALLING

By RepoJournal · Filed · About Vercel

Grok reasoning models are failing 4-12% of the time on continuation steps, and Vercel AI just shipped two fixes that surface the actual errors and stop duplicate reasoning events from tanking requests.

The XAI provider in Vercel AI was silently breaking multi-step tool calls with grok-4.3 and grok-4.20-reasoning [1]. Every reasoning summary part event fired a new reasoning-start marker, which meant when XAI split a reasoning block across multiple parts, Vercel AI sent duplicate markers that violated XAI's API contract. That's been fixed [2]. In parallel, error reporting was completely broken [3]. XAI 4xx failures surfaced as generic "Bad Request" messages while the real error detail lived buried in responseBody, making debugging impossible [4]. Now errors properly parse XAI's actual response schema and bubble up the real message. On the Turborepo side, v2.9.15-canary.3 hit a doc aliasing snag but shipped critical cache fixes [5], while the standalone Vercel CLI fixed its own update check routing [6]. The AI package is holding in pre-release mode and waiting on the next changeset merge [7].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] fix(provider/xai): dedupe reasoning-start on multi-summary-part responses to prevent xai 400s on continuations ↗ vercel/ai
  2. [2] fix(provider/xai): dedupe reasoning-start on multi-summary-part responses to prevent xai 400s on continuations (#15334) vercel/ai
  3. [3] fix(provider/xai): surface full xai error detail in APICallError.message ↗ vercel/ai
  4. [4] fix(provider/xai): surface full xai error detail in APICallError.message (#15338) vercel/ai
  5. [5] release(turborepo): 2.9.15-canary.3 ↗ vercel/turborepo
  6. [6] [FIX] Fixing a single deployment error ↗ vercel/vercel
  7. [7] Version Packages (canary) ↗ vercel/ai

Quick answers

What shipped in Vercel on May 17, 2026?
Grok reasoning models are failing 4-12% of the time on continuation steps, and Vercel AI just shipped two fixes that surface the actual errors and stop duplicate reasoning events from tanking requests. In total, 3 commits, 5 pull requests, and 11 releases landed.
Who contributed to Vercel on May 17, 2026?
3 developers shipped this update, including dancer, github-actions[bot], and Melkeydev.
What were the notable Vercel updates?
fix(provider/xai): dedupe reasoning-start on multi-summary-part responses to prevent xai 400s on continuations, fix(provider/xai): dedupe reasoning-start on multi-summary-part responses to prevent xai 400s on continuations (#15334), and fix(provider/xai): surface full xai error detail in APICallError.message.

More from @vercel

Daily updates, in your inbox

Follow Vercel

Keep up with Vercel in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?