125 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-08-14
stories 158

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

NEXT.JS UNIFIES RSC RESPONSE PIPELINE, AI SDK FIXES SILENT TOOL DROPS

By RepoJournal · Filed · About Vercel · Composed from the cited sources · methodology

Next.js completed a multi-part refactor to route all RSC requests through a single NavigationFlightResponse format, eliminating hand-synced positional arrays and shared cache-write logic across the router.

The biggest wins come from Next.js consolidating response handling. Four PRs from acdlite standardized how the framework writes server responses into the client cache, converting per-segment and tree prefetches to the unified NavigationFlightResponse format [2][3][4][5]. This kills duplicate logic that had to stay in sync by hand and replaces positional arrays with the same root-anchored tree used everywhere else, cutting surface area for bugs. On the same frontier, Vercel's AI SDK shipped fixes for two silent failures: provider-defined tools were dropped without warning [7], and MCP OAuth requests omitted server-advertised scopes [8]. The SDK also wired credential brokering into the network sandbox to keep provider secrets out of agent processes [6]. Eve shipped role-aware instruction context so static rules stay in system history while dynamic ones seed sessions [9], plus a lazy botName resolver that can wait for request-scoped credentials before resolving . Chat gained message reply support across WhatsApp, Messenger, and XChat [11], mark-as-read capabilities with provider-specific behavior [12], and switched Telegram streams from native drafts to post-and-edit by default to prevent leaked previews [10].

Action items

References

  1. [1] Add a script for adopting fork pull requests (#97252) ↗ vercel/next.js
  2. [2] Unify how a response's shell and full payloads are written ↗ vercel/next.js
  3. [3] Convert per-segment prefetches to NavigationFlightResponse format ↗ vercel/next.js
  4. [4] Unify how server responses are written into the client cache ↗ vercel/next.js
  5. [5] Convert tree prefetches to NavigationFlightResponse format ↗ vercel/next.js
  6. [6] feat(harness): support request transformations in network sandbox abstraction and use it to apply credential brokering when available (#18859) ↗ vercel/ai
  7. [7] fix: provider-defined tools are silently dropped by open-responses (#18880) ↗ vercel/ai
  8. [8] fix: MCP OAuth authorization requests omit server-advertised scopes (#18818) ↗ vercel/ai
  9. [9] feat(eve): instructions - add role-aware context ↗ vercel/eve
  10. [10] fix(telegram): make native draft streaming opt-in ↗ vercel/chat
  11. [11] feat(chat): add message reply support ↗ vercel/chat
  12. [12] feat(chat): add mark as read support ↗ vercel/chat

Quick answers

What shipped in Vercel on August 14, 2026?
Next.js completed a multi-part refactor to route all RSC requests through a single NavigationFlightResponse format, eliminating hand-synced positional arrays and shared cache-write logic across the router. In total, 67 commits, 71 pull requests, and 20 releases landed.
Who contributed to Vercel on August 14, 2026?
10 developers shipped this update, including Sebastian "Sebbie" Silbermann, acdlite, Felix Arntz, ai-sdk-factory[bot], aayush-kapoor, bensabic, AndrewBarba, and benpankow, and 2 more.
What were the notable Vercel updates?
Add a script for adopting fork pull requests (#97252), Unify how a response's shell and full payloads are written, and Convert per-segment prefetches to NavigationFlightResponse format.