You can connect to your environments using VS Code in the browser, providing a zero-install, “ready to code” experience. This guide will walk you through the setup process and provide tips for managing and troubleshooting within VS Code Browser.

VS Code Browser

​
Opening an Environment

  1. Start an environment in Gitpod

  2. Open in VS Code Browser

    • While the environment is starting, you can click the Open in VS Code Browser button on the action bar, which is possible even when the environment is not fully running yet. VS Code Browser should open in a new tab.

      Open from the Action Bar

  3. VS Code Browser will then ask you to authenticate with your Gitpod account:

    1. Click Allow when prompted to sign in to navigate to the Gitpod authentication page.

    Authentication Prompt

    1. Follow the authentication process to complete the sign-in.

    Complete Authentication Page

    1. After signing in, you will be redirected back to VS Code and the page can be closed.

Note: If you encounter any issues during the sign-in process, it may be helpful to sign out and try again.

​
Managing Your Environment

Once connected, you can manage your environment directly from VS Code in the Browser:

​
Viewing Environment Details

  • Check the status, active branch, and logs using the Environment Details panel.
  • If you closed the panel, re-open it using the Gitpod Flex: Show Environment Details command from the Command Palette.

Environment Details in VS Code

​
Accessing Commands

  • Open the Command Palette (Cmd+Shift+P or Ctrl+Shift+P) and type Gitpod Flex to view commands such as:

    Gitpod Flex Commands

  • Clicking on the remote indicator in the bottom-left corner of the window also shows a quick menu of Gitpod Flex commands.

    Remote Indicator

​
Rebuild

Rebuilding is necessary to apply changes made to .devcontainer.json, Dockerfile, or docker-compose.yml files to the container. This process ensures that your development environment reflects the latest configuration updates.

To rebuild the container, you have two options:

  1. Command Palette: Use Gitpod Flex: Rebuild Container

  2. Rebuild Prompt: VS Code detects changes and prompts

    Rebuild Prompt

While the container is rebuilding, you will be disconnected and automatically reconnected when it’s finished. You can inspect the details view to learn about the progress and inspect logs.

Rebuild Logs

​
Settings Sync

Enable Settings Sync to sync all your extensions and other preferences from VS Code Desktop in VS Code Browser, read more about over at the offical Settings Sync documentation.

​
Troubleshooting

​
Limitations

The following limitations are present in addititon to the limitations listed for VS Code Destop:

  • Trying to install any web extension, e.g. Vim, will fail.
  • It’s not possible to connect to an environment in recovery mode.
    • ✅ Workaround: Use VS Code Desktop or the Gitpod CLI to connect and fix the devcontainer.json configuration to exit recovery mode.

​
Authentication Issues

If you’re experiencing authentication issues or need to switch accounts:

  1. Use the Gitpod Flex: Sign Out command to sign out.
  2. Confirm the sign-out when prompted.
  3. You can then sign in again with the same or a different account.

​
General Issues

If you encounter unexpected problems:

  1. Check the Gitpod Flex output view for any useful information.
  2. When sharing reports with us:
    • Use Developer: Set Log Level... command to Trace, it would give us more insights. Remember to set it back to Info afterwards.
    • Use the Gitpod Flex: Export all logs command from the problematic window. This will contain all relevant logs.

Note: Be cautious when sharing logs on the internet, as they may contain sensitive information.

Was this page helpful?