8f964ea2cb
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Grace Park <gracepark@github.com> Co-authored-by: Steve Guntrip <12534592+stevecat@users.noreply.github.com> Co-authored-by: Robert Sese <sese@github.com> Co-authored-by: Peter Bengtsson <peterbe@github.com> Co-authored-by: Rachael Sewell <rachmari@github.com>
2.1 KiB
title, intro, product, versions, type, topics, shortTitle
| title | intro | product | versions | type | topics | shortTitle | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Troubleshooting Codespaces clients | You can use {% data variables.product.prodname_codespaces %} in your browser or through {% data variables.product.prodname_vscode %}. This article provides troubleshooting steps for common client issues. | {% data reusables.gated-features.codespaces %} |
|
reference |
|
Codespaces clients |
{% data variables.product.prodname_vscode %} troubleshooting
When you connect a desktop version of {% data variables.product.prodname_vscode %} to a codespace, you will notice few differences compared with working in a normal workspace but the experience will be fairly similar.
When you open a codespace in your browser using {% data variables.product.prodname_vscode %} in the web, you will notice more differences. For example, some key bindings will be different or missing, and some extensions may behave differently. For a summary, see: "Known limitations and adaptions" in the {% data variables.product.prodname_vscode %} docs.
You can check for known issues and log new issues with the {% data variables.product.prodname_vscode %} experience in the microsoft/vscode repository.
Browser troubleshooting
If you encounter issues using codespaces in a browser that is not Chromium-based, try switching to a Chromium-based browser, or check for known issues with your browser in the microsoft/vscode repository by searching for issues labeled with the name of your browser, such as firefox or safari.
If you encounter issues using codespaces in a Chromium-based browser, you can check if you're experiencing another known issue with {% data variables.product.prodname_vscode %} in the microsoft/vscode repository.