PhpStorm 2026.1 Adds Laravel 13 and Agent Tools

PhpStorm 2026.1 is here, and the headline is simple: JetBrains is treating the IDE less like a code editor and more like a control center for modern PHP work. This release adds support for Laravel 13, expands its MCP server for third-party agents, and adds quick-fixes for the PHP 8.5 pipe operator.

That mix tells you where JetBrains thinks the daily pain points are: framework drift, agent integration, and the small language features that save time when they are handled well by tooling. For Laravel teams, this is one of those updates that changes the feel of the editor more than it changes a single feature checkbox.

Laravel support gets broader, and more practical

JetBrains says PhpStorm 2026.1 adds support for Laravel 13, Livewire, Filament, Laravel Wayfinder, and packages from the staudenmeir ecosystem. That matters because Laravel projects rarely live in a vacuum anymore. A typical app now mixes routing helpers, component libraries, generated code, and package-level abstractions that need the IDE to understand context instead of guessing.

The release also improves Eloquent method handling, makes Find Usages more accurate, and adds a new Route Search UI for moving through application routes faster. If you have ever wasted time hunting for a route name buried in a large codebase, this is the kind of quality-of-life feature that pays off every day.

There is also a PHP-side update that will matter once PHP 8.5 lands in more production stacks. PhpStorm can now spot places where the new pipe operator fits and offer a quick-fix that rewrites code automatically. That is the sort of support that lowers the friction of adopting a language feature, instead of making teams wait until they have time to refactor by hand.

• Laravel 13 support is included in the IDE
• Livewire and Filament get updated support
• Route Search UI helps you jump through app routes faster
• PHP 8.5 pipe operator quick-fixes can rewrite eligible code
• Generics inference is better for callable generic types

PhpStorm’s MCP server is now useful to agents

The bigger story may be around the Model Context Protocol. PhpStorm’s built-in MCP server now exposes inspections, quick-fixes, IDE search, and IDE actions to third-party agents such as Claude Code and Windsurf. In plain English, an external coding agent can ask the IDE what it sees, then act on that information instead of working blind.

JetBrains also added a Laravel Idea MCP server integration for Laravel-specific tooling. That is important because generic agent access is useful, but framework-aware access is better. A PHP agent that understands project conventions, route metadata, and Laravel-specific helpers can make cleaner edits than one that only sees raw files.

“The future of coding is not about replacing developers, but about amplifying their capabilities.” — Martin Fowler

That quote from Martin Fowler fits this release well. PhpStorm is not trying to turn the IDE into an autonomous app builder. It is giving agents a wider set of tools while keeping the editor as the place where humans still make the final call.

JetBrains also introduced the Junie CLI beta, an LLM-agnostic coding agent with bring-your-own-key pricing. That is a notable move because it reduces lock-in. Teams can choose models and spend controls instead of accepting one vendor’s defaults.

AI features and testing updates aim at daily friction

One of the more interesting additions is Next Edit Suggestions. JetBrains says these AI-powered related changes can appear across a file without consuming AI quota. That phrasing suggests a more conservative model than a fully chat-driven workflow: the IDE recommends adjacent edits when it sees a likely follow-up change, which is often the part developers forget to make after a quick fix.

Testing and debugging also picked up useful changes. Breakpoints can now be set in non-PHP files with .ezt extensions and native path mapping support. Go to Test works better with PHPUnit’s #[UsesClass] attributes, and Pest navigation in the Test Runner has improved too. These are small details, but test navigation is one of those places where weak tooling quietly slows everyone down.

There is a project indexing optimization too. PhpStorm now detects framework-specific directories that contain generated, cached, or user-uploaded content and excludes them from indexing automatically. On bigger Laravel apps, that should reduce the amount of time the IDE spends chewing through files you do not actually want in code intelligence.

• Next Edit Suggestions can propose related edits without AI quota usage
• Junie CLI is in beta with bring-your-own-key pricing
• Non-PHP .ezt breakpoints now support native path mapping
• Go to Test improved for PHPUnit #[UsesClass] and Pest
• Auto-exclusion skips generated and cached directories from indexing

Git worktrees and frontend support fill in the rest

PhpStorm 2026.1 also gives first-class support to git worktrees. If you work on multiple branches in parallel, that is a real productivity gain. Instead of constantly stashing changes or juggling separate clones, you can keep branch-specific workspaces side by side and let the IDE understand the setup properly.

The release adds terminal completion for Git, Docker, kubectl, and custom scripts, plus smoother caret animation and native Wayland support on Linux with X11 fallback. Those are the kinds of polish items that do not make launch trailers, but they shape whether an IDE feels dependable after hours of use.

Frontend support also moved forward. TypeScript now uses a service-powered type engine by default, React gets use memo and use no memo directive highlighting, Vue 3.1.8 integration is included, Angular 21.x template support arrives, and the CSS color() function is now recognized. For teams that ship Laravel apps with modern frontend stacks, this keeps PhpStorm relevant beyond the PHP file itself.

There is one notable sunset here: Code With Me is being retired after this release and will continue as a standalone marketplace plugin. That is a reminder that JetBrains is pruning older collaboration paths while pushing harder on agent-aware workflows and IDE-native assistance.

For Laravel teams deciding whether to upgrade, the practical question is not whether PhpStorm 2026.1 has more features. It clearly does. The real question is whether your workflow is already using agents, worktrees, and newer PHP syntax enough to feel the benefit immediately. If the answer is yes, this release is worth a fast rollout on a pilot project before you push it across the whole team.

For more Laravel ecosystem coverage, see our related piece on Laravel 13.3.0 and this update on PHPantom.