PhpStorm 2026.3 improves Laravel workflows with agents and processes

The errors that surface too late

Laravel projects have a class of mistakes that can look perfectly fine during a visual review. A misspelled configuration key, a missing Livewire component method, or a resource route targeting an unavailable action may only fail when somebody reaches that specific path. PhpStorm 2026.3 adds inspections aimed at catching those problems in the editor before they turn into runtime failures. (blog.jetbrains.com)

The three announced inspections are Unknown config keys, Laravel routes for missing resource route methods, and Unknown Livewire component method. They do not replace tests, but they target a useful category of issues: references that look credible in a diff and are only validated when Laravel resolves them. Their practical value is reducing investigation time on small, repetitive changes. (blog.jetbrains.com)

Let the agent inspect its own changes

The important part is not limited to seeing these warnings in the IDE. With PhpStorm’s MCP server enabled, an external client can use the IDE’s analysis tools to inspect files and retrieve issues reported by inspections. That makes it possible to have an agent edit code, inspect the result, and leave the change ready for human review. (blog.jetbrains.com)

You enable it through Settings | AI | MCP Server by selecting Enable MCP Server. It is worth reviewing the tools exposed to the client, since the MCP server can analyze code, modify files, run configurations, and execute terminal commands. You do not need to grant broad permissions by default just to benefit from inspections. (jetbrains.com)

{
  "require": {
    "php": "^8.6"
  }
}

PhpStorm can also derive the language level from the php requirement in composer.json, in addition to the setting at Settings | PHP | PHP language level. This helps the IDE flag PHP 8.6 syntax or APIs when a project still needs to support an earlier version. The setting should match the PHP version used in production, not simply the newest interpreter available on a developer machine. (blog.jetbrains.com)

One place for Laravel’s supporting processes

The Laravel tool window now includes a Processes tab for long-running commands. JetBrains says it can list, start, stop, restart, and show output for processes such as the development server, queue workers, and npm dev commands. That is a practical improvement for projects where backend work, queues, and Vite usually live in separate terminal tabs. (blog.jetbrains.com)

For a project opened inside a Dev Container, or connected to a homelab machine that runs development services, keeping that view close to the code can reduce context switching. It does not remove the need for Docker, Compose, or SSH sessions; it simply makes the state and output of already running processes easier to reach. When a worker fails to start or the development server needs checking, that proximity matters more than one more terminal tab. (blog.jetbrains.com)

The fine print

These inspections depend on PhpStorm being able to understand the project, its dependencies, and its configuration correctly. They cannot guarantee that a key is valid in every environment, and they do not replace integration tests, deployed-configuration checks, or a review of actual Livewire behavior. MCP also deserves care: Run shell commands or run configurations without confirmation (brave mode) allows commands to run without asking for confirmation every time. (jetbrains.com)

The Processes panel does not turn the IDE into a production process supervisor either. It is for development processes that need observing and controlling during local or remote work, not a replacement for systemd, Supervisor, Docker Compose, or whatever orchestration runs your servers. This is a workflow improvement, not a new infrastructure layer. (blog.jetbrains.com)

A useful upgrade for context-heavy work

JetBrains Air adds a workspace for running agents and reviewing their changes next to source files and diffs. It can work with compatible agents that are already installed, but the Laravel-specific benefit is having IDE inspections available as another verification step in that loop. Agents may speed up edits, while static analysis and review remain the safeguards against accepting bad changes faster. (blog.jetbrains.com)

PhpStorm 2026.3 does not remove the need for Artisan commands or for understanding the environment where an application runs. It does provide better signals for broken references and a more convenient place to manage common Laravel processes. If PhpStorm is already part of your daily workflow, those two changes alone make this release worth evaluating. (blog.jetbrains.com)

Source: Laravel News Official documentation: PhpStorm 2026.3