RepoJournal
Vercel

@vercel

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

Pick a date

  1. Tue 5 may
  2. Wed 6 may
  3. Thu 7 may
  4. Fri 8 may
  5. Sat 9 may
  6. Sun 10 may
  7. Mon 11 may
  8. Tue 12 may
  9. Wed 13 may
  10. Thu 14 may
  11. Fri 15 may
  12. Sat 16 may
  13. Sun 17 may
  14. Mon 18 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

NEXT.JS 16.3 APP SHELLS GO STABLE, AI SDK FIXES STREAMING TIMEOUT BUG

By RepoJournal · Filed · About Vercel

The playground is live with Next.js 16.3's self-upgrading app shells, Vercel's AI SDK patched a critical timeout bug that left streams hanging indefinitely, and Claude Fable 5 hit 96% on coding evals with agent context.

The next-app-router-playground shipped a major rename aligned with Next.js 16.3's official App Shells feature [1], ditching experimental flags like `unstable_instant` and `optimisticRouting` that are now either default or removed entirely. Meanwhile, vercel/ai fixed a nasty bug where `streamText()` with `timeout.stepMs` would never abort a stalled model stream that opened but never produced content [2]. The fix mirrors the correct behavior already working in `generateText`, so timeouts now fire across all streaming modes. On the Connect front, @vercel/connect 0.2.1 [3] added a `revokeToken` API and introduced `forceRefresh` for real-time token validation [4], solving the problem where revoked-but-unexpired tokens kept working until natural expiry. The Chat SDK now routes Telegram slash commands properly [6], and vercel/functions 3.7.0 shipped an experimental WebSocket upgrade API [5] for runtime bidirectional communication. Claude Fable 5 eval results show 96% pass rate with agent context [7], running through the Vercel AI Gateway with data-retention enabled.

Action items

References

  1. [1] Update partial fallbacks -> appshell upgrading example ↗ vercel/next-app-router-playground
  2. [2] fix(ai): enforce timeout.stepMs for the whole step in streamText (#15840) vercel/ai
  3. [3] @vercel/[email protected] ↗ vercel/vercel
  4. [4] [@vercel/connect] re-validate revoked grants via opt-in validate/forceRefresh ↗ vercel/vercel
  5. [5] @vercel/[email protected] ↗ vercel/vercel
  6. [6] feat(telegram): support slash commands ↗ vercel/chat
  7. [7] Add Claude Fable 5 eval results ↗ vercel/next-evals-oss

FAQ

What changed in Vercel on June 10, 2026?
The playground is live with Next.js 16.3's self-upgrading app shells, Vercel's AI SDK patched a critical timeout bug that left streams hanging indefinitely, and Claude Fable 5 hit 96% on coding evals with agent context.
What should Vercel teams do about it?
Update next-app-router-playground references to App Shells before 16.3 final • Upgrade @vercel/ai to latest and test streamText timeouts in production • Integrate forceRefresh in Connect token flows where revocation matters
Which Vercel repositories shipped on June 10, 2026?
vercel/next-app-router-playground, vercel/ai, vercel/vercel, vercel/chat, vercel/next-evals-oss

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.