pygls-v2

Migrates pygls v1 Language Servers to pygls v2 by mapping old APIs.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Da1sypetals/cutile-lsp --skill pygls-v2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pygls-v2
Source: https://github.com/Da1sypetals/cutile-lsp/tree/main/skills/pygls_v2
Command: npx skills add https://github.com/Da1sypetals/cutile-lsp --skill pygls-v2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers migrate a pygls v1-based Language Server to pygls v2 by outlining breaking changes and mapping old APIs to the new ones, reducing upgrade friction.

Core Features & Use Cases

  • Migration guidance: Step-by-step notes on adapting command methods, renamed types, and server APIs.
  • Compatibility checks: Highlights deprecated patterns to remove and new conventions to adopt when upgrading a project.
  • Use Case: When updating an existing Python LSP server, follow this Skill to align to pygls v2 and avoid common integration pitfalls.

Quick Start

Start with reading the pygls v2 migration guide and apply the changes to your codebase, renaming imports and updating function signatures as shown in examples.

Frequently Asked Questions about pygls-v2

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a Python language server from pygls v1 to v2?

Migrating a Python LSP server from pygls v1 to v2 involves mapping old APIs to new ones, removing deprecated patterns, renaming classes, and updating command methods to align with the new protocol integrations.

What are the breaking changes when upgrading a pygls language server?

Breaking changes when upgrading a pygls language server include renamed classes, updated command handling methods, and new protocol integrations that require modifying old function signatures to meet new API conventions.

Does pygls v2 support existing Python LSP servers without rewriting the codebase?

pygls v2 supports existing Python LSP servers but requires targeted codebase modifications rather than a full rewrite, specifically updating imports, removing deprecated patterns, and aligning server APIs to new signatures.

Why does my pygls v1 command handling fail after upgrading to v2?

Your pygls v1 command handling fails after upgrading to v2 because of API changes that require you to map old command methods to updated conventions and adapt function signatures to the new protocol integrations.

What is the best way to handle deprecated patterns when upgrading a Python language server?

The best way to handle deprecated patterns when upgrading a Python language server is to follow pygls v2 migration guidance to identify outdated conventions, remove them, and adopt new server API signatures systematically.