AI agents are no longer just about making them smarter.
It’s about knowing what they actually did.
Laravel AI SDK 0.11 brings run-level IDs, lifecycle events, step timings, tool failure tracking, better failover, and hosted tool search.
Less black box. More production-grade AI.
Kudos to @taylorotwell and the @laravel team for pushing this forward. 🚀
#Laravel #PHP #AI
This is the kind of AI + Laravel integration that actually gets us excited.
Tackle isn’t just another AI coding assistant. It gives the agent access to the Laravel app itself, with the tools, context, and guardrails it needs to work within the application.
The “guardrails as code” part is especially interesting.
This feels like where AI-assisted development is heading.
👏 @jordankdalton
#Laravel #PHP #AI
PHP developers can now build far beyond the browser. And that’s a bigger deal than it sounds. 🚀
@nativephp is changing the conversation around what PHP can be used for.
If you already know @laravel, Blade, Eloquent, and the PHP ecosystem, NativePHP lets you take those skills into desktop and mobile application development without having to start from scratch with Swift, Kotlin, Flutter, or React Native.
For developers, here’s what actually matters:
🔹 One familiar ecosystem
You can continue using @laravel, PHP, and the tools you already know while targeting native applications.
🔹 Desktop + Mobile
@nativephp supports applications for macOS, Windows, Linux, iOS, and Android.
🔹 PHP runs with the application
This isn't simply a @laravel website opened inside a browser. @nativephp packages the application so it can run locally on the target device. For mobile, the framework is designed to run the PHP application natively on the device without requiring a web server.
🔹 Native capabilities matter
The interesting part isn't just reusing @laravel code. NativePHP provides access to platform capabilities and application features that make sense outside the traditional web environment.
🔹 Your @laravel knowledge becomes more valuable
Database access, business logic, authentication, queues, events, APIs, and the broader @laravel ecosystem don't suddenly become irrelevant when you move beyond the browser.
But there is an important distinction:
@nativephp doesn't mean “build anything native without learning anything new.”
Developers still need to understand things like:
• Offline-first behaviour
• Local storage and synchronization
• Device permissions
• App lifecycle
• Performance and memory
• Platform-specific UX
• App Store / Play Store distribution
• Security when application code and data live on the user's device
That’s where the real engineering challenge begins.
And that's exactly why I think @nativephp is interesting.
It isn't trying to make PHP replace every technology.
It's giving PHP developers another surface to build on.
For years, the default thinking was:
PHP → Web
Now the conversation is becoming:
PHP + Laravel → Web + Desktop + Mobile
Huge credit to @simonhamp, @ShaneDRosenthal, and the @nativephp team for pushing PHP into territory most of us probably never expected it to reach.
The interesting question isn't “Can PHP build native apps?”
It clearly can.
The interesting question is:
What are @laravel developers going to build with it? 👀
#PHP #Laravel #NativePHP #WebDevelopment #MobileDevelopment #DesktopApps #SoftwareDevelopment #OpenSource
Laravel 13’s PHP Attributes update may look like a small syntax improvement.
For Laravel + React + Inertia teams, it’s actually a nice step toward keeping backend and frontend contracts in sync.
Instead of:
class User extends Model
{
protected $fillable = [
'name', 'email', 'team_id'
];
protected function casts(): array
{
return [
'created_at' => 'datetime',
];
}
}
You can now keep that intent directly on the model:
#[Fillable(['name', 'email', 'team_id'])]
#[Cast('created_at', 'datetime')]
class User extends Model
{
// ...
}
That becomes particularly useful with Inertia:
return Inertia::render('Users/Show', [
'user' => new UserResource($user),
]);
interface PageProps {
user: User;
}
The flow is straightforward:
Eloquent -> Resource -> Inertia -> React
Consistent casts for dates, JSON, and enums help keep the data React receives predictable, while IDEs and static analysis can catch more issues earlier.
The important part isn’t just less configuration.
It’s having a clearer contract between the Laravel backend and React frontend.
For teams building larger Inertia applications, that’s a change worth paying attention to.
#Laravel #PHP #InertiaJS #ReactJS
Major props to our Silver Sponsor, @ucodesoft at #LaraconIN2025! 🎉
Turning bold ideas into real-world solutions🔥 Trusted by industry leaders, and now powering up this epic event.
Glad to have you on board for this incredible journey!
Shame on Modi that he refuses to declare Ram Sethu as a National Heritage Monument even though his Minister of Culture, Prahlad Patel had recommended his Ministry’s decision for to PM Modi to sign the file approving the declaration. But Modi is still sitting on the file. Why?
@drmlko25 @RailMinIndia I must say, things has changed since @sureshpprabhu left. We got a call from some one but no wheelchair. Had to visit ASM office to get it. Last time it was available right at train door. Anyways Thanks for the call.