Docs: Missing scope of support for third-party extensions in GitLab Workspaces / WebIDE

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue
  • Start this issue's title with Docs: or Docs feedback:.

Problem to solve

GitLab does not appear to have explicit documentation detailing the support scope or limitations for third-party extensions in Workspaces. The documentation focuses on:

  • How to enable the extension marketplace - Manage extensions
  • Configuration options for administrators - Configure VS Code Extension Marketplace
  • Technical setup requirements - Configure workspaces

With no mention of scope of support for the third-party extensions, the handling of support requests for extension related issues is difficult at best.

We do have a general support statement, Out of Scope - Troubleshooting non-GitLab components, but do we still need to eliminate GitLab being the root cause for a third-party extension not working?

Proposal

Provide a statement that clearly states the scope of supportability for third-party extensions, and to what degree GitLab are committed to troubleshooting their use and interaction with GitLab components, e.g. WebIDE / Workspaces.

Who can address the issue

Product team.

Edited Jun 26, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading