PhpStorm 2026.3: Air Agents, Laravel Checks, PHP 8.6

· PhpStorm, Laravel

Table of contents

JetBrains shipped PhpStorm 2026.3 this week, and it is the release where the IDE openly reorganises itself around coding agents. There is a new agent workspace called Air, Laravel inspections that agents can call through PhpStorm's MCP server, a bundled skill that gives agents the right PHP binary, and PHP 8.6 support just ahead of the PHP 8.6 release later this month. I use PhpStorm every day on Laravel and Magento projects, so here is what changes in practice, based on JetBrains' notes and Laravel News' summary, and what I'd turn on first.

Air: coding agents inside the IDE

Air is a workspace for running coding agents next to your code. It works with Claude Agent, Codex, Gemini, GitHub Copilot, Junie, OpenCode and other agents that speak the Agent Client Protocol (ACP), and it detects the agents already installed on your machine.

  • Your existing subscriptions work. Provider subscriptions, API keys and custom base URLs are supported; a JetBrains AI subscription is not required. A free Junie Lite configuration only needs a JetBrains Account.
  • Sessions, files and diffs sit side by side in editor tabs, instead of in a chat panel squeezed into a corner.
  • Review comments go back to the agent. You can attach a note to a specific line of a diff and send it to the agent, which is how code review should work with an agent.

That last point is the one I care about. The weak spot of agent workflows, as I wrote in my practical AI coding workflow, is reviewing what the agent produced. Line comments on a diff make that review faster and more precise than re-explaining things in a chat.

New Laravel inspections and the Processes tab

Three new inspections target mistakes that usually only show up at runtime:

  • Unknown config keys: a config('services.stripe.secrett') typo is flagged in the editor.
  • Missing resource route methods: a Route::resource() pointing at a controller without the matching methods.
  • Unknown Livewire component method: a wire:click calling a method the component doesn't have.

The Laravel tool window also gets a Processes tab that lists, starts, stops and restarts long-running processes such as the dev server, queue workers and npm run dev, with their output. For anyone who keeps four terminal tabs open for artisan serve, queue:work, Vite and logs, that is a real comfort.

Letting agents check their own work

The interesting part is how these pieces connect. The inspections work in the editor and through PhpStorm's MCP server, so an agent can run them and apply quick-fixes on the code it just wrote. And 2026.3 bundles a php-runtime-tools skill that hands agents your project's configured PHP interpreter, so they stop calling a system php with the wrong version or missing extensions.

That second problem is very real on Magento projects, where the project runs PHP in Docker and the system PHP on the host is something else entirely. An agent that runs php bin/magento or the test suite with the wrong binary wastes your time and its own. To try it:

  1. Enable the MCP server in PhpStorm's settings.
  2. Check that the project's PHP interpreter (local, Docker or WSL) is the one configured under PHP.
  3. Point your agent at PhpStorm's MCP server, and ask it to run inspections on the files it changed before it reports back.

PHP 8.6 support

PHP 8.6 is due later this November (see my PHP 8.6 overview), and PhpStorm is ready for it. Set the language level under PHP | PHP language level or through the php requirement in composer.json. For projects that still target 8.5 or earlier, PhpStorm flags 8.6-only syntax and calls to new functions such as clamp(), which is exactly what you want in a library that supports several PHP versions. There are also migration inspections and quick-fixes, and completion and type inference for the new APIs.

Other changes worth knowing

  • A new terminal built on libghostty, which JetBrains says improves shortcuts, emoji and styling in tools like Claude Code, Codex and Junie. Terminal tabs can also move into the editor.
  • Better WSL support: PHP binaries in your WSL distribution are detected, and Xdebug works with a WSL interpreter without extra network setup.
  • Remote development over SSH from inside the IDE, now using OpenSSH, with certificate authentication, hardware keys and ProxyJump.
  • Git worktrees copy your local .idea configuration and can run a setup script, handy if you give each agent its own worktree.
  • Error and freeze reports are now sent automatically. If your client contracts forbid it, turn it off under Settings | Appearance & Behavior | System Settings | Data Sharing.

Conclusion

PhpStorm 2026.3 is less about new editor tricks and more about making the IDE the place where agents and humans work on the same code. For Laravel developers, the new inspections and the Processes tab are worth the update on their own. For anyone using agents, the MCP server plus the php-runtime-tools skill is the part to try first: an agent that runs your inspections with your PHP interpreter makes far fewer avoidable mistakes. And check the data-sharing setting before you open a client project.