Laravel 13: The Era of Stability and Native AI Integration

Guest: Thanks so much for having me, Alex. It’s an exciting—and frankly, a very relieved—time to be a Laravel dev right now. Guest: Oh, the room literally erupted. I think there was this collective sigh of relief from every CTO and lead dev in the audience. To answer your question—yeah, it’s legit. The promise is that if you’re on Laravel 12, you can literally just bump that composer constraint to version 13 and… that’s it. You’re done. Host: Well, let’s talk about those new tools, because that’s the "meat" of this release. The Laravel AI SDK is now native. It’s not a third-party package anymore; it’s right there in the core. For someone who hasn't played with the experimental versions, what does that look like day-to-day? Guest: It’s honestly beautiful in its simplicity. If you’ve ever sent an email or saved a file in Laravel, you already know how to use the AI SDK. It uses the same "driver" pattern. So, in your config, you can specify if you're using OpenAI, Anthropic, or even a local model via Ollama. Host: That is huge. I’ve definitely spent way too many hours fighting with LLMs just to get a consistent array back. And I love that you mentioned Ollama. Having local model support out of the box is a big deal for privacy and cost, right? Guest: Absolutely. For enterprise clients, the "your data stays on your server" argument is a game-changer. And because it’s a unified interface, you can develop locally with Ollama for free, and then flip a switch in production to use a more powerful model like Claude or GPT-4. No code changes required. It’s that "pluggability" that Laravel is famous for, just applied to the AI world. Host: Now, there is one syntax change that caught my eye, even if it is optional. We’re seeing more PHP Attributes. I saw the example of defining Eloquent models using attributes like `#` or `#`. As someone who’s used to the old protected properties, why should I make the switch? Guest: (Laughs) I’ll admit, I was a skeptic at first! I’m a "protected $table" guy through and through. But once you see it in an IDE like PhpStorm, it clicks. Attributes are much better for static analysis. Tools like PHPStan can "see" them much more easily than they can see a magic property. Host: I think that’s the "Era of Stability" theme again. "Here’s a better way, but we aren't going to force you to use it." Guest: I think we’re going to see a wave of "Smart" features. Imagine your admin panel having a "Smart Search" that isn't just looking for keywords but understands context because it's using the native AI SDK. Or Pulse giving you automated insights on *why* a query is slow, not just that it *is* slow. Host: That’s such a powerful point. It really feels like Laravel is maturing into this "industrial-grade" framework that can handle the modern web without losing that fun, expressive feeling we all started for. Guest: Honestly? Get yourself to Laravel 12 as soon as you can. If you’re on 12, the move to 13 is going to be a non-event. It’ll be the easiest major upgrade you’ve ever done. And maybe start playing with the AI SDK as a package now, so you’re ready to hit the ground running when it becomes native. Host: Great advice. Marcus, thank you so much for sharing your insights. This has been fascinating. Guest: My pleasure, Alex. Thanks for having me!