The Wire · Showcase
NEXT.JS UNIFIES RSC RESPONSE PIPELINE, AI SDK FIXES SILENT TOOL DROPS
By RepoJournal · Filed · About Vercel
![ai-sdk-factory[bot]](https://avatars.githubusercontent.com/in/4315504?v=4)
10 people shipped this
acdlite
@acdlite
4 cited
dancer
@dancer
3 cited
ai-sdk-factory[bot]
@ai-sdk-factory[bot]
2 cited
Sebastian "Sebbie" Silbermann
@eps1lon
1 cited
Felix Arntz
@felixarntz
1 cited
AndrewBarba
@AndrewBarba
1 cited
aayush-kapoor
@aayush-kapoor
bensabic
@bensabic
benpankow
@benpankow
dummdidumm
@dummdidumm
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].
One email a day. Unsubscribe in one click.
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. Read a past issue →
Action items
- → Adopt the pr-adopt script for external contributions to enable deploy test coverage vercel/next.js [plan]
- → Upgrade AI SDK if using MCP with OAuth or provider-defined tools vercel/ai [immediate]
- → Review Telegram streaming config if relying on native draft behavior vercel/chat [monitor]
References
- [1] Add a script for adopting fork pull requests (#97252) vercel/next.js
- [2] Unify how a response's shell and full payloads are written ↗ vercel/next.js
- [3] Convert per-segment prefetches to NavigationFlightResponse format ↗ vercel/next.js
- [4] Unify how server responses are written into the client cache ↗ vercel/next.js
- [5] Convert tree prefetches to NavigationFlightResponse format ↗ vercel/next.js
- [6] feat(harness): support request transformations in network sandbox abstraction and use it to apply credential brokering when available (#18859) vercel/ai
- [7] fix: provider-defined tools are silently dropped by open-responses (#18880) vercel/ai
- [8] fix: MCP OAuth authorization requests omit server-advertised scopes (#18818) vercel/ai
- [9] feat(eve): instructions - add role-aware context ↗ vercel/eve
- [10] fix(telegram): make native draft streaming opt-in ↗ vercel/chat
- [11] feat(chat): add message reply support ↗ vercel/chat
- [12] feat(chat): add mark as read support ↗ vercel/chat
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&s=48 "github-actions[bot]"){kind=small}
![langchain-oss-model-profiles[bot]](https://avatars.githubusercontent.com/in/2903571?v=4&s=48 "langchain-oss-model-profiles[bot]"){kind=small}
