Repository navigation
Colab-server-powered language support (LSP). #214
Description
Is your feature request related to a problem?
I am frustrated when there is no support for LSP
Describe the solution you'd like to see
As now we don't have to install modules directly because colab provided out of the box directly but locally LSP does not support like we have LSP support in browser or you can say notebook running on colab website
Reacted by Asuka Minato, Doron Gold and azmain-micronet
Activity
JagjeevanAK commentedon Nov 14, 2025
Hey it looks like after disabling the pylance it is working fine
kevineger commentedon Nov 14, 2025
Hey @JagjeevanAK, thanks for filing the issue!
You're right - support for this hasn't quite landed, and adding it's been a bit tricky! But good news... it should land early next week!
The following are some nitty gritty details, which may or may not be interesting.
First, why it's tricky... Users can configure whatever language clients they want for their VS Code installation. As with the rest of VS Code, configuration is entirely up to the user! The standard out of the box config is through the defacto
Pythonextension which usesPylancefor a language client/server. This operates strictly using the running VS Code's Python sys path. For most users, that's their local computer where they're running VS Code (or the remote VS Code server they're connected to).But thankfully, Colab actually runs a language server! We're in the midst of hooking this up (can see some of the in-flight PRs landing if curious). Our language client support should satisfy/work for most folks, though it will be partial because:
numpy) are unavailable, if they aren't also installed wherever the local Pylance client is looking.[-]local LSP support for modules as models are stored remotely[/-][+]Colab-server-powered language support (LSP).[/+]JagjeevanAK commentedon Nov 17, 2025
Hey @kevineger thank you for your kind words
yangdanny97 commentedon Nov 18, 2025
Hi, we got a request to allow Pyrefly (a new language server for Python) to be used in colab - I wanted to make sure that the language server support being added here is generic and not specific to Pylance.
JagjeevanAK commentedon Nov 19, 2025
@yangdanny97 I think remote colab support will be generic and general if not wrong as current issue is that vscode and jupyter does not provide some api's so that colab team can play around it.
kevineger commentedon Nov 19, 2025
Yep, that's correct.
Colab implements a language server (see the protocol for details). Our extension will register a
LanguageClient(see VS Code docs) against it.I had hoped to wrap that work up this week, but it'll spill over to next week.
Will update this issue as things progress.
dorongold commentedon Apr 9, 2026
@kevineger, just checking in. Is there any update on this issue?
asukaminato0721 commentedon Aug 30, 2026
oh, I find a crazy way to do this. Since we have terminal
it works...