PhpStorm 2026.2 Ships a Laravel Tool Window and an Agent Skills Manager

JetBrains pushed out PhpStorm 2026.2, and while every release brings the usual batch of inspection tweaks and refactoring polish, this one has a couple of additions that are directly relevant if Laravel is how you pay your bills.

A dedicated Laravel tool window

The biggest addition for Laravel developers is a new Laravel tool window, a panel that lets you manage Laravel logs and deployments without leaving the IDE. If you've spent years bouncing between a terminal tab tailing storage/logs/laravel.log and PhpStorm itself, this collapses that into one place. It's a small quality-of-life change on paper, but "small quality-of-life change you use fifty times a day" tends to add up to real time saved over a project.

FileReference: making string paths navigable

The new #[FileReference] attribute marks string file paths as full IDE references for navigation and refactoring. If you've ever had a config value, a Blade view path, or a storage path stored as a plain string, you know PhpStorm has historically had no way to know that string means a file on disk. Cmd/Ctrl-click did nothing, and renaming the actual file didn't update any of the strings pointing at it.

#[FileReference] fixes that for your own code by letting you annotate exactly which string parameters or properties represent file paths:

class TemplateLoader
{
    public function __construct(
        #[FileReference] private string $templatePath,
    ) {}
}

Once annotated, PhpStorm treats that string like any other file reference: click-through navigation, "find usages," and automatic updates when you rename or move the referenced file. It's a narrow feature, but it closes a long-standing gap between "the IDE understands class references" and "the IDE understands string-based file references," which shows up constantly in frameworks that lean on convention-based paths.

PHP 8.5's pipe operator gets full support

With PHP 8.5 landing later this year, PhpStorm 2026.2 adds support for its new pipe operator, the |> syntax that lets you chain function calls left to right instead of nesting them:

$result = $value
    |> trim(...)
    |> strtolower(...)
    |> ucfirst(...);

That's functionally identical to ucfirst(strtolower(trim($value))), just read in the order the operations actually happen instead of inside-out. PhpStorm's support here means proper syntax highlighting, inspections, and refactoring support the moment your project bumps its PHP version, rather than the editor treating the new syntax as an error for a few months until tooling catches up.

An agent skills manager, right in the IDE

The most forward-looking addition is a cross-agent skills manager: a curated directory of skills for AI coding agents that you can browse, add, and manage directly inside PhpStorm. The problem this solves is a familiar one if you've used Claude Code, Cursor, or a similar tool on a Laravel project: the agent doesn't inherently know your framework's conventions, your team's testing setup, or how your specific package ecosystem is wired together, and you end up re-explaining the same context at the start of every session.

Installing a skill through the new manager persists that domain knowledge so your agents carry it across every project and session automatically, instead of it living only in your own head or a README nobody reads. For teams leaning more heavily on AI-assisted development day to day, this is the kind of infrastructure that quietly saves a lot of repeated context-setting.

Worth the upgrade?

None of these are the kind of headline feature that gets a standing ovation at a conference, but taken together they're a solid, practical release. If you're a Laravel developer using PhpStorm daily, the Laravel tool window alone is likely to earn its keep within the first week, and the agent skills manager is worth a look if AI-assisted coding is already part of your workflow. Full details are in JetBrains' official release notes and the What's New page.