VS Code sessions

Posit Workbench allows you to launch VS Code sessions from the home page via the Job Launcher, if configured. Users can start VS Code sessions that allow them to work with VS Code while still working within the administrative framework provided by Posit Workbench, such as authentication, PAM session management, etc.


Before VS Code sessions can be launched, the Job Launcher must be setup correctly. For more information, see the Job Launcher section.


Posit is not affiliated with Microsoft. Your usage of the open source code-server and VS Code are subject to their respective licenses: see code-server license and vscode license.

Posit Workbench extension

VS Code sessions are intended to be used with the Posit Workbench VS Code extension installed. The extension provides users with a button to open the Posit Workbench homepage in a new tab. Because VS Code sessions are running remotely, any web server a user may be developing, such as Shiny, Dash, or Streamlit, will also be running remotely. The Posit Workbench VS Code extension allows users to access these remote web servers through their browser. If the extension is not installed, VS Code sessions will launch but without the additional features; users working on these types of apps will not be able to access the servers they are running on.

Additional VS Code extensions

In addition to the Posit Workbench VS Code extension, there are a variety of VS Code extensions that can improve the user’s development environment. Extensions offer a variety of additional functionality such as additional languages, debuggers, themes, and tools to support the development workflow.

Normally extensions are managed by a user who installs them through an extension marketplace onto their desktop. For Posit Workbench, you need to decide if users will be able to install extensions themselves, or if you will provide a global installation of extensions. User installation of extensions provides the most flexibility and is consistent with a user’s VS Code desktop experience. However, if Posit Workbench will be in a restricted or airgapped network, admins may need to install extensions globally for users.

The default configuration will allow users to manage their own extensions. If a global installation directory is desired it can be configured using the VS Code install script or through the VS Code configuration file. See General installation for details.

Regardless of the extension installation directory, administrators can configure a list of extensions that should be installed for all users. See Pre-Installing VS Code extensions.