Ehsan Bagherzadegan
Back to articles
7 min read

PhpStorm 2026.3: Agent Workspace, PHP 8.6 Support, and Laravel Inspections

PhpStorm 2026.3 introduces Air — an integrated workspace for AI coding agents — plus full PHP 8.6 support, new Laravel inspections, a Processes tab for background services, and major type inference improvements.

PhpStorm 2026.3 arrived on November 6 with the most significant update for PHP developers in recent memory. The headlining feature is Air, a dedicated workspace for AI coding agents that runs inside the IDE. But the release also brings first-class PHP 8.6 support (GA November 19), new Laravel inspections, a Processes tab for managing background services, and substantial type inference improvements.

If you write PHP for a living, this release changes daily workflows in ways that go beyond incremental polish.

Air: An Agent Workspace Inside the Editor

Air is PhpStorm's answer to the question: what does an IDE look like when AI agents are first-class collaborators rather than chat sidebars?

You open Air from the right-hand tool window. It spawns a persistent session where you can connect any supported agent — Claude Agent, Codex, Gemini, Copilot, Junie, or OpenCode. The agent gets its own editor tabs: project files, diffs, and inline comments all open side by side with your code. When an agent proposes a change, you see a diff in an editor tab, not a floating overlay. You can edit the diff directly, accept it, or send inline comments back to the agent without leaving the keyboard.

This is a meaningful shift from the "chat panel + apply patch" loop. The agent's context — open files, recent diffs, terminal output — stays visible and navigable. You can run tests, inspect the database, or search the codebase while the agent works, and the agent sees those actions in real time.

PhpStorm does not ship its own agent. You bring your API keys and choose your provider. The bundled php-runtime-tools skill gives connected agents access to your project's PHP interpreter, so they can run syntax checks, execute scripts, and verify refactorings against the actual runtime.

PHP 8.6 Support: Ready for November 19

PHP 8.6 reaches GA on November 19, and PhpStorm 2026.3 ships with full support out of the box. The highlights:

  • Migration inspections flag code that will behave differently or error on 8.6, with quick-fixes to update it.
  • Readonly property defaults are now recognized and completed. You can write public readonly string $status = 'draft'; and the IDE understands the default.
  • New function completion covers clamp(), grapheme_strrev(), and the Time\Duration class.
  • Partial function application (fn($x) => strlen($x) > 5 ? ...) gets proper type inference and parameter completion.
  • SortDirection enum and function parameter doc comments (/** @param Type */ $param) are fully supported.

The migration inspections are particularly valuable for teams upgrading multiple applications. They catch issues like the new session security defaults (session.use_strict_mode=1, session.cookie_httponly=1, session.cookie_samesite=Lax) that may break existing login flows if you're not prepared.

Laravel: Three New Inspections and a Processes Tab

Laravel developers get three new code inspections that catch real bugs before they hit production:

  1. Unknown config keys — config('app.unknown_key') now warns if the key doesn't exist in any loaded config file.
  2. Missing resource route methods — If you define Route::resource('posts', PostController::class) but the controller lacks index, create, store, etc., PhpStorm flags the gaps.
  3. Unknown Livewire component methods — Calling $this->nonExistentMethod() in a Livewire component now triggers an inspection.

These are the kinds of typos and omissions that previously surfaced only at runtime or in code review. Having them in the editor saves a round trip.

The Processes tab (View → Tool Windows → Processes) is a quality-of-life addition that feels overdue. It lists running queue workers, php artisan serve, Vite, and other background processes started from PhpStorm. You can stop, restart, and view output without hunting for terminal tabs. For projects running Octane, Horizon, or Reverb alongside the dev server, this single pane replaces three or four terminal windows.

Type Inference: Generics, Callables, and Array Shapes

The type inference engine received a deep update that matters most when you work with modern PHP codebases using generics, callables, and complex array shapes.

  • Generics on classes and interfaces now propagate through more contexts — return types, method chains, and nested generic types resolve correctly.
  • Callable signatures in PHPDoc (@param callable(string): int $callback) are understood and enforced.
  • Array shapes (array{id: int, name: string}) infer keys and types through assignments, array_merge, and spread operations.
  • @param-closure-this lets you document the $this context inside a closure passed as a parameter.
  • Generic factory returns — static::create() on a generic base class now resolves to the concrete child's type parameters.
  • Spread-operator arrays ([...$a, ...$b]) preserve key types when the operands are shaped arrays.

If you run PHPStan at level 8 or 9, you'll notice fewer "PhpStorm knows but PHPStan doesn't" (and vice versa) discrepancies. The two tools are converging on a shared understanding of PHP's type system.

Git Worktrees: Local Config Comes Along

Git worktrees let you check out multiple branches simultaneously — essential for reviewing PRs, hotfixes, or parallel features. PhpStorm 2026.3 now copies your local .idea configuration (run configurations, inspection profiles, file colors, custom scopes) into new worktrees automatically.

Open a PR in a worktree, and your debug configuration for php artisan test --filter=Feature/AuthTest is already there. No re-creating run configs, no stashing changes to switch context. The worktree feels like a true parallel workspace, not a bare checkout.

Terminal Rebuilt on libghostty

The built-in terminal now runs on libghostty, the same engine that powers the Ghostty terminal emulator. The practical differences:

  • Shortcuts work reliably (no more Ctrl+L fighting with the IDE).
  • Emoji and complex glyphs render correctly.
  • ANSI styling and true color support are complete.
  • Tabs can be dragged out of the terminal tool window into the editor area as full tabs — useful for keeping a tail -f storage/logs/laravel.log pane next to your code.

Freeze Fixes and WSL Improvements

JetBrains moved several blocking operations (indexing, file system scans, VCS status) off the UI thread. The result: fewer "PhpStorm froze for 10 seconds" moments on large codebases. Automatic error reporting is enabled by default (opt-out in Settings → Appearance & Behavior → System Settings → Error Reporting).

WSL development got a streamlined setup flow. PhpStorm now auto-detects PHP binaries inside WSL distributions and configures zero-config Xdebug with a single click. Remote development over SSH includes a "light mode" that lets you start editing immediately while the full backend indexes in the background.

When to Upgrade

Upgrade today if:

  • You use AI coding agents daily — Air changes the ergonomics materially.
  • You're planning a PHP 8.6 upgrade in the next month — the migration inspections alone justify the update.
  • You run multiple background processes (queue workers, Vite, Octane, Reverb) and want a single pane to manage them.
  • You use Git worktrees for PR reviews or parallel features.

Hold off if:

  • You're on a stable 2026.2.x and none of the above apply. The core editing experience hasn't changed.
  • Your team standardizes on a specific PhpStorm version for consistency — coordinate the rollout.

The Bigger Picture

PhpStorm 2026.3 signals where JetBrains sees PHP development heading: AI agents as peers, not assistants; first-class framework intelligence (Laravel, Symfony, Drupal); and tooling that reduces context switching. The Processes tab and worktree config sync are small features that compound daily. Air is the strategic bet.

PHP 8.6 arrives in two weeks. Having an IDE that understands Time\Duration, partial application, and the new session defaults before you deploy is a quiet advantage.

Sources