RepoJournal
Laravel

@laravel

PHP's most popular framework — Forge, Vapor, and a massive paying audience

Pick a date

  1. Sun 3 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Sun 10 may
  9. Mon 11 may
  10. Tue 12 may
  11. Wed 13 may
  12. Thu 14 may
  13. Fri 15 may
  14. Sat 16 may
  15. Sun 17 may
  16. Tue 19 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

LARAVEL AI FIXES SILENT STREAM FAILURES, ADDS GEMINI CACHE SUPPORT

By RepoJournal · Filed · About Laravel

BroadcastAgent no longer leaves users staring at loading spinners when streams fail — the framework now broadcasts errors to the frontend so clients can handle them gracefully.

Laravel AI shipped a critical fix [1] that broadcasts `stream_failed` events when the BroadcastAgent job throws an unhandled exception, finally giving frontend code visibility into stream failures instead of leaving UIs permanently loading. This pairs well with the new Gemini context cache support [2] that lets you pass previously cached content via the `cachedContent` parameter in agent provider options, cutting latency for high-frequency Gemini calls. Meanwhile, Boost patched three tooling-quality bugs [3] affecting Windows developers — mixed path separators in generated AI files and missing trailing newlines in skill file output. None of these are breaking changes, but the stream failure fix is production-ready and should be pulled immediately if you're running BroadcastAgent in queue jobs. The Gemini cache feature is a solid optimization if you're heavy on API calls. The Boost fixes are polish that matters when you're committing generated code.

Action items

References

  1. [1] Broadcast stream_failed event when BroadcastAgent job fails ↗ laravel/ai
  2. [2] Gemini context cache support via cachedContent param in agent provider options ↗ laravel/ai
  3. [3] Fix path separators and trailing newlines in install output (#790) laravel/boost

FAQ

What changed in Laravel on May 10, 2026?
BroadcastAgent no longer leaves users staring at loading spinners when streams fail — the framework now broadcasts errors to the frontend so clients can handle them gracefully.
What should Laravel teams do about it?
Update laravel/ai to pull the stream_failed broadcast fix if running BroadcastAgent • Upgrade Boost to v2 latest if you're on Windows and running boost:install • Review Gemini cache support if you have high-volume agent calls
Which Laravel repositories shipped on May 10, 2026?
laravel/ai, laravel/boost

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.