Milind Daraniya

Laravel LSP in 2026: Bring Laravel Autocomplete to Neovim, Zed, and Sublime Text

Published September 19th, 2026 13 min read

Laravel has always had good support in code editors, especially when working with VS Code or PhpStorm. But in real projects, I often want to use different editors depending on the work I am doing.

Sometimes I use VS Code. Sometimes a lightweight editor is more comfortable. Some developers prefer Neovim, Zed, or Sublime Text.

The problem with Laravel is that normal PHP autocomplete is not always enough.

Laravel uses a lot of framework features such as routes, controllers, Blade views, configuration, Eloquent models, facades, and dependency injection. A normal PHP language server can understand PHP, but it may not fully understand what Laravel is doing.

This is where Laravel LSP becomes useful.

What Is Laravel LSP?

LSP means Language Server Protocol.

It is a standard way for a code editor to communicate with a language server. The language server understands the code and provides information to the editor.

For Laravel developers, the Laravel LSP adds Laravel-aware editor support.

According to the official Laravel documentation, Laravel LSP provides framework-aware features such as:

  • Code completion
  • Hover information
  • Diagnostics
  • Go-to-definition
  • Document links
  • Quick fixes
  • Laravel and Blade support

This means the editor can understand much more than normal PHP syntax.

For me, the important part is simple: the editor can understand Laravel code instead of treating it like only normal PHP code.

Why Normal PHP Autocomplete Is Sometimes Not Enough

Consider a Laravel route:

Route::get('/customers', [CustomerController::class, 'index']);

A PHP language server understands the PHP classes and methods.

But Laravel applications contain many framework-level relationships.

For example:

return view('customers.index');

The string customers.index represents a Blade view.

Laravel knows what that means.

A Laravel-aware language server can provide better information around these Laravel-specific concepts.

The same idea applies to:

  • Routes
  • Controllers
  • Blade files
  • Configuration
  • Laravel helpers
  • Models
  • Framework classes
  • Laravel-specific conventions

When working on a large Laravel project, these small improvements can save a lot of time.

Laravel LSP Is Not Another Laravel Framework

This is important to understand.

Laravel LSP is not a replacement for Laravel.

It does not change how your Laravel application works.

It is a developer tool that connects your editor with Laravel-specific knowledge.

Your application still runs normally:

php artisan serve

or through your normal Nginx, PHP-FPM, Docker, Laravel Herd, or other development setup.

The LSP mainly improves the coding experience.

Which Editors Can Use Laravel LSP?

One of the interesting things about Laravel LSP in 2026 is that it is not limited to one editor.

Laravel's current documentation mentions support around editors such as:

  • VS Code
  • Cursor
  • Neovim
  • Zed
  • Sublime Text
  • PhpStorm

The official Laravel ecosystem also provides an official VS Code extension, while the Laravel LSP can be used with other editors that support the language-server protocol.

This is useful because developers have very different editor preferences.

A Laravel developer who prefers Neovim does not have to move to VS Code just to get Laravel-aware coding support.

Installing Laravel LSP

The installation is simple.

The official documentation currently provides this Composer command:

composer global require laravel/lsp

Your Composer global vendor binary directory should also be available in your system PATH.

After installation, the editor needs to be configured to communicate with the Laravel language server.

The exact configuration depends on the editor.

This is one reason I prefer the LSP approach. The language server is separate from the editor, so the same Laravel-aware language tooling can work with multiple editors.

What Does Laravel LSP Actually Help With?

The biggest advantage is not one single feature.

It is the combination of many small features.

1. Better Autocomplete

Autocomplete is one of the first things developers notice.

Instead of remembering every available method or class, the editor can suggest relevant Laravel code.

This becomes more useful in large applications where there may be hundreds of classes, models, services, actions, requests, events, jobs, and resources.

2. Go to Definition

In a large Laravel project, I often need to jump from one piece of code to another.

For example, I may see:

CustomerService::createCustomer();

and want to immediately open the definition.

Go-to-definition reduces the time spent manually searching through folders.

When a project has thousands of files, this matters a lot.

3. Diagnostics

Another useful feature is diagnostics.

Diagnostics allow the editor to identify problems and show them while I am working.

Instead of discovering every problem only after running the application, some issues can be shown directly in the editor.

This gives a faster development loop:

Write code → see problem → fix problem → continue

4. Hover Information

Hover support is a small feature, but I use it often.

You can move your mouse over a class, method, or Laravel-related element and see additional information without opening another file.

This is especially useful when working with unfamiliar code.

5. Blade Support

Blade is one of the most important parts of Laravel applications.

A Laravel project can contain a large number of Blade files, components, layouts, directives, variables, and reusable UI sections.

Having Laravel and Blade-aware editor support can make these files easier to work with. Laravel's documentation specifically lists Laravel and Blade support as part of Laravel LSP.

Laravel LSP and AI Coding Agents

This is another interesting part of the current Laravel ecosystem.

Laravel is now putting more focus on AI-assisted development.

Laravel's current documentation includes guidance for working with AI coding agents, and Laravel LSP is positioned as part of the modern Laravel developer tooling ecosystem.

This makes sense because AI coding agents also need accurate information about the codebase.

A developer using an AI coding tool with Laravel is working with the same basic problem:

The more accurately the tool understands Laravel code, the better the development experience.

Laravel has also introduced Laravel PAO, which provides cleaner structured output for AI agents working with tools such as PHPUnit, Pest, PHPStan, Rector, and Artisan.

So I see Laravel development moving in an interesting direction.

It is not only about writing code faster.

It is also about making the development environment easier for both developers and coding agents to understand.

Laravel LSP vs Normal PHP Language Support

There is an important difference.

Normal PHP support is mainly focused on understanding PHP.

Laravel LSP adds Laravel-specific knowledge.

For example:

Normal PHP understanding

class UserService
{
    public function create()
    {
        //
    }
}

This is standard PHP and most PHP language servers can understand it.

But Laravel applications also use things such as:

Route::get(...)
view(...)
config(...)
auth()
request()

and many framework conventions that are not simply plain PHP syntax.

This is where framework-aware tooling becomes useful.

Do I Need Laravel LSP If I Already Use VS Code?

Not necessarily.

VS Code already has strong Laravel support through the official Laravel VS Code extension, which provides Laravel-specific functionality and automatic Laravel LSP support.

So the important point is not:

"Every Laravel developer must install Laravel LSP."

The important point is:

"Laravel-aware language tooling is becoming more important for modern Laravel development."

For developers using VS Code, some of this functionality may already be available through the official extension.

For developers using Neovim, Zed, Sublime Text, or another compatible editor, Laravel LSP can make the experience much closer to what Laravel developers expect from a modern IDE.

Laravel LSP Is Especially Useful for Large Projects

In my experience, tools like this become more valuable as the project becomes larger.

For a small Laravel project with ten or twenty files, manually navigating the code is not difficult.

But imagine a project with:

  • 100+ controllers
  • 300+ models and services
  • Many API resources
  • Hundreds of Blade files
  • Multiple modules
  • Queues and jobs
  • Events and listeners
  • Multiple authentication systems
  • Large Eloquent relationships

At this point, developer navigation becomes a real productivity issue.

The more code I have, the more important autocomplete, navigation, diagnostics, and framework awareness become.

Laravel LSP Is Part of a Bigger Change

Laravel 13 is continuing Laravel's yearly release cycle and has a strong focus on developer experience and AI-native workflows. Laravel 13 was released on March 17, 2026, and requires PHP 8.3 or newer.

Laravel has also introduced several other developer-focused improvements during 2026.

For example, Laravel added route metadata support, and later introduced a read-through filesystem driver for gradually moving files between storage disks without requiring an immediate migration of every file.

This tells me that Laravel is not only adding large headline features.

A lot of the focus is also on making everyday development easier.

Should Laravel Developers Try It?

I think Laravel LSP is worth trying, especially when using an editor outside the traditional Laravel IDE setup.

For someone already happy with PhpStorm or VS Code, the biggest question is whether the existing Laravel tooling already gives everything needed.

For someone using Neovim, Zed, Sublime Text, or another LSP-compatible editor, Laravel LSP is much more interesting.

The installation is simple, and the main benefit is better Laravel-aware development inside the editor.

Final Thoughts

After working with PHP and Laravel for many years, I have learned that developer tools are not just small extras.

When you work on the same project for months or years, saving a few seconds on navigation, finding definitions, understanding code, or catching a problem can add up to a lot of time.

Laravel LSP is one of those tools that may not completely change how we write Laravel applications, but it can improve how we work with them every day.