If none of these steps helped solve the issue, you can also try: Keep this log for later if your problem isn't solved. Bad shell names, arguments, or environment variables can cause the terminal to not launch. Logging often reveals what is wrong as all arguments used to create the terminal process/pty are recorded. You can enable trace logging and capture a log when launching the terminal. For example, some older versions of Windows 10 did not work well with the VS Code terminal.Įnable trace logging. The same advice applies if you are on an older build of your operating system. If your shell is installed separate from your platform, try installing the latest available version of the shell. Use the most recent version of your shell. You may also want to check that you have installed the latest version of your shell. To find the latest version of VS Code, go to the VS Code release notes. You can check your VS Code version via Help > About (on macOS Code > About Visual Studio Code). Each VS Code monthly release has many updates and fixes and may include integrated terminal improvements. The exit codes displayed come from the shell and you may be able to diagnose shell issues by searching on the internet for the specific shell and exit code. Some terminal launch failures may be due to your shell installation and are not specific to VS Code. Try running your designated integrated terminal shell outside VS Code from an external terminal or command prompt. You can open settings.json via the Edit in settings.json link in the Settings editor or with the Preferences: Open User Settings (JSON) command from the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P)).

Most Integrated Terminal settings will need to be modified directly in your user settings.json JSON file. You can review settings in the Settings editor ( File > Preferences > Settings) and search for specific settings by the setting ID.Ī quick way to check if you have changed settings that you might not be aware of, is to use the filter in the Settings editor.

- Whether to use ConPTY for Windows terminal process communication.

- Controls the current working directory a split terminal starts with.Shell profile for automation-related terminal usage like tasks and debug. Review these terminal.integrated settings that could affect the launch: To troubleshoot Integrated Terminal launch failures in Visual Studio Code, follow these steps to diagnose issues:Ĭheck your user settings. Note: If you're on Windows, you may want to review the common issues on Windows section first. The troubleshooting steps, such as checking your settings and enabling logging, apply to all platforms that support VS Code macOS, Linux, and Windows. There you can read how to configure the terminal, as well as review answers to common questions.īelow are specific troubleshooting steps, if the user guide hasn't helped you diagnose the launch failure. If you are new to using the VS Code Integrated Terminal, you can learn more in the Integrated Terminal user guide.

We hope you'll find an answer here for your shell or terminal issue and can get quickly back to work. The VS Code team works hard to make the terminal experience as seamless as possible but in some cases, there are issues with shell or terminal configurations that the VS Code editor can't work around.Īfter having worked with hundreds of developers to diagnose their terminal launch failures, the VS Code team has put together this topic with the advice and troubleshooting tips that have helped people in the past. To start, we'd like to say we're sorry that you're here reading this document instead of having a good time using the Integrated Terminal in Visual Studio Code. Configure IntelliSense for cross-compilingĮdit Troubleshoot Terminal launch failures.

Launchpad manager osx