Several VS Code–compatible editors provide built-in language model features, but do not expose those models through the VS Code Language Model API (vscode.lm.*). As a result, extensions that rely on vscode.lm.selectChatModels cannot access available models, even though the editor itself supports chat and other LM-powered functionality.
In multiple non-Microsoft VS Code builds:
- vscode.lm is missing, stubbed, or returns no models.
- selectChatModels cannot be used by extensions.
- Built-in editor LMs are inaccessible to extensions via the standard API.
If we want to support a wider-range of users, we also need to support patterns for common VS Code-esque forks that use the open-vsx standard. This includes:
- Cursor
- VSCodium / Theia
Credit: Arjun Guha
Several VS Code–compatible editors provide built-in language model features, but do not expose those models through the VS Code Language Model API (vscode.lm.*). As a result, extensions that rely on vscode.lm.selectChatModels cannot access available models, even though the editor itself supports chat and other LM-powered functionality.
In multiple non-Microsoft VS Code builds:
If we want to support a wider-range of users, we also need to support patterns for common VS Code-esque forks that use the open-vsx standard. This includes:
Credit: Arjun Guha