RepoJournal
Vercel

@vercel

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

Pick a date

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

The Wire · Showcase

SLACK ADAPTER GETS FINE-GRAINED CLIENT CONTROL, AI SDK FRAMEWORK SUITE ROLLS STEADY PATCHES

By RepoJournal · Filed · About Vercel

Vercel/chat ships WebClient configuration options for Slack adapters, while the AI SDK ecosystem closes SSE handling gaps and bumps dependencies across Vue, Svelte, React, and RSC frameworks.

The Slack adapter in vercel/chat now exposes webClientOptions [1], letting you configure retry logic, per-request timeouts, custom headers, and rate-limit behavior on underlying WebClient instances. This applies to both default and per-token clients for multi-workspace setups, giving you surgical control where you needed blanket configuration before. Meanwhile, @ai-sdk/[email protected] [2] patches a critical SSE handling bug that was dropping messages without explicit event fields, the kind of silent failure that makes AI integrations unreliable. The rest of the AI SDK suite rolled patches across all major framework integrations [3] [4] [5] [6], keeping the dependency graph synchronized at [email protected]. On the workflow side, the world-vercel adapter switched event endpoints to v4 wire format [7], moving from verbose shapes to length-prefixed frames with CBOR metadata, a format change that stays transparent at the public API level but cuts wire overhead. Documentation around run idempotency landed [8], finally codifying the hook-token pattern for duplicate-sensitive work that teams have been asking about.

Action items

References

  1. [1] feat(slack): expose webClientOptions to configure the underlying WebClient ↗ vercel/chat
  2. [2] @ai-sdk/[email protected] ↗ vercel/ai
  3. [3] @ai-sdk/[email protected] ↗ vercel/ai
  4. [4] @ai-sdk/[email protected] ↗ vercel/ai
  5. [5] @ai-sdk/[email protected] ↗ vercel/ai
  6. [6] @ai-sdk/[email protected] ↗ vercel/ai
  7. [7] [world-vercel] Switch event endpoints to v4 wire format ↗ vercel/workflow
  8. [8] docs: document run idempotency ↗ vercel/workflow

FAQ

What changed in Vercel on June 15, 2026?
Vercel/chat ships WebClient configuration options for Slack adapters, while the AI SDK ecosystem closes SSE handling gaps and bumps dependencies across Vue, Svelte, React, and RSC frameworks.
What should Vercel teams do about it?
Update @ai-sdk/mcp to 1.0.51 if you're building SSE-based AI integrations • Review new Slack webClientOptions for timeout and retry tuning if you maintain multi-workspace Slack bots • Read the idempotency docs for workflow run patterns before your next retry-logic PR
Which Vercel repositories shipped on June 15, 2026?
vercel/chat, vercel/ai, vercel/workflow

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.