-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[vscode] Implementation of the Chat and Language Model APIs #13777
Comments
Hi, any news on this issue? Will this be planned in the near future? Would be awesome to have an implemention. =) |
Hi @chbo123456, we are currently in the process of implementing AI within Theia (see #14119 and #14048). |
Thanks @rschnekenbu , I checked out the new theiaai features, quite awesome! Does this mean that I don't really need e.g. the official github copilot plugin anymore, if I want to use the "Codex" Model (aka github copilot) or did I missunderstand the new abilities and "only" standard openai/ollama models are usable here? In the end, I don't really need the vscode API, as long as I could make use of github copilot, that's why I'm asking. |
GitHub Copilot isn't really supported by Theia. The only way to download the extension is via the official VS Code marketplace, which prohibits installation of any downloaded extension into any app that isn't officially distributed by Microsoft (i.e. Desktop VS Code or GitHub CodeSpaces). Even though it might be technically possible to support the extension in Theia, we won't do so due to the Terms of Service/licensing issues mentioned above.
The Theia AI integration doesn't limit you to any specific models - we support any model provider that supports either the OpenAI API (i.e. VLLM) or Ollama. Those can be hosted by OpenAI themselves, or any other party that offers a OpenAI compatible API (so essentially everyone, you can even spin this up locally). AFAIK this issue here in particular is about contributing the VS Code API to support extensions that use the language model API. |
As these interfaces have been stubbed with #13756, this issue tracks the implementation of these APIs.
The text was updated successfully, but these errors were encountered: