## Problem to solve Workspaces currently only work with VS Code-based workflows. While that covers the Web IDE, and eventually the connection from a desktop version of VS Code, it leaves out a significant portion of developers who don't use VS Code. More context on why we are injecting the Web IDE and only the Web IDE can be found in https://gitlab.com/gitlab-org/gitlab/-/issues/406748+ and related issues. ## Propsoal Support multiple editors for workspaces. Based on the most popular editors, we should reach broad enough coverage by supporting: - JetBrains suite (IntelliJ, Goland, PyCharm, RubyMine, etc) - Jupyter Notebook/JupyterLab - vim/SSH ## What this epic is not about This epic is about creating tooling for different editors apart from VS Code - e.g. Jetbrains, Jupyter notebooks - that we as a product will offer on SaaS to our users. Providing ability to organiztions to bring thier own tools(editors, etc.) and configure it to be injected into the workspace is part of &12475+ . Rolling out this feature is dependent on &12475+ . However the development of the capability can be done independently - e.g. figure out if we need to fork JetBrains projects or not? how can we create an image which can be injected into the workspace, etc.