🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 22 (from laksa170)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa022.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://code.visualstudio.com/docs/terminal/basics\')), getAhrefsUnparsedNoserviceFromURL(\'https://code.visualstudio.com/docs/terminal/basics\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/code.visualstudio.com\/docs\/terminal\/basics","crawl_time":1776017328,"first_indexed_time":1658256144,"http_code":200,"src_unparsed":"com,visualstudio!code,\/docs\/terminal\/basics s443","src_root_hash":"11536831065451992222","history_drop_reason":null,"meta_title":"Terminal Basics","meta_descriptions":["Visual Studio Code has an integrated terminal to enable working in your shell of choice without leaving the editor."],"attrs_boilerpipe_text":"Visual Studio Code includes a full featured integrated terminal that starts at the root of your workspace. It provides integration with the editor to support features like\nlinks\nand\nerror detection\n. The integrated terminal can run commands such as mkdir and git just like a standalone terminal.\nYou can open a terminal as follows:\nFrom the menu, use the\nTerminal\n>\nNew Terminal\nor\nView\n>\nTerminal\nmenu commands.\nFrom the\nCommand Palette\n(\n⇧⌘P\n(Windows, Linux\nCtrl+Shift+P\n)\n), use the\nView: Toggle Terminal\ncommand.\nIn the Explorer, you can use the\nOpen in Integrated Terminal\ncontext menu command to open a new terminal from a folder.\nTo toggle the terminal panel, use the\n⌃`\n(Windows, Linux\nCtrl+`\n)\nkeyboard shortcut.\nTo create a new terminal, use the\n⌃⇧`\n(Windows, Linux\nCtrl+Shift+`\n)\nkeyboard shortcut.\nVS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar:\nNote\nIf you prefer to work outside VS Code, open an external terminal with the\n⇧⌘C\n(Windows, Linux\nCtrl+Shift+C\n)\nkeyboard shortcut\nTerminal shells\nThe integrated terminal can use various shells installed on your machine, with the default being pulled from your system defaults. Shells are detected and presented in the terminal profiles dropdown.\nYou can learn more about configuring terminal shells in the\nterminal profiles\narticle.\nManaging terminals\nThe terminal tabs UI is on the right side of the terminal view. Each terminal has an entry with its name, icon, color, and group decoration (if any).\nAdd terminal instances by selecting the\n+\nicon on the top-right of the\nTERMINAL\npanel, selecting a profile from the terminal dropdown, or by triggering the\n⌃⇧`\n(Windows, Linux\nCtrl+Shift+`\n)\ncommand. This action creates another entry in the tab list associated with that terminal.\nRemove terminal instances by hovering a tab and selecting the\nTrash Can\nbutton, selecting a tab item and pressing\nDelete\n, using\nTerminal: Kill the Active Terminal Instance\ncommand, or via the right-click context menu.\nNavigate between terminal groups using focus next\n⇧⌘]\n(Windows, Linux\nCtrl+PageDown\n)\nand focus previous\n⇧⌘[\n(Windows, Linux\nCtrl+PageUp\n)\n.\nIcons may appear to the right of the terminal title on the tab label when a terminal's status changes. Some examples are a bell (macOS) and for tasks, displaying a check mark when there are no errors and an X otherwise. Hover the icon to read status information, which may contain actions.\nGroups (split panes)\nPlace multiple terminals side-by-side and create a group by splitting a terminal:\nHover over an entry in the list of terminals on the right and select the inline split button.\nRight-click the context menu and select the\nSplit\nmenu option.\nAlt\nand click on a tab, the\n+\nbutton, or the single tab on the terminal panel.\nTrigger the\n⌘\\\n(Windows, Linux\nCtrl+Shift+5\n)\ncommand.\nTip\nThe working directory for the new terminal depends on the\nterminal.integrated.splitCwd\nsetting\n.\nNavigate between terminals in a group by focusing the previous pane,\n⌥⌘←\n(Windows, Linux\nAlt+Left\n)\n, or the next pane,\n⌥⌘→\n(Windows, Linux\nAlt+Right\n)\n.\nDragging and dropping tabs in the list rearranges them. Dragging a tab into the main terminal area allows moving a terminal from one group to another.\nMoving a terminal into its own group can be done with the\nTerminal: Unsplit Terminal\ncommand through the Command Palette or in the right-click context menu.\nTerminals in editor area\nYou can open terminals in the editor area (terminal editors) with the\nTerminal: Create New Terminal in Editor Area\ncommand, the\nTerminal: Create New Terminal in Editor Area to the Side\ncommand, or by dragging a terminal from the terminal view into the editor area. Terminal editors are presented like regular editor tabs:\nYou can have terminal editors on either side or arranged in multiple dimensions using the editor group layout system, e.g. PowerShell and WSL terminals stacked to the right of file editors:\nThe\nterminal.integrated.defaultLocation\nsetting can change the default\nview\nor\neditor\narea terminal location.\nTerminals in new windows\nOpening a terminal in a new VS Code window is possible in a few different ways:\nUse\n⌃⇧⌥`\n(Windows, Linux\nCtrl+Shift+Alt+`\n)\nRight-click the terminal tab if you have multiple terminals, or left-click the tab if you only have a single terminal opened. Then select\nMove Terminal to New Window\nSelect the\nNew Terminal Window\nentry that's available in several different menus\nNavigating the buffer\nThe content in the terminal is called the buffer, with the section right above the bottom viewport being called \"scrollback\". The amount of scrollback kept is determined by the\nterminal.integrated.scrollback\nsetting\nand defaults to\n1000\nlines.\nThere are various commands available to navigate around the terminal buffer:\nScroll up a line -\n⌥⌘PageUp\n(Windows\nCtrl+Alt+PageUp\n, Linux\nCtrl+Shift+Up\n)\nScroll down a line -\n⌥⌘PageDown\n(Windows\nCtrl+Alt+PageDown\n, Linux\nCtrl+Shift+Down\n)\nScroll up a page -\nPageUp\n(Windows, Linux\nShift+PageUp\n)\nScroll down a page -\nPageDown\n(Windows, Linux\nShift+PageDown\n)\nScroll to the top -\n⌘Home\n(Windows\nCtrl+Home\n, Linux\nShift+Home\n)\nScroll to the bottom -\n⌘End\n(Windows\nCtrl+End\n, Linux\nShift+End\n)\nCommand\nnavigation is also available (see\nshell integration\n):\nScroll to the previous command -\n⌘↑\n(Windows, Linux\nCtrl+Up\n)\nScroll to the next command -\n⌘↓\n(Windows, Linux\nCtrl+Down\n)\nScrolling will happen instantaneously, but can be configured to animate over a short duration with the\nterminal.integrated.smoothScrolling\nsetting.\nLinks\nThe terminal features sophisticated link detection with editor integration and even extension contributed link handlers. Hover over a link to display an underline, then hold the\nCtrl\n\/\nCmd\nkey and click.\nThese built-in link handlers are used in the following priority order:\nURIs\/URLs: Links that look like URIs, such as\nhttps:\/\/code.visualstudio.com\n,\nvscode:\/\/path\/to\/file\nor\nfile:\/\/path\/to\/file\nwill open using the standard handler for the protocol. For example,\nhttps\nlinks will open the browser.\nFile links: Links to files that have been verified to exist on the system. These will open the file in a new editor tab and support many common line\/column formats such as\nfile:1:2\n,\nfile:line 1, column 2\n.\nFolder links: Links to folders are similar to file links but will open a new VS Code window at the folder.\nWord links: Fallback link type that uses the\nterminal.integrated.wordSeparators\nsetting. The setting defines word boundaries and make nearly all text into words. Activating a word link searches the workspace for the word. If there is a single result it will open, otherwise it will present the search results. Word links are considered \"low confidence\" and will not show an underline or tooltip unless you hold the\nCtrl\n\/\nCmd\nkey. They also have limited support for line and column suffixes.\nThe\nOpen Detected Link\ncommand (\n⇧⌘G\n(Windows, Linux\nCtrl+Shift+G\n)\n) can be used to access links via the keyboard:\nTip\nIf link verification causes performance issues, like in high latency remote environments, disable it via the\nterminal.integrated.enableFileLinks\nsetting\n.\nExtensions handling links\nExtensions can contribute\nlink providers\nwhich allow the extension to define what happens when clicked. An example of this is the\nGitLens\nextension detecting Git branch links.\nKeyboard accessibility\nLinks are keyboard accessible through several commands that open links based on the type of link.\nTerminal: Open Last Local File Link\n- Opens the most recent local file link. No default keyboard shortcut.\nTerminal: Open Last URL link\n- Opens the most recent URI\/URL link. No default keyboard shortcut.\nTerminal: Open Detected Link...\n- Opens a searchable Quick Pick with all detected links, including word links. The default keyboard shortcut is\nCtrl\/Cmd+Shift+O\n, which is the same as the\nGo to Symbol in Editor\nkeyboard shortcut.\nCopy & paste\nThe keyboard shortcuts for copy and paste follow platform standards:\nLinux:\nCtrl+Shift+C\nand\nCtrl+Shift+V\n; selection paste is available with\nShift+Insert\nmacOS:\nCmd+C\nand\nCmd+V\nWindows:\nCtrl+C\nand\nCtrl+V\nCopying is done automatically on selection when\nterminal.integrated.copyOnSelection\nis enabled.\nBy default, there is a warning when pasting multiple lines, which can be disabled with the\nterminal.integrated.enableMultiLinePasteWarning\nsetting. This is only done when the shell does not support \"bracketed paste mode\". When that mode is enabled, the shell is indicating that it can handle multiple line pasting.\nUsing the mouse\nRight-click behavior\nThe right-click behavior differs based on the platform:\nLinux: Show the context menu.\nmacOS: Select the word under the cursor and show the context menu.\nWindows: Copy and drop selection if there is a selection, otherwise paste.\nThis can be configured using the\nterminal.integrated.rightClickBehavior\nsetting. The options are:\ndefault\n- Show the context menu.\ncopyPaste\n- Copy when there is a selection, otherwise paste.\npaste\n- Paste on right-click.\nselectWord\n- Select the word under the cursor and show the context menu.\nnothing\n- Do nothing and pass event to terminal.\nColumn selection\nPress\nAlt\nand left-click drag to select a rectangle of text inside the terminal instead of the regular selection of a line.\nReposition the cursor with Alt\nAlt\nand left-click will reposition the cursor to underneath the mouse. This works by simulating arrow keystrokes, which may not work reliably for some shells or programs. This feature can be disabled with the\nterminal.integrated.altClickMovesCursor\nsetting.\nMouse events mode\nWhen applications running in the terminal turn on mouse events mode, such as Vim mouse mode, mouse interaction is sent to the application instead of the terminal. This means that clicking and dragging will no longer create a selection. Terminal selection can be forced by holding the\nAlt\nkey on Windows and Linux, this can also be done with the\nOption\nkey on macOS but requires enabling the\nterminal.integrated.macOptionClickForcesSelection\nsetting first.\nFind\nThe integrated terminal has find functionality that can be triggered with\n⌘F\n(Windows, Linux\nCtrl+F\n)\n.\nTip\nCtrl+F\ncan be sent to the shell by removing the\nworkbench.action.terminal.focusFind\ncommand from\ncommands to skip shell\n.\nRun selected text\nTo use the\nrunSelectedText\ncommand, select text in an editor and run the command\nTerminal: Run Selected Text in Active Terminal\nvia the\nCommand Palette\n(\n⇧⌘P\n(Windows, Linux\nCtrl+Shift+P\n)\n), the terminal will attempt to run the selected text. If no text is selected in the active editor, the entire line that the cursor is on will run in the terminal.\nTip\nAlso run the active file using the command\nworkbench.action.terminal.runActiveFile\n.\nMaximizing the terminal\nThe terminal view can be maximized by clicking the maximize panel size button with the upwards chevron icon. This will temporarily hide the editors and maximize the panel. This is useful to temporarily focus on a large amount of output. Some developers use VS Code as a standalone terminal by opening a new window, maximizing the panel, and hiding the side bar.\nNote that the panel can only be maximized if its\nalignment\noption is set to\nCenter\n.\nSelect all\nThere is a\nTerminal: Select All\ncommand, which is bound to\nCmd+A\non macOS, but does not have a default keyboard shortcut on Windows and Linux as it may conflict with shell hotkeys. To use\nCtrl+A\nto select all, add this custom keyboard shortcut:\n{\n\"key\"\n:\n\"ctrl+a\"\n,\n\"command\"\n:\n\"workbench.action.terminal.selectAll\"\n,\n\"when\"\n:\n\"terminalFocus && !isMac\"\n},\nDrag and drop file paths\nDragging a file into the terminal will input the path into the terminal, with escaping to match the active shell.\nAutomating terminals with tasks\nThe\nTasks\nfeature can be used to automate the launching of terminals, for example, the following\n.vscode\/tasks.json\nfile will launch a Command Prompt and PowerShell terminal in a single terminal group when the window starts:\n{\n\"version\"\n:\n\"2.0.0\"\n,\n\"presentation\"\n: {\n\"echo\"\n:\nfalse\n,\n\"reveal\"\n:\n\"always\"\n,\n\"focus\"\n:\nfalse\n,\n\"panel\"\n:\n\"dedicated\"\n,\n\"showReuseMessage\"\n:\ntrue\n},\n\"tasks\"\n: [\n{\n\"label\"\n:\n\"Create terminals\"\n,\n\"dependsOn\"\n: [\n\"First\"\n,\n\"Second\"\n],\n\/\/ Mark as the default build task so cmd\/ctrl+shift+b will create them\n\"group\"\n: {\n\"kind\"\n:\n\"build\"\n,\n\"isDefault\"\n:\ntrue\n},\n\/\/ Try start the task on folder open\n\"runOptions\"\n: {\n\"runOn\"\n:\n\"folderOpen\"\n}\n},\n{\n\/\/ The name that shows up in terminal tab\n\"label\"\n:\n\"First\"\n,\n\/\/ The task will launch a shell\n\"type\"\n:\n\"shell\"\n,\n\"command\"\n:\n\"\"\n,\n\/\/ Set the shell type\n\"options\"\n: {\n\"shell\"\n: {\n\"executable\"\n:\n\"cmd.exe\"\n,\n\"args\"\n: []\n}\n},\n\/\/ Mark as a background task to avoid the spinner animation on the terminal tab\n\"isBackground\"\n:\ntrue\n,\n\"problemMatcher\"\n: [],\n\/\/ Create the tasks in a terminal group\n\"presentation\"\n: {\n\"group\"\n:\n\"my-group\"\n}\n},\n{\n\"label\"\n:\n\"Second\"\n,\n\"type\"\n:\n\"shell\"\n,\n\"command\"\n:\n\"\"\n,\n\"options\"\n: {\n\"shell\"\n: {\n\"executable\"\n:\n\"pwsh.exe\"\n,\n\"args\"\n: []\n}\n},\n\"isBackground\"\n:\ntrue\n,\n\"problemMatcher\"\n: [],\n\"presentation\"\n: {\n\"group\"\n:\n\"my-group\"\n}\n}\n]\n}\nThis file could be committed to the repository to share with other developers or created as a user task via the\nworkbench.action.tasks.openUserTasks\ncommand.\nWorking directory\nBy default, the terminal will open at the folder that is opened in the Explorer. The\nterminal.integrated.cwd\nsetting allows specifying a custom path to open instead:\n{\n\"terminal.integrated.cwd\"\n:\n\"\/home\/user\"\n}\nSplit terminals on Windows will start in the directory that the parent terminal started with. On macOS and Linux, split terminals will inherit the current working directory of the parent terminal. This behavior can be changed using the\nterminal.integrated.splitCwd\nsetting:\n{\n\"terminal.integrated.splitCwd\"\n:\n\"workspaceRoot\"\n}\nThere are also extensions available that give more options such as\nTerminal Here\n.\nFixed dimension terminals\nThe\nTerminal: Set Fixed Dimensions\ncommand allows changing the number of columns and rows that the terminal and it's backing pseudoterminal uses. This will add scroll bars when necessary, which may lead to an unpleasant UX and is generally not recommended, but it is a common ask on Windows in particular for reading logs or long lines when paging tools aren't available.\nYou can also right-click on a terminal tab and select\nToggle Size to Content Width\n(\n⌥Z\n(Windows, Linux\nAlt+Z\n)\n) to resize the number of terminal columns to the largest wrapped line in the terminal.\nGitHub Copilot in the terminal\nIf you have access to\nGitHub Copilot\n, you can use it to get AI-powered help with terminal commands and shell scripting. There are several ways to use Copilot with the terminal:\nTerminal inline chat\nStart an inline chat directly in the terminal to get help with shell commands:\nOpen the terminal (\n⌃`\n(Windows, Linux\nCtrl+`\n)\n)\nPress\n⌘I\n(Windows, Linux\nCtrl+I\n)\nor run the\nTerminal Inline Chat\ncommand from the Command Palette\nEnter your question or request in natural language, such as:\n\"How do I find the largest files in this directory?\"\n\"Show me how to undo the last git commit\"\n\"Create a bash script to analyze log files\"\nWhen Copilot provides a response, you can select\nRun\nto execute the command directly or\nInsert\nto add it to the terminal for further editing.\nFor more information about using GitHub Copilot with the terminal, see\nUse terminal inline chat\n.\nTerminal chat participant\nUse the dedicated\n@terminal\nchat participant in ask mode in the Chat view:\nOpen the Chat view (\n⌃⌘I\n(Windows, Linux\nCtrl+Alt+I\n)\n)\nStart your question with\n@terminal\nto direct it to the terminal participant\nAsk about terminal commands, shell scripting, or explaining terminal output\nExamples:\n@terminal list the 5 largest files in this workspace\n@terminal \/explain top shell command\n@terminal how to grep for patterns recursively\nReference terminal context in chat\nYou can include terminal information as context in your chat prompts:\nUse\n#terminalSelection\nto add selected text from the terminal to your chat prompt\nUse\n#terminalLastCommand\nto include the last command you ran in the terminal\nNext steps\nThe basics of the terminal have been covered in this document. Read on to find out more about:\nTerminal inline chat\n- AI-powered suggestions right in your terminal.\nTasks\n- Tasks let you integrate with external tools and leverage the terminal heavily.\nMastering VS Code's Terminal\n- An external blog with plenty of power user tips for the terminal.\nExplore terminal commands by browsing the keyboard shortcuts within VS Code (\nPreferences: Open Keyboard Shortcuts\nthen search on 'terminal').\nCommon questions\nI'm having problems launching the terminal\nThere's a\ndedicated troubleshooting guide\nfor these sorts of problems.\nHow do I create an Admin terminal?\nThe integrated terminal shell is running with the permissions of VS Code. If you need to run a shell command with elevated (administrator) or different permissions, use platform utilities such as\nrunas.exe\nwithin a terminal.\nYou can learn more about customizing terminals via terminal profiles in\nConfiguring Profiles\n.\nCan I add a keyboard shortcut for the Explorer's Open in Integrated Terminal command?\nYou can open new terminals for specific folders from the Explorer via the\nOpen in Integrated Terminal\ncontext menu command.\nBy default, there is no keyboard shortcut associated with\nOpen in Integrated Terminal\nbut you can add your own via the Keyboard Shortcuts editor (\n⌘K ⌘S\n(Windows, Linux\nCtrl+K Ctrl+S\n)\n) to add a keyboard shortcut to your\nkeybindings.json\n.\nThe\nkeybindings.json\nexample below adds the keyboard shortcut\nCtrl+T\nfor\nopenInTerminal\n.\n{\n\"key\"\n:\n\"ctrl+t\"\n,\n\"command\"\n:\n\"openInTerminal\"\n,\n\"when\"\n:\n\"filesExplorerFocus\"\n}\nWhy is nvm complaining about a prefix option when the integrated terminal is launched?\nnvm (Node Version Manager) users often see this error for the first time inside VS Code's integrated terminal:\nnvm\nis\nnot\ncompatible\nwith\nthe\nnpm\nconfig\n\"prefix\"\noption:\ncurrently\nset\nto\n\"\/usr\/local\"\nRun\n`\nnpm\nconfig delete prefix`\nor\n`\nnvm\nuse\n--delete-prefix\nv8.9.1\n--silent\n`\nto\nunset\nit\nThis is mostly a macOS problem and does not happen in external terminals. The typical reasons for this are the following:\nnpm\nwas globally installed using another instance of\nnode\nthat is somewhere in your path (such as\n\/usr\/local\/bin\/npm\n).\nTo get the development tools on the\n$PATH\n, VS Code will launch a bash login shell on startup. This means that your\n~\/.bash_profile\nhas already run and when an integrated terminal launches, it will run\nanother\nlogin shell, reordering the\n$PATH\npotentially in unexpected ways.\nTo resolve this issue, you need to track down where the old\nnpm\nis installed and remove both it and its out-of-date node_modules. Find the\nnvm\ninitialization script and run\nwhich npm\nbefore it runs, which should print the path when you launch a new terminal.\nOnce you have the path to npm, find the old node_modules by resolving the symlink by running a command something like this:\nls\n-la\n\/usr\/local\/bin\n|\ngrep\n\"np[mx]\"\nThis will give you the resolved path at the end:\n...\nnpm\n->\n..\/lib\/node_modules\/npm\/bin\/npm-cli.js\n...\nnpx\n->\n..\/lib\/node_modules\/npm\/bin\/npx-cli.js\nFrom there, removing the files and relaunching VS Code should fix the issue:\nrm\n\/usr\/local\/bin\/npm\n\/usr\/local\/lib\/node_modules\/npm\/bin\/npm-cli.js\nrm\n\/usr\/local\/bin\/npx\n\/usr\/local\/lib\/node_modules\/npm\/bin\/npx-cli.js\nWhy does macOS make a ding sound when I resize terminal split panes?\nThe keyboard shortcuts ⌃⌘← and ⌃⌘→ are the defaults for resizing individual split panes in the terminal. While they work, they also cause a system \"invalid key\" sound to play due to an issue in Chromium. The\nrecommended workaround\nis to tell macOS to no-op for these keyboard shortcuts by running this in your terminal:\nmkdir\n-p\n~\/Library\/KeyBindings\ncat\n>\n~\/Library\/KeyBindings\/DefaultKeyBinding.dict\n<<\nEOF\n{\n\"@^\\UF700\" = \"noop:\";\n\"@^\\UF701\" = \"noop:\";\n\"@^\\UF702\" = \"noop:\";\n\"@^\\UF703\" = \"noop:\";\n\"@~^\\UF700\" = \"noop:\";\n\"@~^\\UF701\" = \"noop:\";\n\"@~^\\UF702\" = \"noop:\";\n\"@~^\\UF703\" = \"noop:\";\n}\nEOF\nI'm having problems with the terminal rendering. What can I do?\nBy default, the integrated terminal will render using GPU acceleration on most machines. Typically when there are rendering problems it's an issue of something in your hardware\/OS\/drivers not playing nicely with the GPU renderer. The first thing to try is to disable GPU acceleration, trading off rendering speed for DOM-based rendering, which is more reliable:\n{\n\"terminal.integrated.gpuAcceleration\"\n:\n\"off\"\n}\nSee the\nGPU acceleration\nsection for more information.\nI see 1~ or [201~ when I paste something\nThis normally means that the program\/shell running inside the terminal requested to turn on \"bracketed paste mode\" but something doesn't support it properly. To work around this, you could run\nprintf \"\\e[?2004l\"\nto disable it for that session or add the following to your\n~\/.inputrc\nfile:\nset\nenable-bracketed-paste\noff\nAlternatively, bracketed paste mode can be forced to ignore the shell's request by turning it off with this setting:\n{\n\"terminal.integrated.ignoreBracketedPasteMode\"\n:\ntrue\n}\nCtrl+A, Ctrl+R output ^A, ^R on zsh\nThis can happen if zsh is in Vim mode instead of Emacs mode, due to setting\n$EDITOR\nor\n$VISUAL\nto\nvi\n\/\nvim\nin your init scripts.\nTo work around this, you have two options:\nEnsure that you don't set\n$EDITOR\nto\nvi(m)\n. However, this isn't an option if you want your Git editor to work.\nAdd\nbindkey -e\nto your init script to set Emacs explicitly.\nHow can I configure Cmd+. to map to Ctrl+C like macOS' built-in terminal?\nThe macOS default terminal uses\nCmd+.\nto perform the same as\nCtrl+C\n. To get this behavior in VS Code, add this\ncustom keyboard shortcut\n:\n{\n\"key\"\n:\n\"cmd+.\"\n,\n\"command\"\n:\n\"workbench.action.terminal.sendSequence\"\n,\n\"when\"\n:\n\"terminalFocus\"\n,\n\"args\"\n: {\n\"text\"\n:\n\"\n\\u0003\n\"\n}\n}\nWhy are the colors in the terminal not correct?\nOne of our accessibility features we enable by default is to ensure a minimum contrast ratio of at least 4.5 is met for the foreground text. This feature ensures that text is readable regardless of the shell and theme used which is not possible otherwise. To disable this feature, you can set:\n\"terminal.integrated.minimumContrastRatio\"\n:\n1\nSee the\nminimum contrast ratio\nsection for more information.\n4\/8\/2026","attrs_markdown":"[Visual Studio Code](https:\/\/code.visualstudio.com\/)\n\n- [Docs](https:\/\/code.visualstudio.com\/docs)\n- [Updates](https:\/\/code.visualstudio.com\/updates)\n- [Blog](https:\/\/code.visualstudio.com\/blogs)\n- [API](https:\/\/code.visualstudio.com\/api)\n- [Extensions](https:\/\/marketplace.visualstudio.com\/VSCode)\n- [MCP](https:\/\/code.visualstudio.com\/mcp)\n- [FAQ](https:\/\/code.visualstudio.com\/docs\/supporting\/faq)\n- [Learn](https:\/\/code.visualstudio.com\/learn)\n- [Events](https:\/\/aka.ms\/vscode\/live)\n\n- [Download](https:\/\/code.visualstudio.com\/Download)\n\n![](https:\/\/code.visualstudio.com\/assets\/icons\/search-dark.svg) ![](https:\/\/code.visualstudio.com\/assets\/icons\/search.svg)    Search Ctrl+Shift+P\n\n![Switch to the dark theme](https:\/\/code.visualstudio.com\/assets\/icons\/theme-light.svg) ![Switch to the light theme](https:\/\/code.visualstudio.com\/assets\/icons\/theme-dark.svg)\n\n[Download](https:\/\/code.visualstudio.com\/Download)\n\nExplore Agentic Development - [Join a GitHub Copilot Dev Day near you\\!](https:\/\/aka.ms\/githubcopilotdevdays)\n\nDismiss this update\n\n#### Documentation\n- [Overview](https:\/\/code.visualstudio.com\/docs)\n- [Setup](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#setup-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/setup\/setup-overview)\n  - [Linux](https:\/\/code.visualstudio.com\/docs\/setup\/linux)\n  - [macOS](https:\/\/code.visualstudio.com\/docs\/setup\/mac)\n  - [Windows](https:\/\/code.visualstudio.com\/docs\/setup\/windows)\n  - [VS Code for the Web](https:\/\/code.visualstudio.com\/docs\/setup\/vscode-web)\n  - [Raspberry Pi](https:\/\/code.visualstudio.com\/docs\/setup\/raspberry-pi)\n  - [Network](https:\/\/code.visualstudio.com\/docs\/setup\/network)\n  - [Additional Components](https:\/\/code.visualstudio.com\/docs\/setup\/additional-components)\n  - [Uninstall](https:\/\/code.visualstudio.com\/docs\/setup\/uninstall)\n- [Get Started](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#getstarted-articles)\n  - [VS Code Tutorial](https:\/\/code.visualstudio.com\/docs\/getstarted\/getting-started)\n  - [Copilot Quickstart](https:\/\/code.visualstudio.com\/docs\/getstarted\/copilot-quickstart)\n  - [User Interface](https:\/\/code.visualstudio.com\/docs\/getstarted\/userinterface)\n  - [Personalize VS Code](https:\/\/code.visualstudio.com\/docs\/getstarted\/personalize-vscode)\n  - [Install Extensions](https:\/\/code.visualstudio.com\/docs\/getstarted\/extensions)\n  - [Tips and Tricks](https:\/\/code.visualstudio.com\/docs\/getstarted\/tips-and-tricks)\n  - [Intro Videos](https:\/\/code.visualstudio.com\/docs\/getstarted\/introvideos)\n- [GitHub Copilot](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#copilot-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/copilot\/overview)\n  - [Setup](https:\/\/code.visualstudio.com\/docs\/copilot\/setup)\n  - [Quickstart](https:\/\/code.visualstudio.com\/docs\/copilot\/getting-started)\n  - [Concepts](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#copilot-concepts-articles)\n    - [Overview](https:\/\/code.visualstudio.com\/docs\/copilot\/concepts\/overview)\n    - [Language Models](https:\/\/code.visualstudio.com\/docs\/copilot\/concepts\/language-models)\n    - [Context](https:\/\/code.visualstudio.com\/docs\/copilot\/concepts\/context)\n    - [Tools](https:\/\/code.visualstudio.com\/docs\/copilot\/concepts\/tools)\n    - [Agents](https:\/\/code.visualstudio.com\/docs\/copilot\/concepts\/agents)\n    - [Customization](https:\/\/code.visualstudio.com\/docs\/copilot\/concepts\/customization)\n    - [Trust & Safety](https:\/\/code.visualstudio.com\/docs\/copilot\/concepts\/trust-and-safety)\n  - [Agents](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#copilot-agents-articles)\n    - [Overview](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/overview)\n    - [Agents Tutorial](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/agents-tutorial)\n    - [Planning](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/planning)\n    - [Memory](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/memory)\n    - [Tools](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/agent-tools)\n    - [Subagents](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/subagents)\n    - [Local Agents](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/local-agents)\n    - [Copilot CLI](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/copilot-cli)\n    - [Cloud Agents](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/cloud-agents)\n    - [Third-Party Agents](https:\/\/code.visualstudio.com\/docs\/copilot\/agents\/third-party-agents)\n  - [Chat](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#copilot-chat-articles)\n    - [Overview](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/copilot-chat)\n    - [Chat Sessions](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/chat-sessions)\n    - [Add Context](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/copilot-chat-context)\n    - [Inline Chat](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/inline-chat)\n    - [Review Edits](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/review-code-edits)\n    - [Checkpoints](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/chat-checkpoints)\n    - [Debug Chat Interactions](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/chat-debug-view)\n    - [Prompt Examples](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/prompt-examples)\n  - [Customization](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#copilot-customization-articles)\n    - [Overview](https:\/\/code.visualstudio.com\/docs\/copilot\/customization\/overview)\n    - [Instructions](https:\/\/code.visualstudio.com\/docs\/copilot\/customization\/custom-instructions)\n    - [Prompt Files](https:\/\/code.visualstudio.com\/docs\/copilot\/customization\/prompt-files)\n    - [Custom Agents](https:\/\/code.visualstudio.com\/docs\/copilot\/customization\/custom-agents)\n    - [Agent Skills](https:\/\/code.visualstudio.com\/docs\/copilot\/customization\/agent-skills)\n    - [Language Models](https:\/\/code.visualstudio.com\/docs\/copilot\/customization\/language-models)\n    - [MCP](https:\/\/code.visualstudio.com\/docs\/copilot\/customization\/mcp-servers)\n    - [Hooks](https:\/\/code.visualstudio.com\/docs\/copilot\/customization\/hooks)\n    - [Plugins](https:\/\/code.visualstudio.com\/docs\/copilot\/customization\/agent-plugins)\n  - [Guides & Tutorials](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#copilot-guides-articles)\n    - [Context Engineering](https:\/\/code.visualstudio.com\/docs\/copilot\/guides\/context-engineering-guide)\n    - [Customize AI](https:\/\/code.visualstudio.com\/docs\/copilot\/guides\/customize-copilot-guide)\n    - [Test-Driven Development](https:\/\/code.visualstudio.com\/docs\/copilot\/guides\/test-driven-development-guide)\n    - [Edit Notebooks with AI](https:\/\/code.visualstudio.com\/docs\/copilot\/guides\/notebooks-with-ai)\n    - [Test with AI](https:\/\/code.visualstudio.com\/docs\/copilot\/guides\/test-with-copilot)\n    - [Test Web Apps with Browser Tools](https:\/\/code.visualstudio.com\/docs\/copilot\/guides\/browser-agent-testing-guide)\n    - [Debug with AI](https:\/\/code.visualstudio.com\/docs\/copilot\/guides\/debug-with-copilot)\n    - [MCP Dev Guide](https:\/\/code.visualstudio.com\/docs\/copilot\/guides\/mcp-developer-guide)\n    - [Monitoring](https:\/\/code.visualstudio.com\/docs\/copilot\/guides\/monitoring-agents)\n  - [Inline Suggestions](https:\/\/code.visualstudio.com\/docs\/copilot\/ai-powered-suggestions)\n  - [Smart Actions](https:\/\/code.visualstudio.com\/docs\/copilot\/copilot-smart-actions)\n  - [Best Practices](https:\/\/code.visualstudio.com\/docs\/copilot\/best-practices)\n  - [Security](https:\/\/code.visualstudio.com\/docs\/copilot\/security)\n  - [Troubleshooting](https:\/\/code.visualstudio.com\/docs\/copilot\/troubleshooting)\n  - [FAQ](https:\/\/code.visualstudio.com\/docs\/copilot\/faq)\n  - [Reference](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#copilot-reference-articles)\n    - [Cheat Sheet](https:\/\/code.visualstudio.com\/docs\/copilot\/reference\/copilot-vscode-features)\n    - [Settings Reference](https:\/\/code.visualstudio.com\/docs\/copilot\/reference\/copilot-settings)\n    - [MCP Configuration](https:\/\/code.visualstudio.com\/docs\/copilot\/reference\/mcp-configuration)\n    - [Workspace Context](https:\/\/code.visualstudio.com\/docs\/copilot\/reference\/workspace-context)\n- [Configure](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#configure-articles)\n  - [Display Language](https:\/\/code.visualstudio.com\/docs\/configure\/locales)\n  - [Layout](https:\/\/code.visualstudio.com\/docs\/configure\/custom-layout)\n  - [Keyboard Shortcuts](https:\/\/code.visualstudio.com\/docs\/configure\/keybindings)\n  - [Settings](https:\/\/code.visualstudio.com\/docs\/configure\/settings)\n  - [Settings Sync](https:\/\/code.visualstudio.com\/docs\/configure\/settings-sync)\n  - [Extensions](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#configure-extensions-articles)\n    - [Extension Marketplace](https:\/\/code.visualstudio.com\/docs\/configure\/extensions\/extension-marketplace)\n    - [Extension Runtime Security](https:\/\/code.visualstudio.com\/docs\/configure\/extensions\/extension-runtime-security)\n  - [Themes](https:\/\/code.visualstudio.com\/docs\/configure\/themes)\n  - [Profiles](https:\/\/code.visualstudio.com\/docs\/configure\/profiles)\n  - [Accessibility](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#configure-accessibility-articles)\n    - [Overview](https:\/\/code.visualstudio.com\/docs\/configure\/accessibility\/accessibility)\n    - [Voice Interactions](https:\/\/code.visualstudio.com\/docs\/configure\/accessibility\/voice)\n  - [Command Line Interface](https:\/\/code.visualstudio.com\/docs\/configure\/command-line)\n  - [Telemetry](https:\/\/code.visualstudio.com\/docs\/configure\/telemetry)\n- [Edit Code](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#editing-articles)\n  - [Basic Editing](https:\/\/code.visualstudio.com\/docs\/editing\/codebasics)\n  - [IntelliSense](https:\/\/code.visualstudio.com\/docs\/editing\/intellisense)\n  - [Code Navigation](https:\/\/code.visualstudio.com\/docs\/editing\/editingevolved)\n  - [Refactoring](https:\/\/code.visualstudio.com\/docs\/editing\/refactoring)\n  - [Snippets](https:\/\/code.visualstudio.com\/docs\/editing\/userdefinedsnippets)\n  - [Workspaces](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#editing-workspaces-articles)\n    - [Overview](https:\/\/code.visualstudio.com\/docs\/editing\/workspaces\/workspaces)\n    - [Multi-Root Workspaces](https:\/\/code.visualstudio.com\/docs\/editing\/workspaces\/multi-root-workspaces)\n    - [Workspace Trust](https:\/\/code.visualstudio.com\/docs\/editing\/workspaces\/workspace-trust)\n- [Build, Debug, Test](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#debugtest-articles)\n  - [Tasks](https:\/\/code.visualstudio.com\/docs\/debugtest\/tasks)\n  - [Debugging](https:\/\/code.visualstudio.com\/docs\/debugtest\/debugging)\n  - [Debug Configuration](https:\/\/code.visualstudio.com\/docs\/debugtest\/debugging-configuration)\n  - [Testing](https:\/\/code.visualstudio.com\/docs\/debugtest\/testing)\n  - [Port Forwarding](https:\/\/code.visualstudio.com\/docs\/debugtest\/port-forwarding)\n  - [Integrated Browser](https:\/\/code.visualstudio.com\/docs\/debugtest\/integrated-browser)\n- [Source Control](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#sourcecontrol-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/sourcecontrol\/overview)\n  - [Quickstart](https:\/\/code.visualstudio.com\/docs\/sourcecontrol\/quickstart)\n  - [Staging & Committing](https:\/\/code.visualstudio.com\/docs\/sourcecontrol\/staging-commits)\n  - [Branches & Worktrees](https:\/\/code.visualstudio.com\/docs\/sourcecontrol\/branches-worktrees)\n  - [Repositories & Remotes](https:\/\/code.visualstudio.com\/docs\/sourcecontrol\/repos-remotes)\n  - [Merge Conflicts](https:\/\/code.visualstudio.com\/docs\/sourcecontrol\/merge-conflicts)\n  - [Collaborate on GitHub](https:\/\/code.visualstudio.com\/docs\/sourcecontrol\/github)\n  - [Troubleshooting](https:\/\/code.visualstudio.com\/docs\/sourcecontrol\/troubleshooting)\n  - [FAQ](https:\/\/code.visualstudio.com\/docs\/sourcecontrol\/faq)\n- [Terminal](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#terminal-articles)\n  - [Getting Started Tutorial](https:\/\/code.visualstudio.com\/docs\/terminal\/getting-started)\n  - [Terminal Basics](https:\/\/code.visualstudio.com\/docs\/terminal\/basics)\n  - [Terminal Profiles](https:\/\/code.visualstudio.com\/docs\/terminal\/profiles)\n  - [Shell Integration](https:\/\/code.visualstudio.com\/docs\/terminal\/shell-integration)\n  - [Appearance](https:\/\/code.visualstudio.com\/docs\/terminal\/appearance)\n  - [Advanced](https:\/\/code.visualstudio.com\/docs\/terminal\/advanced)\n- [Enterprise](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#enterprise-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/enterprise\/overview)\n  - [Enterprise Policies](https:\/\/code.visualstudio.com\/docs\/enterprise\/policies)\n  - [AI Settings](https:\/\/code.visualstudio.com\/docs\/enterprise\/ai-settings)\n  - [Extensions](https:\/\/code.visualstudio.com\/docs\/enterprise\/extensions)\n  - [Telemetry](https:\/\/code.visualstudio.com\/docs\/enterprise\/telemetry)\n  - [Updates](https:\/\/code.visualstudio.com\/docs\/enterprise\/updates)\n- [Languages](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#languages-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/languages\/overview)\n  - [JavaScript](https:\/\/code.visualstudio.com\/docs\/languages\/javascript)\n  - [JSON](https:\/\/code.visualstudio.com\/docs\/languages\/json)\n  - [HTML](https:\/\/code.visualstudio.com\/docs\/languages\/html)\n  - [Emmet](https:\/\/code.visualstudio.com\/docs\/languages\/emmet)\n  - [CSS, SCSS and Less](https:\/\/code.visualstudio.com\/docs\/languages\/css)\n  - [TypeScript](https:\/\/code.visualstudio.com\/docs\/languages\/typescript)\n  - [Markdown](https:\/\/code.visualstudio.com\/docs\/languages\/markdown)\n  - [PowerShell](https:\/\/code.visualstudio.com\/docs\/languages\/powershell)\n  - [C++](https:\/\/code.visualstudio.com\/docs\/languages\/cpp)\n  - [Java](https:\/\/code.visualstudio.com\/docs\/languages\/java)\n  - [PHP](https:\/\/code.visualstudio.com\/docs\/languages\/php)\n  - [Python](https:\/\/code.visualstudio.com\/docs\/languages\/python)\n  - [Julia](https:\/\/code.visualstudio.com\/docs\/languages\/julia)\n  - [R](https:\/\/code.visualstudio.com\/docs\/languages\/r)\n  - [Ruby](https:\/\/code.visualstudio.com\/docs\/languages\/ruby)\n  - [Rust](https:\/\/code.visualstudio.com\/docs\/languages\/rust)\n  - [Go](https:\/\/code.visualstudio.com\/docs\/languages\/go)\n  - [T-SQL](https:\/\/code.visualstudio.com\/docs\/languages\/tsql)\n  - [C\\#](https:\/\/code.visualstudio.com\/docs\/languages\/csharp)\n  - [.NET](https:\/\/code.visualstudio.com\/docs\/languages\/dotnet)\n  - [Swift](https:\/\/code.visualstudio.com\/docs\/languages\/swift)\n- [Node.js \/ JavaScript](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#nodejs-articles)\n  - [Working with JavaScript](https:\/\/code.visualstudio.com\/docs\/nodejs\/working-with-javascript)\n  - [Node.js Tutorial](https:\/\/code.visualstudio.com\/docs\/nodejs\/nodejs-tutorial)\n  - [Node.js Debugging](https:\/\/code.visualstudio.com\/docs\/nodejs\/nodejs-debugging)\n  - [Deploy Node.js Apps](https:\/\/code.visualstudio.com\/docs\/nodejs\/nodejs-deployment)\n  - [Browser Debugging](https:\/\/code.visualstudio.com\/docs\/nodejs\/browser-debugging)\n  - [Angular Tutorial](https:\/\/code.visualstudio.com\/docs\/nodejs\/angular-tutorial)\n  - [React Tutorial](https:\/\/code.visualstudio.com\/docs\/nodejs\/reactjs-tutorial)\n  - [Vue Tutorial](https:\/\/code.visualstudio.com\/docs\/nodejs\/vuejs-tutorial)\n  - [Debugging Recipes](https:\/\/code.visualstudio.com\/docs\/nodejs\/debugging-recipes)\n  - [Performance Profiling](https:\/\/code.visualstudio.com\/docs\/nodejs\/profiling)\n  - [Extensions](https:\/\/code.visualstudio.com\/docs\/nodejs\/extensions)\n- [TypeScript](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#typescript-articles)\n  - [Tutorial](https:\/\/code.visualstudio.com\/docs\/typescript\/typescript-tutorial)\n  - [Transpiling](https:\/\/code.visualstudio.com\/docs\/typescript\/typescript-transpiling)\n  - [Editing](https:\/\/code.visualstudio.com\/docs\/typescript\/typescript-editing)\n  - [Refactoring](https:\/\/code.visualstudio.com\/docs\/typescript\/typescript-refactoring)\n  - [Debugging](https:\/\/code.visualstudio.com\/docs\/typescript\/typescript-debugging)\n- [Python](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#python-articles)\n  - [Quick Start](https:\/\/code.visualstudio.com\/docs\/python\/python-quick-start)\n  - [Tutorial](https:\/\/code.visualstudio.com\/docs\/python\/python-tutorial)\n  - [Run Python Code](https:\/\/code.visualstudio.com\/docs\/python\/run)\n  - [Editing](https:\/\/code.visualstudio.com\/docs\/python\/editing)\n  - [Linting](https:\/\/code.visualstudio.com\/docs\/python\/linting)\n  - [Formatting](https:\/\/code.visualstudio.com\/docs\/python\/formatting)\n  - [Debugging](https:\/\/code.visualstudio.com\/docs\/python\/debugging)\n  - [Environments](https:\/\/code.visualstudio.com\/docs\/python\/environments)\n  - [Testing](https:\/\/code.visualstudio.com\/docs\/python\/testing)\n  - [Python Interactive](https:\/\/code.visualstudio.com\/docs\/python\/jupyter-support-py)\n  - [Django Tutorial](https:\/\/code.visualstudio.com\/docs\/python\/tutorial-django)\n  - [FastAPI Tutorial](https:\/\/code.visualstudio.com\/docs\/python\/tutorial-fastapi)\n  - [Flask Tutorial](https:\/\/code.visualstudio.com\/docs\/python\/tutorial-flask)\n  - [Create Containers](https:\/\/code.visualstudio.com\/docs\/python\/tutorial-create-containers)\n  - [Deploy Python Apps](https:\/\/code.visualstudio.com\/docs\/python\/python-on-azure)\n  - [Python in the Web](https:\/\/code.visualstudio.com\/docs\/python\/python-web)\n  - [Settings Reference](https:\/\/code.visualstudio.com\/docs\/python\/settings-reference)\n- [Java](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#java-articles)\n  - [Getting Started](https:\/\/code.visualstudio.com\/docs\/java\/java-tutorial)\n  - [Navigate and Edit](https:\/\/code.visualstudio.com\/docs\/java\/java-editing)\n  - [Refactoring](https:\/\/code.visualstudio.com\/docs\/java\/java-refactoring)\n  - [Formatting and Linting](https:\/\/code.visualstudio.com\/docs\/java\/java-linting)\n  - [Project Management](https:\/\/code.visualstudio.com\/docs\/java\/java-project)\n  - [Build Tools](https:\/\/code.visualstudio.com\/docs\/java\/java-build)\n  - [Run and Debug](https:\/\/code.visualstudio.com\/docs\/java\/java-debugging)\n  - [Testing](https:\/\/code.visualstudio.com\/docs\/java\/java-testing)\n  - [Spring Boot](https:\/\/code.visualstudio.com\/docs\/java\/java-spring-boot)\n  - [Modernizing Java Apps](https:\/\/code.visualstudio.com\/docs\/java\/java-app-mod)\n  - [Application Servers](https:\/\/code.visualstudio.com\/docs\/java\/java-tomcat-jetty)\n  - [Deploy Java Apps](https:\/\/code.visualstudio.com\/docs\/java\/java-on-azure)\n  - [GUI Applications](https:\/\/code.visualstudio.com\/docs\/java\/java-gui)\n  - [Extensions](https:\/\/code.visualstudio.com\/docs\/java\/extensions)\n  - [FAQ](https:\/\/code.visualstudio.com\/docs\/java\/java-faq)\n- [C++](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#cpp-articles)\n  - [Intro Videos](https:\/\/code.visualstudio.com\/docs\/cpp\/introvideos-cpp)\n  - [GCC on Linux](https:\/\/code.visualstudio.com\/docs\/cpp\/config-linux)\n  - [GCC on Windows](https:\/\/code.visualstudio.com\/docs\/cpp\/config-mingw)\n  - [GCC on Windows Subsystem for Linux](https:\/\/code.visualstudio.com\/docs\/cpp\/config-wsl)\n  - [Clang on macOS](https:\/\/code.visualstudio.com\/docs\/cpp\/config-clang-mac)\n  - [Microsoft C++ on Windows](https:\/\/code.visualstudio.com\/docs\/cpp\/config-msvc)\n  - [Build with CMake](https:\/\/code.visualstudio.com\/docs\/cpp\/build-with-cmake)\n  - [CMake Tools on Linux](https:\/\/code.visualstudio.com\/docs\/cpp\/cmake-linux)\n  - [CMake Quick Start](https:\/\/code.visualstudio.com\/docs\/cpp\/cmake-quickstart)\n  - [C++ Dev Tools for Copilot](https:\/\/code.visualstudio.com\/docs\/cpp\/cpp-devtools)\n  - [Editing and Navigating](https:\/\/code.visualstudio.com\/docs\/cpp\/cpp-ide)\n  - [Debugging](https:\/\/code.visualstudio.com\/docs\/cpp\/cpp-debug)\n  - [Configure Debugging](https:\/\/code.visualstudio.com\/docs\/cpp\/launch-json-reference)\n  - [Refactoring](https:\/\/code.visualstudio.com\/docs\/cpp\/cpp-refactoring)\n  - [Settings Reference](https:\/\/code.visualstudio.com\/docs\/cpp\/customize-cpp-settings)\n  - [Configure IntelliSense](https:\/\/code.visualstudio.com\/docs\/cpp\/configure-intellisense)\n  - [Configure IntelliSense for Cross-Compiling](https:\/\/code.visualstudio.com\/docs\/cpp\/configure-intellisense-crosscompilation)\n  - [FAQ](https:\/\/code.visualstudio.com\/docs\/cpp\/faq-cpp)\n- [C\\#](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#csharp-articles)\n  - [Intro Videos](https:\/\/code.visualstudio.com\/docs\/csharp\/introvideos-csharp)\n  - [Get Started](https:\/\/code.visualstudio.com\/docs\/csharp\/get-started)\n  - [Navigate and Edit](https:\/\/code.visualstudio.com\/docs\/csharp\/navigate-edit)\n  - [IntelliCode](https:\/\/code.visualstudio.com\/docs\/csharp\/intellicode)\n  - [Refactoring](https:\/\/code.visualstudio.com\/docs\/csharp\/refactoring)\n  - [Formatting and Linting](https:\/\/code.visualstudio.com\/docs\/csharp\/formatting-linting)\n  - [Project Management](https:\/\/code.visualstudio.com\/docs\/csharp\/project-management)\n  - [Build Tools](https:\/\/code.visualstudio.com\/docs\/csharp\/build-tools)\n  - [Package Management](https:\/\/code.visualstudio.com\/docs\/csharp\/package-management)\n  - [Run and Debug](https:\/\/code.visualstudio.com\/docs\/csharp\/debugging)\n  - [Testing](https:\/\/code.visualstudio.com\/docs\/csharp\/testing)\n  - [FAQ](https:\/\/code.visualstudio.com\/docs\/csharp\/cs-dev-kit-faq)\n- [Container Tools](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#containers-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/containers\/overview)\n  - [Node.js](https:\/\/code.visualstudio.com\/docs\/containers\/quickstart-node)\n  - [Python](https:\/\/code.visualstudio.com\/docs\/containers\/quickstart-python)\n  - [ASP.NET Core](https:\/\/code.visualstudio.com\/docs\/containers\/quickstart-aspnet-core)\n  - [Debug](https:\/\/code.visualstudio.com\/docs\/containers\/debug-common)\n  - [Docker Compose](https:\/\/code.visualstudio.com\/docs\/containers\/docker-compose)\n  - [Registries](https:\/\/code.visualstudio.com\/docs\/containers\/quickstart-container-registries)\n  - [Deploy to Azure](https:\/\/code.visualstudio.com\/docs\/containers\/app-service)\n  - [Choose a Dev Environment](https:\/\/code.visualstudio.com\/docs\/containers\/choosing-dev-environment)\n  - [Customize](https:\/\/code.visualstudio.com\/docs\/containers\/reference)\n  - [Develop with Kubernetes](https:\/\/code.visualstudio.com\/docs\/containers\/bridge-to-kubernetes)\n  - [Tips and Tricks](https:\/\/code.visualstudio.com\/docs\/containers\/troubleshooting)\n- [Data Science](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#datascience-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/datascience\/overview)\n  - [Jupyter Notebooks](https:\/\/code.visualstudio.com\/docs\/datascience\/jupyter-notebooks)\n  - [Data Science Tutorial](https:\/\/code.visualstudio.com\/docs\/datascience\/data-science-tutorial)\n  - [Python Interactive](https:\/\/code.visualstudio.com\/docs\/datascience\/python-interactive)\n  - [Data Wrangler Quick Start](https:\/\/code.visualstudio.com\/docs\/datascience\/data-wrangler-quick-start)\n  - [Data Wrangler](https:\/\/code.visualstudio.com\/docs\/datascience\/data-wrangler)\n  - [PyTorch Support](https:\/\/code.visualstudio.com\/docs\/datascience\/pytorch-support)\n  - [Azure Machine Learning](https:\/\/code.visualstudio.com\/docs\/datascience\/azure-machine-learning)\n  - [Manage Jupyter Kernels](https:\/\/code.visualstudio.com\/docs\/datascience\/jupyter-kernel-management)\n  - [Jupyter Notebooks on the Web](https:\/\/code.visualstudio.com\/docs\/datascience\/notebooks-web)\n  - [Data Science in Microsoft Fabric](https:\/\/code.visualstudio.com\/docs\/datascience\/microsoft-fabric-quickstart)\n- [Intelligent Apps](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#intelligentapps-articles)\n  - [AI Toolkit Overview](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/overview)\n  - [AI Toolkit Copilot Tools](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/copilot-tools)\n  - [Models](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/models)\n  - [Playground](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/playground)\n  - [Agent Builder](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/agentbuilder)\n  - [Agent Inspector](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/agent-inspector)\n  - [Migrating from Visualizer to Agent Inspector](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/migrate-from-visualizer)\n  - [Bulk Run](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/bulkrun)\n  - [Evaluation](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/evaluation)\n  - [Fine-Tuning (Automated Setup)](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/finetune)\n  - [Fine-Tuning (Project Template)](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/finetune-legacy)\n  - [Model Conversion](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/modelconversion)\n  - [Tracing](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/tracing)\n  - [Profiling (Windows ML)](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/profiling)\n  - [FAQ](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/faq)\n  - [Reference](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#intelligentapps-reference-articles)\n    - [File Structure](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/reference\/FileStructure)\n    - [Manual Model Conversion](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/reference\/ManualModelConversion)\n    - [Manual Model Conversion on GPU](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/reference\/ManualConversionOnGPU)\n    - [Setup Environment Without AI Toolkit](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/reference\/SetupWithoutAITK)\n    - [Template Project](https:\/\/code.visualstudio.com\/docs\/intelligentapps\/reference\/TemplateProject)\n- [Azure](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#azure-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/azure\/overview)\n  - [Getting Started](https:\/\/code.visualstudio.com\/docs\/azure\/gettingstarted)\n  - [Resources View](https:\/\/code.visualstudio.com\/docs\/azure\/resourcesextension)\n  - [Deployment](https:\/\/code.visualstudio.com\/docs\/azure\/deployment)\n  - [VS Code for the Web - Azure](https:\/\/code.visualstudio.com\/docs\/azure\/vscodeforweb)\n  - [Containers](https:\/\/code.visualstudio.com\/docs\/azure\/containers)\n  - [Azure Kubernetes Service](https:\/\/code.visualstudio.com\/docs\/azure\/aksextensions)\n  - [Kubernetes](https:\/\/code.visualstudio.com\/docs\/azure\/kubernetes)\n  - [MongoDB](https:\/\/code.visualstudio.com\/docs\/azure\/mongodb)\n  - [Remote Debugging for Node.js](https:\/\/code.visualstudio.com\/docs\/azure\/remote-debugging)\n- [Remote](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#remote-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/remote\/remote-overview)\n  - [SSH](https:\/\/code.visualstudio.com\/docs\/remote\/ssh)\n  - [Dev Containers](https:\/\/code.visualstudio.com\/docs\/remote\/dev-containers)\n  - [Windows Subsystem for Linux](https:\/\/code.visualstudio.com\/docs\/remote\/wsl)\n  - [GitHub Codespaces](https:\/\/code.visualstudio.com\/docs\/remote\/codespaces)\n  - [VS Code Server](https:\/\/code.visualstudio.com\/docs\/remote\/vscode-server)\n  - [Tunnels](https:\/\/code.visualstudio.com\/docs\/remote\/tunnels)\n  - [SSH Tutorial](https:\/\/code.visualstudio.com\/docs\/remote\/ssh-tutorial)\n  - [WSL Tutorial](https:\/\/code.visualstudio.com\/docs\/remote\/wsl-tutorial)\n  - [Tips and Tricks](https:\/\/code.visualstudio.com\/docs\/remote\/troubleshooting)\n  - [FAQ](https:\/\/code.visualstudio.com\/docs\/remote\/faq)\n- [Dev Containers](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#devcontainers-articles)\n  - [Overview](https:\/\/code.visualstudio.com\/docs\/devcontainers\/containers)\n  - [Tutorial](https:\/\/code.visualstudio.com\/docs\/devcontainers\/tutorial)\n  - [Attach to Container](https:\/\/code.visualstudio.com\/docs\/devcontainers\/attach-container)\n  - [Create Dev Container](https:\/\/code.visualstudio.com\/docs\/devcontainers\/create-dev-container)\n  - [Advanced Containers](https:\/\/code.visualstudio.com\/docs\/devcontainers\/containers-advanced)\n  - [devcontainer.json](https:\/\/code.visualstudio.com\/docs\/devcontainers\/devcontainerjson-reference)\n  - [Dev Container CLI](https:\/\/code.visualstudio.com\/docs\/devcontainers\/devcontainer-cli)\n  - [Tips and Tricks](https:\/\/code.visualstudio.com\/docs\/devcontainers\/tips-and-tricks)\n  - [FAQ](https:\/\/code.visualstudio.com\/docs\/devcontainers\/faq)\n- [Reference](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#reference-articles)\n  - [Default Keyboard Shortcuts](https:\/\/code.visualstudio.com\/docs\/reference\/default-keybindings)\n  - [Default Settings](https:\/\/code.visualstudio.com\/docs\/reference\/default-settings)\n  - [Substitution Variables](https:\/\/code.visualstudio.com\/docs\/reference\/variables-reference)\n  - [Tasks Schema](https:\/\/code.visualstudio.com\/docs\/reference\/tasks-appendix)\n\nTopics\n\nCopy as Markdown\n\n- Copy as Markdown\n- View as Markdown\n\n#### On this page there are 19 sectionsOn this page\n- [Terminal shells](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminal-shells)\n- [Managing terminals](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_managing-terminals)\n- [Terminals in editor area](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminals-in-editor-area)\n- [Terminals in new windows](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminals-in-new-windows)\n- [Navigating the buffer](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_navigating-the-buffer)\n- [Links](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_links)\n- [Copy & paste](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_copy-paste)\n- [Using the mouse](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_using-the-mouse)\n- [Find](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_find)\n- [Run selected text](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_run-selected-text)\n- [Maximizing the terminal](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_maximizing-the-terminal)\n- [Select all](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_select-all)\n- [Drag and drop file paths](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_drag-and-drop-file-paths)\n- [Automating terminals with tasks](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_automating-terminals-with-tasks)\n- [Working directory](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_working-directory)\n- [Fixed dimension terminals](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_fixed-dimension-terminals)\n- [GitHub Copilot in the terminal](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_github-copilot-in-the-terminal)\n- [Next steps](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_next-steps)\n- [Common questions](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_common-questions)\n\n# Terminal Basics\nVisual Studio Code includes a full featured integrated terminal that starts at the root of your workspace. It provides integration with the editor to support features like [links](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_links) and [error detection](https:\/\/code.visualstudio.com\/docs\/debugtest\/tasks). The integrated terminal can run commands such as mkdir and git just like a standalone terminal.\n\nYou can open a terminal as follows:\n\n- From the menu, use the **Terminal** \\> **New Terminal** or **View** \\> **Terminal** menu commands.\n- From the **Command Palette** (⇧⌘P (Windows, Linux Ctrl+Shift+P)), use the **View: Toggle Terminal** command.\n- In the Explorer, you can use the **Open in Integrated Terminal** context menu command to open a new terminal from a folder.\n- To toggle the terminal panel, use the ⌃\\` (Windows, Linux Ctrl+\\`) keyboard shortcut.\n- To create a new terminal, use the ⌃⇧\\` (Windows, Linux Ctrl+Shift+\\`) keyboard shortcut.\n\nVS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar:\n\n![The integrated terminal can run commands such as mkdir and git just like a standalone terminal. VS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar.](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/integrated-terminal.png)\n\nNote\n\nIf you prefer to work outside VS Code, open an external terminal with the ⇧⌘C (Windows, Linux Ctrl+Shift+C) keyboard shortcut\n## [Terminal shells](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminal-shells)\nThe integrated terminal can use various shells installed on your machine, with the default being pulled from your system defaults. Shells are detected and presented in the terminal profiles dropdown.\n\n![A detected profile can be chosen in the dropdown next to the new terminal button. Some examples on Windows include PowerShell, Command Prompt, Git Bash and WSL](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/select-profile-dropdown.png)\n\nYou can learn more about configuring terminal shells in the [terminal profiles](https:\/\/code.visualstudio.com\/docs\/terminal\/profiles) article.\n\n## [Managing terminals](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_managing-terminals)\nThe terminal tabs UI is on the right side of the terminal view. Each terminal has an entry with its name, icon, color, and group decoration (if any).\n\n![Activating the Launch Profile button will show all detected and manually configured profiles](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/tabs.png)\n\nAdd terminal instances by selecting the **\\+** icon on the top-right of the **TERMINAL** panel, selecting a profile from the terminal dropdown, or by triggering the ⌃⇧\\` (Windows, Linux Ctrl+Shift+\\`) command. This action creates another entry in the tab list associated with that terminal.\n\nRemove terminal instances by hovering a tab and selecting the **Trash Can** button, selecting a tab item and pressing Delete, using **Terminal: Kill the Active Terminal Instance** command, or via the right-click context menu.\n\nNavigate between terminal groups using focus next ⇧⌘\\] (Windows, Linux Ctrl+PageDown) and focus previous ⇧⌘\\[ (Windows, Linux Ctrl+PageUp).\n\nIcons may appear to the right of the terminal title on the tab label when a terminal's status changes. Some examples are a bell (macOS) and for tasks, displaying a check mark when there are no errors and an X otherwise. Hover the icon to read status information, which may contain actions.\n\n### [Groups (split panes)](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_groups-split-panes)\nPlace multiple terminals side-by-side and create a group by splitting a terminal:\n\n- Hover over an entry in the list of terminals on the right and select the inline split button.\n- Right-click the context menu and select the **Split** menu option.\n- Alt and click on a tab, the **\\+** button, or the single tab on the terminal panel.\n- Trigger the ⌘\\\\ (Windows, Linux Ctrl+Shift+5) command.\n\nTip\n\nThe working directory for the new terminal depends on the terminal.integrated.splitCwd Open in VS Code Open in VS Code Insiders [setting](https:\/\/code.visualstudio.com\/docs\/configure\/settings).\n\nNavigate between terminals in a group by focusing the previous pane, ⌥⌘← (Windows, Linux Alt+Left), or the next pane, ⌥⌘→ (Windows, Linux Alt+Right).\n\nDragging and dropping tabs in the list rearranges them. Dragging a tab into the main terminal area allows moving a terminal from one group to another.\n\nMoving a terminal into its own group can be done with the **Terminal: Unsplit Terminal** command through the Command Palette or in the right-click context menu.\n\n## [Terminals in editor area](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminals-in-editor-area)\nYou can open terminals in the editor area (terminal editors) with the **Terminal: Create New Terminal in Editor Area** command, the **Terminal: Create New Terminal in Editor Area to the Side** command, or by dragging a terminal from the terminal view into the editor area. Terminal editors are presented like regular editor tabs:\n\n![Terminal editors are presented like regular text file tabs](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/terminal-editor.png)\n\nYou can have terminal editors on either side or arranged in multiple dimensions using the editor group layout system, e.g. PowerShell and WSL terminals stacked to the right of file editors:\n\n![Terminal editors are can be laid out using the editor group layout system, for example 2 terminals could sit to the right of a text editor](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/terminal-editor-grid.png)\n\nThe terminal.integrated.defaultLocation Open in VS Code Open in VS Code Insiders setting can change the default `view` or `editor` area terminal location.\n\n## [Terminals in new windows](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminals-in-new-windows)\nOpening a terminal in a new VS Code window is possible in a few different ways:\n\n- Use ⌃⇧⌥\\` (Windows, Linux Ctrl+Shift+Alt+\\`)\n- Right-click the terminal tab if you have multiple terminals, or left-click the tab if you only have a single terminal opened. Then select **Move Terminal to New Window**\n- Select the **New Terminal Window** entry that's available in several different menus\n## [Navigating the buffer](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_navigating-the-buffer)\nThe content in the terminal is called the buffer, with the section right above the bottom viewport being called \"scrollback\". The amount of scrollback kept is determined by the terminal.integrated.scrollback Open in VS Code Open in VS Code Insiders [setting](https:\/\/code.visualstudio.com\/docs\/configure\/settings) and defaults to `1000` lines.\n\nThere are various commands available to navigate around the terminal buffer:\n\n- Scroll up a line - ⌥⌘PageUp (Windows Ctrl+Alt+PageUp, Linux Ctrl+Shift+Up)\n- Scroll down a line - ⌥⌘PageDown (Windows Ctrl+Alt+PageDown, Linux Ctrl+Shift+Down)\n- Scroll up a page - PageUp (Windows, Linux Shift+PageUp)\n- Scroll down a page - PageDown (Windows, Linux Shift+PageDown)\n- Scroll to the top - ⌘Home (Windows Ctrl+Home, Linux Shift+Home)\n- Scroll to the bottom - ⌘End (Windows Ctrl+End, Linux Shift+End)\n\n**Command** navigation is also available (see [shell integration](https:\/\/code.visualstudio.com\/docs\/terminal\/shell-integration)):\n\n- Scroll to the previous command - ⌘↑ (Windows, Linux Ctrl+Up)\n- Scroll to the next command - ⌘↓ (Windows, Linux Ctrl+Down)\n\nScrolling will happen instantaneously, but can be configured to animate over a short duration with the terminal.integrated.smoothScrolling Open in VS Code Open in VS Code Insiders setting.\n\n## [Links](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_links)\nThe terminal features sophisticated link detection with editor integration and even extension contributed link handlers. Hover over a link to display an underline, then hold the Ctrl\/Cmd key and click.\n\nThese built-in link handlers are used in the following priority order:\n\n- URIs\/URLs: Links that look like URIs, such as `https:\/\/code.visualstudio.com`, `vscode:\/\/path\/to\/file` or `file:\/\/path\/to\/file` will open using the standard handler for the protocol. For example, `https` links will open the browser.\n  ![Opening a URI link will open it in the system browser](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-uri.png)\n- File links: Links to files that have been verified to exist on the system. These will open the file in a new editor tab and support many common line\/column formats such as `file:1:2`, `file:line 1, column 2`.\n  ![Activating a file link will open it in an editor](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-file.png)\n- Folder links: Links to folders are similar to file links but will open a new VS Code window at the folder.\n  ![Activating a folder link will open it in a new window](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-folder.png)\n- Word links: Fallback link type that uses the terminal.integrated.wordSeparators Open in VS Code Open in VS Code Insiders setting. The setting defines word boundaries and make nearly all text into words. Activating a word link searches the workspace for the word. If there is a single result it will open, otherwise it will present the search results. Word links are considered \"low confidence\" and will not show an underline or tooltip unless you hold the Ctrl\/Cmd key. They also have limited support for line and column suffixes.\n  ![Activating a word link 'terminal:15' will open a Quick Pick searching the workspace for all files containing 'terminal', choosing an option will open the file at line 15](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-word.png)\n\nThe **Open Detected Link** command (⇧⌘G (Windows, Linux Ctrl+Shift+G)) can be used to access links via the keyboard:\n\n![Open Detected Link opens a quick pick with all links in the viewport, split into categories](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-open-detected.png)\n\nTip\n\nIf link verification causes performance issues, like in high latency remote environments, disable it via the terminal.integrated.enableFileLinks Open in VS Code Open in VS Code Insiders [setting](https:\/\/code.visualstudio.com\/docs\/configure\/settings).\n### [Extensions handling links](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_extensions-handling-links)\nExtensions can contribute **link providers** which allow the extension to define what happens when clicked. An example of this is the [GitLens](https:\/\/marketplace.visualstudio.com\/items?itemName=eamodio.gitlens) extension detecting Git branch links.\n\n![When GitLens is installed, hovering a branch name will provide custom behavior to open the branch in the UI](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-extension.png)\n\n### [Keyboard accessibility](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_keyboard-accessibility)\nLinks are keyboard accessible through several commands that open links based on the type of link.\n\n- **Terminal: Open Last Local File Link** - Opens the most recent local file link. No default keyboard shortcut.\n- **Terminal: Open Last URL link** - Opens the most recent URI\/URL link. No default keyboard shortcut.\n- **Terminal: Open Detected Link...** - Opens a searchable Quick Pick with all detected links, including word links. The default keyboard shortcut is Ctrl\/Cmd+Shift+O, which is the same as the **Go to Symbol in Editor** keyboard shortcut.\n## [Copy & paste](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_copy-paste)\nThe keyboard shortcuts for copy and paste follow platform standards:\n\n- Linux: Ctrl+Shift+C and Ctrl+Shift+V; selection paste is available with Shift+Insert\n- macOS: Cmd+C and Cmd+V\n- Windows: Ctrl+C and Ctrl+V\n\nCopying is done automatically on selection when terminal.integrated.copyOnSelection Open in VS Code Open in VS Code Insiders is enabled.\n\nBy default, there is a warning when pasting multiple lines, which can be disabled with the terminal.integrated.enableMultiLinePasteWarning Open in VS Code Open in VS Code Insiders setting. This is only done when the shell does not support \"bracketed paste mode\". When that mode is enabled, the shell is indicating that it can handle multiple line pasting.\n\n## [Using the mouse](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_using-the-mouse)\n### [Right-click behavior](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_rightclick-behavior)\nThe right-click behavior differs based on the platform:\n\n- Linux: Show the context menu.\n- macOS: Select the word under the cursor and show the context menu.\n- Windows: Copy and drop selection if there is a selection, otherwise paste.\n\nThis can be configured using the terminal.integrated.rightClickBehavior Open in VS Code Open in VS Code Insiders setting. The options are:\n\n- `default` - Show the context menu.\n- `copyPaste` - Copy when there is a selection, otherwise paste.\n- `paste` - Paste on right-click.\n- `selectWord` - Select the word under the cursor and show the context menu.\n- `nothing` - Do nothing and pass event to terminal.\n### [Column selection](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_column-selection)\nPress Alt and left-click drag to select a rectangle of text inside the terminal instead of the regular selection of a line.\n\n### [Reposition the cursor with Alt](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_reposition-the-cursor-with-alt)\nAlt and left-click will reposition the cursor to underneath the mouse. This works by simulating arrow keystrokes, which may not work reliably for some shells or programs. This feature can be disabled with the terminal.integrated.altClickMovesCursor Open in VS Code Open in VS Code Insiders setting.\n\n### [Mouse events mode](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_mouse-events-mode)\nWhen applications running in the terminal turn on mouse events mode, such as Vim mouse mode, mouse interaction is sent to the application instead of the terminal. This means that clicking and dragging will no longer create a selection. Terminal selection can be forced by holding the Alt key on Windows and Linux, this can also be done with the Option key on macOS but requires enabling the terminal.integrated.macOptionClickForcesSelection Open in VS Code Open in VS Code Insiders setting first.\n\n## [Find](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_find)\nThe integrated terminal has find functionality that can be triggered with ⌘F (Windows, Linux Ctrl+F).\n\n![Find in the terminal will highlight all text matching the query](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/terminal-find.png)\n\nTip\n\nCtrl+F can be sent to the shell by removing the `workbench.action.terminal.focusFind` command from [commands to skip shell](https:\/\/code.visualstudio.com\/docs\/terminal\/advanced#_keyboard-shortcuts-and-the-shell).\n## [Run selected text](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_run-selected-text)\nTo use the `runSelectedText` command, select text in an editor and run the command **Terminal: Run Selected Text in Active Terminal** via the **Command Palette** (⇧⌘P (Windows, Linux Ctrl+Shift+P)), the terminal will attempt to run the selected text. If no text is selected in the active editor, the entire line that the cursor is on will run in the terminal.\n\nTip\n\nAlso run the active file using the command `workbench.action.terminal.runActiveFile`.\n## [Maximizing the terminal](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_maximizing-the-terminal)\nThe terminal view can be maximized by clicking the maximize panel size button with the upwards chevron icon. This will temporarily hide the editors and maximize the panel. This is useful to temporarily focus on a large amount of output. Some developers use VS Code as a standalone terminal by opening a new window, maximizing the panel, and hiding the side bar.\n\nNote that the panel can only be maximized if its [alignment](https:\/\/code.visualstudio.com\/docs\/configure\/custom-layout#_panel-alignment) option is set to **Center**.\n\n## [Select all](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_select-all)\nThere is a **Terminal: Select All** command, which is bound to Cmd+A on macOS, but does not have a default keyboard shortcut on Windows and Linux as it may conflict with shell hotkeys. To use Ctrl+A to select all, add this custom keyboard shortcut:\n\nJSON\n```\n{\n  \"key\": \"ctrl+a\",\n  \"command\": \"workbench.action.terminal.selectAll\",\n  \"when\": \"terminalFocus && !isMac\"\n},\n```\n## [Drag and drop file paths](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_drag-and-drop-file-paths)\nDragging a file into the terminal will input the path into the terminal, with escaping to match the active shell.\n\n## [Automating terminals with tasks](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_automating-terminals-with-tasks)\nThe [Tasks](https:\/\/code.visualstudio.com\/docs\/debugtest\/tasks) feature can be used to automate the launching of terminals, for example, the following `.vscode\/tasks.json` file will launch a Command Prompt and PowerShell terminal in a single terminal group when the window starts:\n\nJsonc\n```\n{\n  \"version\": \"2.0.0\",\n  \"presentation\": {\n    \"echo\": false,\n    \"reveal\": \"always\",\n    \"focus\": false,\n    \"panel\": \"dedicated\",\n    \"showReuseMessage\": true\n  },\n  \"tasks\": [\n    {\n      \"label\": \"Create terminals\",\n      \"dependsOn\": [\n        \"First\",\n        \"Second\"\n      ],\n      \/\/ Mark as the default build task so cmd\/ctrl+shift+b will create them\n      \"group\": {\n        \"kind\": \"build\",\n        \"isDefault\": true\n      },\n      \/\/ Try start the task on folder open\n      \"runOptions\": {\n        \"runOn\": \"folderOpen\"\n      }\n    },\n    {\n      \/\/ The name that shows up in terminal tab\n      \"label\": \"First\",\n      \/\/ The task will launch a shell\n      \"type\": \"shell\",\n      \"command\": \"\",\n      \/\/ Set the shell type\n      \"options\": {\n        \"shell\": {\n          \"executable\": \"cmd.exe\",\n          \"args\": []\n        }\n      },\n      \/\/ Mark as a background task to avoid the spinner animation on the terminal tab\n      \"isBackground\": true,\n      \"problemMatcher\": [],\n      \/\/ Create the tasks in a terminal group\n      \"presentation\": {\n        \"group\": \"my-group\"\n      }\n    },\n    {\n      \"label\": \"Second\",\n      \"type\": \"shell\",\n      \"command\": \"\",\n      \"options\": {\n        \"shell\": {\n          \"executable\": \"pwsh.exe\",\n          \"args\": []\n        }\n      },\n      \"isBackground\": true,\n      \"problemMatcher\": [],\n      \"presentation\": {\n        \"group\": \"my-group\"\n      }\n    }\n  ]\n}\n```\n\nThis file could be committed to the repository to share with other developers or created as a user task via the `workbench.action.tasks.openUserTasks` command.\n\n## [Working directory](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_working-directory)\nBy default, the terminal will open at the folder that is opened in the Explorer. The terminal.integrated.cwd Open in VS Code Open in VS Code Insiders setting allows specifying a custom path to open instead:\n\nJSON\n```\n{\n  \"terminal.integrated.cwd\": \"\/home\/user\"\n}\n```\n\nSplit terminals on Windows will start in the directory that the parent terminal started with. On macOS and Linux, split terminals will inherit the current working directory of the parent terminal. This behavior can be changed using the terminal.integrated.splitCwd Open in VS Code Open in VS Code Insiders setting:\n\nJSON\n```\n{\n  \"terminal.integrated.splitCwd\": \"workspaceRoot\"\n}\n```\n\nThere are also extensions available that give more options such as [Terminal Here](https:\/\/marketplace.visualstudio.com\/items?itemName=Tyriar.vscode-terminal-here).\n\n## [Fixed dimension terminals](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_fixed-dimension-terminals)\nThe **Terminal: Set Fixed Dimensions** command allows changing the number of columns and rows that the terminal and it's backing pseudoterminal uses. This will add scroll bars when necessary, which may lead to an unpleasant UX and is generally not recommended, but it is a common ask on Windows in particular for reading logs or long lines when paging tools aren't available.\n\nYou can also right-click on a terminal tab and select **Toggle Size to Content Width** (⌥Z (Windows, Linux Alt+Z)) to resize the number of terminal columns to the largest wrapped line in the terminal.\n\n## [GitHub Copilot in the terminal](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_github-copilot-in-the-terminal)\nIf you have access to [GitHub Copilot](https:\/\/code.visualstudio.com\/docs\/copilot\/setup), you can use it to get AI-powered help with terminal commands and shell scripting. There are several ways to use Copilot with the terminal:\n\n### [Terminal inline chat](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminal-inline-chat)\nStart an inline chat directly in the terminal to get help with shell commands:\n\n1. Open the terminal (⌃\\` (Windows, Linux Ctrl+\\`))\n2. Press ⌘I (Windows, Linux Ctrl+I) or run the **Terminal Inline Chat** command from the Command Palette\n3. Enter your question or request in natural language, such as:\n   - \"How do I find the largest files in this directory?\"\n   - \"Show me how to undo the last git commit\"\n   - \"Create a bash script to analyze log files\"\n\n![Terminal inline chat helps you quickly get and run shell commands](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/terminal-chat-2.png)\n\nWhen Copilot provides a response, you can select **Run** to execute the command directly or **Insert** to add it to the terminal for further editing.\n\nFor more information about using GitHub Copilot with the terminal, see [Use terminal inline chat](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/inline-chat#_use-terminal-inline-chat).\n\n### [Terminal chat participant](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminal-chat-participant)\nUse the dedicated `@terminal` chat participant in ask mode in the Chat view:\n\n1. Open the Chat view (⌃⌘I (Windows, Linux Ctrl+Alt+I))\n2. Start your question with `@terminal` to direct it to the terminal participant\n3. Ask about terminal commands, shell scripting, or explaining terminal output\n\nExamples:\n\n- `@terminal list the 5 largest files in this workspace`\n- `@terminal \/explain top shell command`\n- `@terminal how to grep for patterns recursively`\n### [Reference terminal context in chat](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_reference-terminal-context-in-chat)\nYou can include terminal information as context in your chat prompts:\n\n- Use `#terminalSelection` to add selected text from the terminal to your chat prompt\n- Use `#terminalLastCommand` to include the last command you ran in the terminal\n## [Next steps](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_next-steps)\nThe basics of the terminal have been covered in this document. Read on to find out more about:\n\n- [Terminal inline chat](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/inline-chat#_use-terminal-inline-chat) - AI-powered suggestions right in your terminal.\n- [Tasks](https:\/\/code.visualstudio.com\/docs\/debugtest\/tasks) - Tasks let you integrate with external tools and leverage the terminal heavily.\n- [Mastering VS Code's Terminal](https:\/\/www.growingwiththeweb.com\/2017\/03\/mastering-vscodes-terminal.html) - An external blog with plenty of power user tips for the terminal.\n- Explore terminal commands by browsing the keyboard shortcuts within VS Code (**Preferences: Open Keyboard Shortcuts** then search on 'terminal').\n## [Common questions](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_common-questions)\n### [I'm having problems launching the terminal](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_im-having-problems-launching-the-terminal)\nThere's a [dedicated troubleshooting guide](https:\/\/code.visualstudio.com\/docs\/supporting\/troubleshoot-terminal-launch) for these sorts of problems.\n\n### [How do I create an Admin terminal?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_how-do-i-create-an-admin-terminal)\nThe integrated terminal shell is running with the permissions of VS Code. If you need to run a shell command with elevated (administrator) or different permissions, use platform utilities such as `runas.exe` within a terminal.\n\nYou can learn more about customizing terminals via terminal profiles in [Configuring Profiles](https:\/\/code.visualstudio.com\/docs\/terminal\/profiles#_configuring-profiles).\n\n### [Can I add a keyboard shortcut for the Explorer's Open in Integrated Terminal command?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_can-i-add-a-keyboard-shortcut-for-the-explorers-open-in-integrated-terminal-command)\nYou can open new terminals for specific folders from the Explorer via the **Open in Integrated Terminal** context menu command.\n\n![A folder selected in the Explorer displaying the context menu with the Open in Integrated Terminal command](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/open-in-terminal-command.png)\n\nBy default, there is no keyboard shortcut associated with **Open in Integrated Terminal** but you can add your own via the Keyboard Shortcuts editor (⌘K ⌘S (Windows, Linux Ctrl+K Ctrl+S)) to add a keyboard shortcut to your `keybindings.json`.\n\nThe `keybindings.json` example below adds the keyboard shortcut Ctrl+T for `openInTerminal`.\n\nJSON\n```\n{\n  \"key\": \"ctrl+t\",\n  \"command\": \"openInTerminal\",\n  \"when\": \"filesExplorerFocus\"\n}\n```\n### [Why is nvm complaining about a prefix option when the integrated terminal is launched?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_why-is-nvm-complaining-about-a-prefix-option-when-the-integrated-terminal-is-launched)\nnvm (Node Version Manager) users often see this error for the first time inside VS Code's integrated terminal:\n\nBash\n```\nnvm is not compatible with the npm config \"prefix\" option: currently set to \"\/usr\/local\"\nRun `npm config delete prefix` or `nvm use --delete-prefix v8.9.1 --silent` to unset it\n```\n\nThis is mostly a macOS problem and does not happen in external terminals. The typical reasons for this are the following:\n\n- `npm` was globally installed using another instance of `node` that is somewhere in your path (such as `\/usr\/local\/bin\/npm`).\n- To get the development tools on the `$PATH`, VS Code will launch a bash login shell on startup. This means that your `~\/.bash_profile` has already run and when an integrated terminal launches, it will run **another** login shell, reordering the `$PATH` potentially in unexpected ways.\n\nTo resolve this issue, you need to track down where the old `npm` is installed and remove both it and its out-of-date node\\_modules. Find the `nvm` initialization script and run `which npm` before it runs, which should print the path when you launch a new terminal.\n\nOnce you have the path to npm, find the old node\\_modules by resolving the symlink by running a command something like this:\n\nBash\n```\nls -la \/usr\/local\/bin | grep \"np[mx]\"\n```\n\nThis will give you the resolved path at the end:\n\nBash\n```\n... npm -> ..\/lib\/node_modules\/npm\/bin\/npm-cli.js\n... npx -> ..\/lib\/node_modules\/npm\/bin\/npx-cli.js\n```\n\nFrom there, removing the files and relaunching VS Code should fix the issue:\n\nBash\n```\nrm \/usr\/local\/bin\/npm \/usr\/local\/lib\/node_modules\/npm\/bin\/npm-cli.js\nrm \/usr\/local\/bin\/npx \/usr\/local\/lib\/node_modules\/npm\/bin\/npx-cli.js\n```\n### [Why does macOS make a ding sound when I resize terminal split panes?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_why-does-macos-make-a-ding-sound-when-i-resize-terminal-split-panes)\nThe keyboard shortcuts ⌃⌘← and ⌃⌘→ are the defaults for resizing individual split panes in the terminal. While they work, they also cause a system \"invalid key\" sound to play due to an issue in Chromium. The [recommended workaround](https:\/\/github.com\/microsoft\/vscode\/issues\/44070#issuecomment-799716362) is to tell macOS to no-op for these keyboard shortcuts by running this in your terminal:\n\nBash\n```\nmkdir -p ~\/Library\/KeyBindings\ncat > ~\/Library\/KeyBindings\/DefaultKeyBinding.dict <<EOF\n{\n  \"@^\\UF700\" = \"noop:\";\n  \"@^\\UF701\" = \"noop:\";\n  \"@^\\UF702\" = \"noop:\";\n  \"@^\\UF703\" = \"noop:\";\n  \"@~^\\UF700\" = \"noop:\";\n  \"@~^\\UF701\" = \"noop:\";\n  \"@~^\\UF702\" = \"noop:\";\n  \"@~^\\UF703\" = \"noop:\";\n}\nEOF\n```\n### [I'm having problems with the terminal rendering. What can I do?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_im-having-problems-with-the-terminal-rendering-what-can-i-do)\nBy default, the integrated terminal will render using GPU acceleration on most machines. Typically when there are rendering problems it's an issue of something in your hardware\/OS\/drivers not playing nicely with the GPU renderer. The first thing to try is to disable GPU acceleration, trading off rendering speed for DOM-based rendering, which is more reliable:\n\nJSON\n```\n{\n  \"terminal.integrated.gpuAcceleration\": \"off\"\n}\n```\n\nSee the [GPU acceleration](https:\/\/code.visualstudio.com\/docs\/terminal\/appearance#_gpu-acceleration) section for more information.\n\n### [I see 1~ or \\[201~ when I paste something](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_i-see-1-or-201-when-i-paste-something)\nThis normally means that the program\/shell running inside the terminal requested to turn on \"bracketed paste mode\" but something doesn't support it properly. To work around this, you could run `printf \"\\e[?2004l\"` to disable it for that session or add the following to your `~\/.inputrc` file:\n\nBash\n```\nset enable-bracketed-paste off\n```\n\nAlternatively, bracketed paste mode can be forced to ignore the shell's request by turning it off with this setting:\n\nJSON\n```\n{\n  \"terminal.integrated.ignoreBracketedPasteMode\": true\n}\n```\n### [Ctrl+A, Ctrl+R output ^A, ^R on zsh](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_ctrla-ctrlr-output-a-r-on-zsh)\nThis can happen if zsh is in Vim mode instead of Emacs mode, due to setting `$EDITOR` or `$VISUAL` to `vi`\/`vim` in your init scripts.\n\nTo work around this, you have two options:\n\n- Ensure that you don't set `$EDITOR` to `vi(m)`. However, this isn't an option if you want your Git editor to work.\n- Add `bindkey -e` to your init script to set Emacs explicitly.\n### [How can I configure Cmd+. to map to Ctrl+C like macOS' built-in terminal?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_how-can-i-configure-cmd-to-map-to-ctrlc-like-macos-builtin-terminal)\nThe macOS default terminal uses Cmd+. to perform the same as Ctrl+C. To get this behavior in VS Code, add this [custom keyboard shortcut](https:\/\/code.visualstudio.com\/docs\/configure\/keybindings):\n\nJSON\n```\n{\n  \"key\": \"cmd+.\",\n  \"command\": \"workbench.action.terminal.sendSequence\",\n  \"when\": \"terminalFocus\",\n  \"args\": { \"text\": \"\\u0003\" }\n}\n```\n### [Why are the colors in the terminal not correct?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_why-are-the-colors-in-the-terminal-not-correct)\nOne of our accessibility features we enable by default is to ensure a minimum contrast ratio of at least 4.5 is met for the foreground text. This feature ensures that text is readable regardless of the shell and theme used which is not possible otherwise. To disable this feature, you can set:\n\nJSON\n```\n\"terminal.integrated.minimumContrastRatio\": 1\n```\n\nSee the [minimum contrast ratio](https:\/\/code.visualstudio.com\/docs\/terminal\/appearance#_minimum-contrast-ratio) section for more information.\n\n## Help and support\n### Still need help?\n- [![](https:\/\/code.visualstudio.com\/assets\/community\/sidebar\/stackoverflow.svg)Ask the community](https:\/\/stackoverflow.com\/questions\/tagged\/vscode)\n- [![](https:\/\/code.visualstudio.com\/assets\/community\/sidebar\/github.svg)Request features](https:\/\/go.microsoft.com\/fwlink\/?LinkID=533482)\n- [![](https:\/\/code.visualstudio.com\/assets\/community\/sidebar\/issue.svg)Report issues](https:\/\/www.github.com\/Microsoft\/vscode\/issues)\n\n### Help us improve\nEdit this page\n\n4\/8\/2026\n\n- [![RSS](https:\/\/code.visualstudio.com\/assets\/community\/sidebar\/rss.svg)RSS Feed](https:\/\/code.visualstudio.com\/feed.xml)\n- [![Stackoverflow](https:\/\/code.visualstudio.com\/assets\/community\/sidebar\/stackoverflow.svg)Ask questions](https:\/\/stackoverflow.com\/questions\/tagged\/vscode)\n- [![Twitter](https:\/\/code.visualstudio.com\/assets\/community\/sidebar\/twitter.svg)Follow @code](https:\/\/go.microsoft.com\/fwlink\/?LinkID=533687)\n- [![GitHub](https:\/\/code.visualstudio.com\/assets\/community\/sidebar\/github.svg)Request features](https:\/\/go.microsoft.com\/fwlink\/?LinkID=533482)\n- [![Issues](https:\/\/code.visualstudio.com\/assets\/community\/sidebar\/issue.svg)Report issues](https:\/\/www.github.com\/Microsoft\/vscode\/issues)\n- [![YouTube](https:\/\/code.visualstudio.com\/assets\/community\/sidebar\/youtube.svg)Watch videos](https:\/\/www.youtube.com\/channel\/UCs5Y5_7XK8HLDX0SLNwkd3w)\n\n- [![VS Code on Github](https:\/\/code.visualstudio.com\/assets\/icons\/github-icon.svg)](https:\/\/github.com\/microsoft\/vscode)\n- [![Follow us on X](https:\/\/code.visualstudio.com\/assets\/icons\/x-icon.svg)](https:\/\/go.microsoft.com\/fwlink\/?LinkID=533687)\n- [![VS Code on LinkedIn](https:\/\/code.visualstudio.com\/assets\/icons\/linkedin-icon.svg)](https:\/\/www.linkedin.com\/showcase\/vs-code)\n- [![VS Code on Bluesky](https:\/\/code.visualstudio.com\/assets\/icons\/bluesky-icon.svg)](https:\/\/bsky.app\/profile\/vscode.dev)\n- [![Join the VS Code community on Reddit](https:\/\/code.visualstudio.com\/assets\/icons\/reddit-icon.svg)](https:\/\/www.reddit.com\/r\/vscode\/)\n- [![The VS Code Insiders Podcast](https:\/\/code.visualstudio.com\/assets\/icons\/podcast-icon.svg)](https:\/\/www.vscodepodcast.com\/)\n- [![VS Code on TikTok](https:\/\/code.visualstudio.com\/assets\/icons\/tiktok-icon.svg)](https:\/\/www.tiktok.com\/@vscode)\n- [![VS Code on YouTube](https:\/\/code.visualstudio.com\/assets\/icons\/youtube-icon.svg)](https:\/\/www.youtube.com\/@code)\n\n[![Microsoft homepage](https:\/\/code.visualstudio.com\/assets\/icons\/microsoft.svg)](https:\/\/www.microsoft.com\/)\n\n- [Support](https:\/\/support.serviceshub.microsoft.com\/supportforbusiness\/create?sapId=d66407ed-3967-b000-4cfb-2c318cad363d \"Get support for VS Code\")\n- [Privacy](https:\/\/go.microsoft.com\/fwlink\/?LinkId=521839 \"View the Microsoft privacy statement\")\n- [Manage Cookies]()\n- [Terms of Use](https:\/\/www.microsoft.com\/legal\/terms-of-use \"View the Microsoft Terms of Use\")\n- [License](https:\/\/code.visualstudio.com\/License \"View the Visual Studio Code license\")\n\n- [Your Privacy Choices](https:\/\/aka.ms\/YourCaliforniaPrivacyChoices \"View Your Privacy Choices\")\n- [Consumer Health Privacy](https:\/\/go.microsoft.com\/fwlink\/?linkid=2259814 \"View the Microsoft Consumer Health Privacy policy\")","attrs_readable_markdown":"Visual Studio Code includes a full featured integrated terminal that starts at the root of your workspace. It provides integration with the editor to support features like [links](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_links) and [error detection](https:\/\/code.visualstudio.com\/docs\/debugtest\/tasks). The integrated terminal can run commands such as mkdir and git just like a standalone terminal.\n\nYou can open a terminal as follows:\n\n- From the menu, use the **Terminal** \\> **New Terminal** or **View** \\> **Terminal** menu commands.\n- From the **Command Palette** (⇧⌘P (Windows, Linux Ctrl+Shift+P)), use the **View: Toggle Terminal** command.\n- In the Explorer, you can use the **Open in Integrated Terminal** context menu command to open a new terminal from a folder.\n- To toggle the terminal panel, use the ⌃\\` (Windows, Linux Ctrl+\\`) keyboard shortcut.\n- To create a new terminal, use the ⌃⇧\\` (Windows, Linux Ctrl+Shift+\\`) keyboard shortcut.\n\nVS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar:\n\n![The integrated terminal can run commands such as mkdir and git just like a standalone terminal. VS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar.](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/integrated-terminal.png)\n\nNote\n\nIf you prefer to work outside VS Code, open an external terminal with the ⇧⌘C (Windows, Linux Ctrl+Shift+C) keyboard shortcut\n## [Terminal shells](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminal-shells)\nThe integrated terminal can use various shells installed on your machine, with the default being pulled from your system defaults. Shells are detected and presented in the terminal profiles dropdown.\n\n![A detected profile can be chosen in the dropdown next to the new terminal button. Some examples on Windows include PowerShell, Command Prompt, Git Bash and WSL](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/select-profile-dropdown.png)\n\nYou can learn more about configuring terminal shells in the [terminal profiles](https:\/\/code.visualstudio.com\/docs\/terminal\/profiles) article.\n\n## [Managing terminals](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_managing-terminals)\nThe terminal tabs UI is on the right side of the terminal view. Each terminal has an entry with its name, icon, color, and group decoration (if any).\n\n![Activating the Launch Profile button will show all detected and manually configured profiles](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/tabs.png)\n\nAdd terminal instances by selecting the **\\+** icon on the top-right of the **TERMINAL** panel, selecting a profile from the terminal dropdown, or by triggering the ⌃⇧\\` (Windows, Linux Ctrl+Shift+\\`) command. This action creates another entry in the tab list associated with that terminal.\n\nRemove terminal instances by hovering a tab and selecting the **Trash Can** button, selecting a tab item and pressing Delete, using **Terminal: Kill the Active Terminal Instance** command, or via the right-click context menu.\n\nNavigate between terminal groups using focus next ⇧⌘\\] (Windows, Linux Ctrl+PageDown) and focus previous ⇧⌘\\[ (Windows, Linux Ctrl+PageUp).\n\nIcons may appear to the right of the terminal title on the tab label when a terminal's status changes. Some examples are a bell (macOS) and for tasks, displaying a check mark when there are no errors and an X otherwise. Hover the icon to read status information, which may contain actions.\n\n### [Groups (split panes)](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_groups-split-panes)\nPlace multiple terminals side-by-side and create a group by splitting a terminal:\n\n- Hover over an entry in the list of terminals on the right and select the inline split button.\n- Right-click the context menu and select the **Split** menu option.\n- Alt and click on a tab, the **\\+** button, or the single tab on the terminal panel.\n- Trigger the ⌘\\\\ (Windows, Linux Ctrl+Shift+5) command.\n\nTip\n\nThe working directory for the new terminal depends on the    terminal.integrated.splitCwd     [setting](https:\/\/code.visualstudio.com\/docs\/configure\/settings).\n\nNavigate between terminals in a group by focusing the previous pane, ⌥⌘← (Windows, Linux Alt+Left), or the next pane, ⌥⌘→ (Windows, Linux Alt+Right).\n\nDragging and dropping tabs in the list rearranges them. Dragging a tab into the main terminal area allows moving a terminal from one group to another.\n\nMoving a terminal into its own group can be done with the **Terminal: Unsplit Terminal** command through the Command Palette or in the right-click context menu.\n\n## [Terminals in editor area](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminals-in-editor-area)\nYou can open terminals in the editor area (terminal editors) with the **Terminal: Create New Terminal in Editor Area** command, the **Terminal: Create New Terminal in Editor Area to the Side** command, or by dragging a terminal from the terminal view into the editor area. Terminal editors are presented like regular editor tabs:\n\n![Terminal editors are presented like regular text file tabs](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/terminal-editor.png)\n\nYou can have terminal editors on either side or arranged in multiple dimensions using the editor group layout system, e.g. PowerShell and WSL terminals stacked to the right of file editors:\n\n![Terminal editors are can be laid out using the editor group layout system, for example 2 terminals could sit to the right of a text editor](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/terminal-editor-grid.png)\n\nThe    terminal.integrated.defaultLocation     setting can change the default `view` or `editor` area terminal location.\n\n## [Terminals in new windows](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminals-in-new-windows)\nOpening a terminal in a new VS Code window is possible in a few different ways:\n\n- Use ⌃⇧⌥\\` (Windows, Linux Ctrl+Shift+Alt+\\`)\n- Right-click the terminal tab if you have multiple terminals, or left-click the tab if you only have a single terminal opened. Then select **Move Terminal to New Window**\n- Select the **New Terminal Window** entry that's available in several different menus\n## [Navigating the buffer](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_navigating-the-buffer)\nThe content in the terminal is called the buffer, with the section right above the bottom viewport being called \"scrollback\". The amount of scrollback kept is determined by the    terminal.integrated.scrollback     [setting](https:\/\/code.visualstudio.com\/docs\/configure\/settings) and defaults to `1000` lines.\n\nThere are various commands available to navigate around the terminal buffer:\n\n- Scroll up a line - ⌥⌘PageUp (Windows Ctrl+Alt+PageUp, Linux Ctrl+Shift+Up)\n- Scroll down a line - ⌥⌘PageDown (Windows Ctrl+Alt+PageDown, Linux Ctrl+Shift+Down)\n- Scroll up a page - PageUp (Windows, Linux Shift+PageUp)\n- Scroll down a page - PageDown (Windows, Linux Shift+PageDown)\n- Scroll to the top - ⌘Home (Windows Ctrl+Home, Linux Shift+Home)\n- Scroll to the bottom - ⌘End (Windows Ctrl+End, Linux Shift+End)\n\n**Command** navigation is also available (see [shell integration](https:\/\/code.visualstudio.com\/docs\/terminal\/shell-integration)):\n\n- Scroll to the previous command - ⌘↑ (Windows, Linux Ctrl+Up)\n- Scroll to the next command - ⌘↓ (Windows, Linux Ctrl+Down)\n\nScrolling will happen instantaneously, but can be configured to animate over a short duration with the    terminal.integrated.smoothScrolling     setting.\n\n## [Links](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_links)\nThe terminal features sophisticated link detection with editor integration and even extension contributed link handlers. Hover over a link to display an underline, then hold the Ctrl\/Cmd key and click.\n\nThese built-in link handlers are used in the following priority order:\n\n- URIs\/URLs: Links that look like URIs, such as `https:\/\/code.visualstudio.com`, `vscode:\/\/path\/to\/file` or `file:\/\/path\/to\/file` will open using the standard handler for the protocol. For example, `https` links will open the browser.\n  ![Opening a URI link will open it in the system browser](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-uri.png)\n- File links: Links to files that have been verified to exist on the system. These will open the file in a new editor tab and support many common line\/column formats such as `file:1:2`, `file:line 1, column 2`.\n  ![Activating a file link will open it in an editor](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-file.png)\n- Folder links: Links to folders are similar to file links but will open a new VS Code window at the folder.\n  ![Activating a folder link will open it in a new window](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-folder.png)\n- Word links: Fallback link type that uses the    terminal.integrated.wordSeparators     setting. The setting defines word boundaries and make nearly all text into words. Activating a word link searches the workspace for the word. If there is a single result it will open, otherwise it will present the search results. Word links are considered \"low confidence\" and will not show an underline or tooltip unless you hold the Ctrl\/Cmd key. They also have limited support for line and column suffixes.\n  ![Activating a word link 'terminal:15' will open a Quick Pick searching the workspace for all files containing 'terminal', choosing an option will open the file at line 15](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-word.png)\n\nThe **Open Detected Link** command (⇧⌘G (Windows, Linux Ctrl+Shift+G)) can be used to access links via the keyboard:\n\n![Open Detected Link opens a quick pick with all links in the viewport, split into categories](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-open-detected.png)\n\nTip\n\nIf link verification causes performance issues, like in high latency remote environments, disable it via the    terminal.integrated.enableFileLinks     [setting](https:\/\/code.visualstudio.com\/docs\/configure\/settings).\n### [Extensions handling links](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_extensions-handling-links)\nExtensions can contribute **link providers** which allow the extension to define what happens when clicked. An example of this is the [GitLens](https:\/\/marketplace.visualstudio.com\/items?itemName=eamodio.gitlens) extension detecting Git branch links.\n\n![When GitLens is installed, hovering a branch name will provide custom behavior to open the branch in the UI](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/link-extension.png)\n\n### [Keyboard accessibility](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_keyboard-accessibility)\nLinks are keyboard accessible through several commands that open links based on the type of link.\n\n- **Terminal: Open Last Local File Link** - Opens the most recent local file link. No default keyboard shortcut.\n- **Terminal: Open Last URL link** - Opens the most recent URI\/URL link. No default keyboard shortcut.\n- **Terminal: Open Detected Link...** - Opens a searchable Quick Pick with all detected links, including word links. The default keyboard shortcut is Ctrl\/Cmd+Shift+O, which is the same as the **Go to Symbol in Editor** keyboard shortcut.\n## [Copy & paste](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_copy-paste)\nThe keyboard shortcuts for copy and paste follow platform standards:\n\n- Linux: Ctrl+Shift+C and Ctrl+Shift+V; selection paste is available with Shift+Insert\n- macOS: Cmd+C and Cmd+V\n- Windows: Ctrl+C and Ctrl+V\n\nCopying is done automatically on selection when    terminal.integrated.copyOnSelection     is enabled.\n\nBy default, there is a warning when pasting multiple lines, which can be disabled with the    terminal.integrated.enableMultiLinePasteWarning     setting. This is only done when the shell does not support \"bracketed paste mode\". When that mode is enabled, the shell is indicating that it can handle multiple line pasting.\n\n## [Using the mouse](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_using-the-mouse)\n### [Right-click behavior](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_rightclick-behavior)\nThe right-click behavior differs based on the platform:\n\n- Linux: Show the context menu.\n- macOS: Select the word under the cursor and show the context menu.\n- Windows: Copy and drop selection if there is a selection, otherwise paste.\n\nThis can be configured using the    terminal.integrated.rightClickBehavior     setting. The options are:\n\n- `default` - Show the context menu.\n- `copyPaste` - Copy when there is a selection, otherwise paste.\n- `paste` - Paste on right-click.\n- `selectWord` - Select the word under the cursor and show the context menu.\n- `nothing` - Do nothing and pass event to terminal.\n### [Column selection](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_column-selection)\nPress Alt and left-click drag to select a rectangle of text inside the terminal instead of the regular selection of a line.\n\n### [Reposition the cursor with Alt](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_reposition-the-cursor-with-alt)\nAlt and left-click will reposition the cursor to underneath the mouse. This works by simulating arrow keystrokes, which may not work reliably for some shells or programs. This feature can be disabled with the    terminal.integrated.altClickMovesCursor     setting.\n\n### [Mouse events mode](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_mouse-events-mode)\nWhen applications running in the terminal turn on mouse events mode, such as Vim mouse mode, mouse interaction is sent to the application instead of the terminal. This means that clicking and dragging will no longer create a selection. Terminal selection can be forced by holding the Alt key on Windows and Linux, this can also be done with the Option key on macOS but requires enabling the    terminal.integrated.macOptionClickForcesSelection     setting first.\n\n## [Find](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_find)\nThe integrated terminal has find functionality that can be triggered with ⌘F (Windows, Linux Ctrl+F).\n\n![Find in the terminal will highlight all text matching the query](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/terminal-find.png)\n\nTip\n\nCtrl+F can be sent to the shell by removing the `workbench.action.terminal.focusFind` command from [commands to skip shell](https:\/\/code.visualstudio.com\/docs\/terminal\/advanced#_keyboard-shortcuts-and-the-shell).\n## [Run selected text](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_run-selected-text)\nTo use the `runSelectedText` command, select text in an editor and run the command **Terminal: Run Selected Text in Active Terminal** via the **Command Palette** (⇧⌘P (Windows, Linux Ctrl+Shift+P)), the terminal will attempt to run the selected text. If no text is selected in the active editor, the entire line that the cursor is on will run in the terminal.\n\nTip\n\nAlso run the active file using the command `workbench.action.terminal.runActiveFile`.\n## [Maximizing the terminal](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_maximizing-the-terminal)\nThe terminal view can be maximized by clicking the maximize panel size button with the upwards chevron icon. This will temporarily hide the editors and maximize the panel. This is useful to temporarily focus on a large amount of output. Some developers use VS Code as a standalone terminal by opening a new window, maximizing the panel, and hiding the side bar.\n\nNote that the panel can only be maximized if its [alignment](https:\/\/code.visualstudio.com\/docs\/configure\/custom-layout#_panel-alignment) option is set to **Center**.\n\n## [Select all](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_select-all)\nThere is a **Terminal: Select All** command, which is bound to Cmd+A on macOS, but does not have a default keyboard shortcut on Windows and Linux as it may conflict with shell hotkeys. To use Ctrl+A to select all, add this custom keyboard shortcut:\n```\n{\n  \"key\": \"ctrl+a\",\n  \"command\": \"workbench.action.terminal.selectAll\",\n  \"when\": \"terminalFocus && !isMac\"\n},\n```\n## [Drag and drop file paths](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_drag-and-drop-file-paths)\nDragging a file into the terminal will input the path into the terminal, with escaping to match the active shell.\n\n## [Automating terminals with tasks](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_automating-terminals-with-tasks)\nThe [Tasks](https:\/\/code.visualstudio.com\/docs\/debugtest\/tasks) feature can be used to automate the launching of terminals, for example, the following `.vscode\/tasks.json` file will launch a Command Prompt and PowerShell terminal in a single terminal group when the window starts:\n```\n{\n  \"version\": \"2.0.0\",\n  \"presentation\": {\n    \"echo\": false,\n    \"reveal\": \"always\",\n    \"focus\": false,\n    \"panel\": \"dedicated\",\n    \"showReuseMessage\": true\n  },\n  \"tasks\": [\n    {\n      \"label\": \"Create terminals\",\n      \"dependsOn\": [\n        \"First\",\n        \"Second\"\n      ],\n      \/\/ Mark as the default build task so cmd\/ctrl+shift+b will create them\n      \"group\": {\n        \"kind\": \"build\",\n        \"isDefault\": true\n      },\n      \/\/ Try start the task on folder open\n      \"runOptions\": {\n        \"runOn\": \"folderOpen\"\n      }\n    },\n    {\n      \/\/ The name that shows up in terminal tab\n      \"label\": \"First\",\n      \/\/ The task will launch a shell\n      \"type\": \"shell\",\n      \"command\": \"\",\n      \/\/ Set the shell type\n      \"options\": {\n        \"shell\": {\n          \"executable\": \"cmd.exe\",\n          \"args\": []\n        }\n      },\n      \/\/ Mark as a background task to avoid the spinner animation on the terminal tab\n      \"isBackground\": true,\n      \"problemMatcher\": [],\n      \/\/ Create the tasks in a terminal group\n      \"presentation\": {\n        \"group\": \"my-group\"\n      }\n    },\n    {\n      \"label\": \"Second\",\n      \"type\": \"shell\",\n      \"command\": \"\",\n      \"options\": {\n        \"shell\": {\n          \"executable\": \"pwsh.exe\",\n          \"args\": []\n        }\n      },\n      \"isBackground\": true,\n      \"problemMatcher\": [],\n      \"presentation\": {\n        \"group\": \"my-group\"\n      }\n    }\n  ]\n}\n```\nThis file could be committed to the repository to share with other developers or created as a user task via the `workbench.action.tasks.openUserTasks` command.\n\n## [Working directory](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_working-directory)\nBy default, the terminal will open at the folder that is opened in the Explorer. The    terminal.integrated.cwd     setting allows specifying a custom path to open instead:\n```\n{\n  \"terminal.integrated.cwd\": \"\/home\/user\"\n}\n```\nSplit terminals on Windows will start in the directory that the parent terminal started with. On macOS and Linux, split terminals will inherit the current working directory of the parent terminal. This behavior can be changed using the    terminal.integrated.splitCwd     setting:\n```\n{\n  \"terminal.integrated.splitCwd\": \"workspaceRoot\"\n}\n```\nThere are also extensions available that give more options such as [Terminal Here](https:\/\/marketplace.visualstudio.com\/items?itemName=Tyriar.vscode-terminal-here).\n\n## [Fixed dimension terminals](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_fixed-dimension-terminals)\nThe **Terminal: Set Fixed Dimensions** command allows changing the number of columns and rows that the terminal and it's backing pseudoterminal uses. This will add scroll bars when necessary, which may lead to an unpleasant UX and is generally not recommended, but it is a common ask on Windows in particular for reading logs or long lines when paging tools aren't available.\n\nYou can also right-click on a terminal tab and select **Toggle Size to Content Width** (⌥Z (Windows, Linux Alt+Z)) to resize the number of terminal columns to the largest wrapped line in the terminal.\n\n## [GitHub Copilot in the terminal](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_github-copilot-in-the-terminal)\nIf you have access to [GitHub Copilot](https:\/\/code.visualstudio.com\/docs\/copilot\/setup), you can use it to get AI-powered help with terminal commands and shell scripting. There are several ways to use Copilot with the terminal:\n\n### [Terminal inline chat](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminal-inline-chat)\nStart an inline chat directly in the terminal to get help with shell commands:\n\n1. Open the terminal (⌃\\` (Windows, Linux Ctrl+\\`))\n2. Press ⌘I (Windows, Linux Ctrl+I) or run the **Terminal Inline Chat** command from the Command Palette\n3. Enter your question or request in natural language, such as:\n   - \"How do I find the largest files in this directory?\"\n   - \"Show me how to undo the last git commit\"\n   - \"Create a bash script to analyze log files\"\n\n![Terminal inline chat helps you quickly get and run shell commands](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/terminal-chat-2.png)\n\nWhen Copilot provides a response, you can select **Run** to execute the command directly or **Insert** to add it to the terminal for further editing.\n\nFor more information about using GitHub Copilot with the terminal, see [Use terminal inline chat](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/inline-chat#_use-terminal-inline-chat).\n\n### [Terminal chat participant](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_terminal-chat-participant)\nUse the dedicated `@terminal` chat participant in ask mode in the Chat view:\n\n1. Open the Chat view (⌃⌘I (Windows, Linux Ctrl+Alt+I))\n2. Start your question with `@terminal` to direct it to the terminal participant\n3. Ask about terminal commands, shell scripting, or explaining terminal output\n\nExamples:\n\n- `@terminal list the 5 largest files in this workspace`\n- `@terminal \/explain top shell command`\n- `@terminal how to grep for patterns recursively`\n### [Reference terminal context in chat](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_reference-terminal-context-in-chat)\nYou can include terminal information as context in your chat prompts:\n\n- Use `#terminalSelection` to add selected text from the terminal to your chat prompt\n- Use `#terminalLastCommand` to include the last command you ran in the terminal\n## [Next steps](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_next-steps)\nThe basics of the terminal have been covered in this document. Read on to find out more about:\n\n- [Terminal inline chat](https:\/\/code.visualstudio.com\/docs\/copilot\/chat\/inline-chat#_use-terminal-inline-chat) - AI-powered suggestions right in your terminal.\n- [Tasks](https:\/\/code.visualstudio.com\/docs\/debugtest\/tasks) - Tasks let you integrate with external tools and leverage the terminal heavily.\n- [Mastering VS Code's Terminal](https:\/\/www.growingwiththeweb.com\/2017\/03\/mastering-vscodes-terminal.html) - An external blog with plenty of power user tips for the terminal.\n- Explore terminal commands by browsing the keyboard shortcuts within VS Code (**Preferences: Open Keyboard Shortcuts** then search on 'terminal').\n## [Common questions](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_common-questions)\n### [I'm having problems launching the terminal](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_im-having-problems-launching-the-terminal)\nThere's a [dedicated troubleshooting guide](https:\/\/code.visualstudio.com\/docs\/supporting\/troubleshoot-terminal-launch) for these sorts of problems.\n\n### [How do I create an Admin terminal?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_how-do-i-create-an-admin-terminal)\nThe integrated terminal shell is running with the permissions of VS Code. If you need to run a shell command with elevated (administrator) or different permissions, use platform utilities such as `runas.exe` within a terminal.\n\nYou can learn more about customizing terminals via terminal profiles in [Configuring Profiles](https:\/\/code.visualstudio.com\/docs\/terminal\/profiles#_configuring-profiles).\n\n### [Can I add a keyboard shortcut for the Explorer's Open in Integrated Terminal command?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_can-i-add-a-keyboard-shortcut-for-the-explorers-open-in-integrated-terminal-command)\nYou can open new terminals for specific folders from the Explorer via the **Open in Integrated Terminal** context menu command.\n\n![A folder selected in the Explorer displaying the context menu with the Open in Integrated Terminal command](https:\/\/code.visualstudio.com\/assets\/docs\/terminal\/basics\/open-in-terminal-command.png)\n\nBy default, there is no keyboard shortcut associated with **Open in Integrated Terminal** but you can add your own via the Keyboard Shortcuts editor (⌘K ⌘S (Windows, Linux Ctrl+K Ctrl+S)) to add a keyboard shortcut to your `keybindings.json`.\n\nThe `keybindings.json` example below adds the keyboard shortcut Ctrl+T for `openInTerminal`.\n```\n{\n  \"key\": \"ctrl+t\",\n  \"command\": \"openInTerminal\",\n  \"when\": \"filesExplorerFocus\"\n}\n```\n### [Why is nvm complaining about a prefix option when the integrated terminal is launched?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_why-is-nvm-complaining-about-a-prefix-option-when-the-integrated-terminal-is-launched)\nnvm (Node Version Manager) users often see this error for the first time inside VS Code's integrated terminal:\n```\nnvm is not compatible with the npm config \"prefix\" option: currently set to \"\/usr\/local\"\nRun `npm config delete prefix` or `nvm use --delete-prefix v8.9.1 --silent` to unset it\n```\nThis is mostly a macOS problem and does not happen in external terminals. The typical reasons for this are the following:\n\n- `npm` was globally installed using another instance of `node` that is somewhere in your path (such as `\/usr\/local\/bin\/npm`).\n- To get the development tools on the `$PATH`, VS Code will launch a bash login shell on startup. This means that your `~\/.bash_profile` has already run and when an integrated terminal launches, it will run **another** login shell, reordering the `$PATH` potentially in unexpected ways.\n\nTo resolve this issue, you need to track down where the old `npm` is installed and remove both it and its out-of-date node\\_modules. Find the `nvm` initialization script and run `which npm` before it runs, which should print the path when you launch a new terminal.\n\nOnce you have the path to npm, find the old node\\_modules by resolving the symlink by running a command something like this:\n```\nls -la \/usr\/local\/bin | grep \"np[mx]\"\n```\nThis will give you the resolved path at the end:\n```\n... npm -> ..\/lib\/node_modules\/npm\/bin\/npm-cli.js\n... npx -> ..\/lib\/node_modules\/npm\/bin\/npx-cli.js\n```\nFrom there, removing the files and relaunching VS Code should fix the issue:\n```\nrm \/usr\/local\/bin\/npm \/usr\/local\/lib\/node_modules\/npm\/bin\/npm-cli.js\nrm \/usr\/local\/bin\/npx \/usr\/local\/lib\/node_modules\/npm\/bin\/npx-cli.js\n```\n### [Why does macOS make a ding sound when I resize terminal split panes?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_why-does-macos-make-a-ding-sound-when-i-resize-terminal-split-panes)\nThe keyboard shortcuts ⌃⌘← and ⌃⌘→ are the defaults for resizing individual split panes in the terminal. While they work, they also cause a system \"invalid key\" sound to play due to an issue in Chromium. The [recommended workaround](https:\/\/github.com\/microsoft\/vscode\/issues\/44070#issuecomment-799716362) is to tell macOS to no-op for these keyboard shortcuts by running this in your terminal:\n```\nmkdir -p ~\/Library\/KeyBindings\ncat > ~\/Library\/KeyBindings\/DefaultKeyBinding.dict <<EOF\n{\n  \"@^\\UF700\" = \"noop:\";\n  \"@^\\UF701\" = \"noop:\";\n  \"@^\\UF702\" = \"noop:\";\n  \"@^\\UF703\" = \"noop:\";\n  \"@~^\\UF700\" = \"noop:\";\n  \"@~^\\UF701\" = \"noop:\";\n  \"@~^\\UF702\" = \"noop:\";\n  \"@~^\\UF703\" = \"noop:\";\n}\nEOF\n```\n### [I'm having problems with the terminal rendering. What can I do?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_im-having-problems-with-the-terminal-rendering-what-can-i-do)\nBy default, the integrated terminal will render using GPU acceleration on most machines. Typically when there are rendering problems it's an issue of something in your hardware\/OS\/drivers not playing nicely with the GPU renderer. The first thing to try is to disable GPU acceleration, trading off rendering speed for DOM-based rendering, which is more reliable:\n```\n{\n  \"terminal.integrated.gpuAcceleration\": \"off\"\n}\n```\nSee the [GPU acceleration](https:\/\/code.visualstudio.com\/docs\/terminal\/appearance#_gpu-acceleration) section for more information.\n\n### [I see 1~ or \\[201~ when I paste something](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_i-see-1-or-201-when-i-paste-something)\nThis normally means that the program\/shell running inside the terminal requested to turn on \"bracketed paste mode\" but something doesn't support it properly. To work around this, you could run `printf \"\\e[?2004l\"` to disable it for that session or add the following to your `~\/.inputrc` file:\n```\nset enable-bracketed-paste off\n```\nAlternatively, bracketed paste mode can be forced to ignore the shell's request by turning it off with this setting:\n```\n{\n  \"terminal.integrated.ignoreBracketedPasteMode\": true\n}\n```\n### [Ctrl+A, Ctrl+R output ^A, ^R on zsh](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_ctrla-ctrlr-output-a-r-on-zsh)\nThis can happen if zsh is in Vim mode instead of Emacs mode, due to setting `$EDITOR` or `$VISUAL` to `vi`\/`vim` in your init scripts.\n\nTo work around this, you have two options:\n\n- Ensure that you don't set `$EDITOR` to `vi(m)`. However, this isn't an option if you want your Git editor to work.\n- Add `bindkey -e` to your init script to set Emacs explicitly.\n### [How can I configure Cmd+. to map to Ctrl+C like macOS' built-in terminal?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_how-can-i-configure-cmd-to-map-to-ctrlc-like-macos-builtin-terminal)\nThe macOS default terminal uses Cmd+. to perform the same as Ctrl+C. To get this behavior in VS Code, add this [custom keyboard shortcut](https:\/\/code.visualstudio.com\/docs\/configure\/keybindings):\n```\n{\n  \"key\": \"cmd+.\",\n  \"command\": \"workbench.action.terminal.sendSequence\",\n  \"when\": \"terminalFocus\",\n  \"args\": { \"text\": \"\\u0003\" }\n}\n```\n### [Why are the colors in the terminal not correct?](https:\/\/code.visualstudio.com\/docs\/terminal\/basics#_why-are-the-colors-in-the-terminal-not-correct)\nOne of our accessibility features we enable by default is to ensure a minimum contrast ratio of at least 4.5 is met for the foreground text. This feature ensures that text is readable regardless of the shell and theme used which is not possible otherwise. To disable this feature, you can set:\n```\n\"terminal.integrated.minimumContrastRatio\": 1\n```\nSee the [minimum contrast ratio](https:\/\/code.visualstudio.com\/docs\/terminal\/appearance#_minimum-contrast-ratio) section for more information.\n\n4\/8\/2026","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

8 hours ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://code.visualstudio.com/docs/terminal/basics
Last Crawled	2026-04-12 18:08:48 (8 hours ago)
First Indexed	2022-07-19 18:42:24 (3 years ago)
HTTP Status Code	200
Meta Title	Terminal Basics
Meta Description	Visual Studio Code has an integrated terminal to enable working in your shell of choice without leaving the editor.
Meta Canonical	null
Boilerpipe Text	Visual Studio Code includes a full featured integrated terminal that starts at the root of your workspace. It provides integration with the editor to support features like links and error detection . The integrated terminal can run commands such as mkdir and git just like a standalone terminal. You can open a terminal as follows: From the menu, use the Terminal > New Terminal or View > Terminal menu commands. From the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ), use the View: Toggle Terminal command. In the Explorer, you can use the Open in Integrated Terminal context menu command to open a new terminal from a folder. To toggle the terminal panel, use the ⌃` (Windows, Linux Ctrl+` ) keyboard shortcut. To create a new terminal, use the ⌃⇧` (Windows, Linux Ctrl+Shift+` ) keyboard shortcut. VS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar: Note If you prefer to work outside VS Code, open an external terminal with the ⇧⌘C (Windows, Linux Ctrl+Shift+C ) keyboard shortcut Terminal shells The integrated terminal can use various shells installed on your machine, with the default being pulled from your system defaults. Shells are detected and presented in the terminal profiles dropdown. You can learn more about configuring terminal shells in the terminal profiles article. Managing terminals The terminal tabs UI is on the right side of the terminal view. Each terminal has an entry with its name, icon, color, and group decoration (if any). Add terminal instances by selecting the + icon on the top-right of the TERMINAL panel, selecting a profile from the terminal dropdown, or by triggering the ⌃⇧` (Windows, Linux Ctrl+Shift+` ) command. This action creates another entry in the tab list associated with that terminal. Remove terminal instances by hovering a tab and selecting the Trash Can button, selecting a tab item and pressing Delete , using Terminal: Kill the Active Terminal Instance command, or via the right-click context menu. Navigate between terminal groups using focus next ⇧⌘] (Windows, Linux Ctrl+PageDown ) and focus previous ⇧⌘[ (Windows, Linux Ctrl+PageUp ) . Icons may appear to the right of the terminal title on the tab label when a terminal's status changes. Some examples are a bell (macOS) and for tasks, displaying a check mark when there are no errors and an X otherwise. Hover the icon to read status information, which may contain actions. Groups (split panes) Place multiple terminals side-by-side and create a group by splitting a terminal: Hover over an entry in the list of terminals on the right and select the inline split button. Right-click the context menu and select the Split menu option. Alt and click on a tab, the + button, or the single tab on the terminal panel. Trigger the ⌘\ (Windows, Linux Ctrl+Shift+5 ) command. Tip The working directory for the new terminal depends on the terminal.integrated.splitCwd setting . Navigate between terminals in a group by focusing the previous pane, ⌥⌘← (Windows, Linux Alt+Left ) , or the next pane, ⌥⌘→ (Windows, Linux Alt+Right ) . Dragging and dropping tabs in the list rearranges them. Dragging a tab into the main terminal area allows moving a terminal from one group to another. Moving a terminal into its own group can be done with the Terminal: Unsplit Terminal command through the Command Palette or in the right-click context menu. Terminals in editor area You can open terminals in the editor area (terminal editors) with the Terminal: Create New Terminal in Editor Area command, the Terminal: Create New Terminal in Editor Area to the Side command, or by dragging a terminal from the terminal view into the editor area. Terminal editors are presented like regular editor tabs: You can have terminal editors on either side or arranged in multiple dimensions using the editor group layout system, e.g. PowerShell and WSL terminals stacked to the right of file editors: The terminal.integrated.defaultLocation setting can change the default view or editor area terminal location. Terminals in new windows Opening a terminal in a new VS Code window is possible in a few different ways: Use ⌃⇧⌥` (Windows, Linux Ctrl+Shift+Alt+` ) Right-click the terminal tab if you have multiple terminals, or left-click the tab if you only have a single terminal opened. Then select Move Terminal to New Window Select the New Terminal Window entry that's available in several different menus Navigating the buffer The content in the terminal is called the buffer, with the section right above the bottom viewport being called "scrollback". The amount of scrollback kept is determined by the terminal.integrated.scrollback setting and defaults to 1000 lines. There are various commands available to navigate around the terminal buffer: Scroll up a line - ⌥⌘PageUp (Windows Ctrl+Alt+PageUp , Linux Ctrl+Shift+Up ) Scroll down a line - ⌥⌘PageDown (Windows Ctrl+Alt+PageDown , Linux Ctrl+Shift+Down ) Scroll up a page - PageUp (Windows, Linux Shift+PageUp ) Scroll down a page - PageDown (Windows, Linux Shift+PageDown ) Scroll to the top - ⌘Home (Windows Ctrl+Home , Linux Shift+Home ) Scroll to the bottom - ⌘End (Windows Ctrl+End , Linux Shift+End ) Command navigation is also available (see shell integration ): Scroll to the previous command - ⌘↑ (Windows, Linux Ctrl+Up ) Scroll to the next command - ⌘↓ (Windows, Linux Ctrl+Down ) Scrolling will happen instantaneously, but can be configured to animate over a short duration with the terminal.integrated.smoothScrolling setting. Links The terminal features sophisticated link detection with editor integration and even extension contributed link handlers. Hover over a link to display an underline, then hold the Ctrl / Cmd key and click. These built-in link handlers are used in the following priority order: URIs/URLs: Links that look like URIs, such as https://code.visualstudio.com , vscode://path/to/file or file://path/to/file will open using the standard handler for the protocol. For example, https links will open the browser. File links: Links to files that have been verified to exist on the system. These will open the file in a new editor tab and support many common line/column formats such as file:1:2 , file:line 1, column 2 . Folder links: Links to folders are similar to file links but will open a new VS Code window at the folder. Word links: Fallback link type that uses the terminal.integrated.wordSeparators setting. The setting defines word boundaries and make nearly all text into words. Activating a word link searches the workspace for the word. If there is a single result it will open, otherwise it will present the search results. Word links are considered "low confidence" and will not show an underline or tooltip unless you hold the Ctrl / Cmd key. They also have limited support for line and column suffixes. The Open Detected Link command ( ⇧⌘G (Windows, Linux Ctrl+Shift+G ) ) can be used to access links via the keyboard: Tip If link verification causes performance issues, like in high latency remote environments, disable it via the terminal.integrated.enableFileLinks setting . Extensions handling links Extensions can contribute link providers which allow the extension to define what happens when clicked. An example of this is the GitLens extension detecting Git branch links. Keyboard accessibility Links are keyboard accessible through several commands that open links based on the type of link. Terminal: Open Last Local File Link - Opens the most recent local file link. No default keyboard shortcut. Terminal: Open Last URL link - Opens the most recent URI/URL link. No default keyboard shortcut. Terminal: Open Detected Link... - Opens a searchable Quick Pick with all detected links, including word links. The default keyboard shortcut is Ctrl/Cmd+Shift+O , which is the same as the Go to Symbol in Editor keyboard shortcut. Copy & paste The keyboard shortcuts for copy and paste follow platform standards: Linux: Ctrl+Shift+C and Ctrl+Shift+V ; selection paste is available with Shift+Insert macOS: Cmd+C and Cmd+V Windows: Ctrl+C and Ctrl+V Copying is done automatically on selection when terminal.integrated.copyOnSelection is enabled. By default, there is a warning when pasting multiple lines, which can be disabled with the terminal.integrated.enableMultiLinePasteWarning setting. This is only done when the shell does not support "bracketed paste mode". When that mode is enabled, the shell is indicating that it can handle multiple line pasting. Using the mouse Right-click behavior The right-click behavior differs based on the platform: Linux: Show the context menu. macOS: Select the word under the cursor and show the context menu. Windows: Copy and drop selection if there is a selection, otherwise paste. This can be configured using the terminal.integrated.rightClickBehavior setting. The options are: default - Show the context menu. copyPaste - Copy when there is a selection, otherwise paste. paste - Paste on right-click. selectWord - Select the word under the cursor and show the context menu. nothing - Do nothing and pass event to terminal. Column selection Press Alt and left-click drag to select a rectangle of text inside the terminal instead of the regular selection of a line. Reposition the cursor with Alt Alt and left-click will reposition the cursor to underneath the mouse. This works by simulating arrow keystrokes, which may not work reliably for some shells or programs. This feature can be disabled with the terminal.integrated.altClickMovesCursor setting. Mouse events mode When applications running in the terminal turn on mouse events mode, such as Vim mouse mode, mouse interaction is sent to the application instead of the terminal. This means that clicking and dragging will no longer create a selection. Terminal selection can be forced by holding the Alt key on Windows and Linux, this can also be done with the Option key on macOS but requires enabling the terminal.integrated.macOptionClickForcesSelection setting first. Find The integrated terminal has find functionality that can be triggered with ⌘F (Windows, Linux Ctrl+F ) . Tip Ctrl+F can be sent to the shell by removing the workbench.action.terminal.focusFind command from commands to skip shell . Run selected text To use the runSelectedText command, select text in an editor and run the command Terminal: Run Selected Text in Active Terminal via the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ), the terminal will attempt to run the selected text. If no text is selected in the active editor, the entire line that the cursor is on will run in the terminal. Tip Also run the active file using the command workbench.action.terminal.runActiveFile . Maximizing the terminal The terminal view can be maximized by clicking the maximize panel size button with the upwards chevron icon. This will temporarily hide the editors and maximize the panel. This is useful to temporarily focus on a large amount of output. Some developers use VS Code as a standalone terminal by opening a new window, maximizing the panel, and hiding the side bar. Note that the panel can only be maximized if its alignment option is set to Center . Select all There is a Terminal: Select All command, which is bound to Cmd+A on macOS, but does not have a default keyboard shortcut on Windows and Linux as it may conflict with shell hotkeys. To use Ctrl+A to select all, add this custom keyboard shortcut: { "key" : "ctrl+a" , "command" : "workbench.action.terminal.selectAll" , "when" : "terminalFocus && !isMac" }, Drag and drop file paths Dragging a file into the terminal will input the path into the terminal, with escaping to match the active shell. Automating terminals with tasks The Tasks feature can be used to automate the launching of terminals, for example, the following .vscode/tasks.json file will launch a Command Prompt and PowerShell terminal in a single terminal group when the window starts: { "version" : "2.0.0" , "presentation" : { "echo" : false , "reveal" : "always" , "focus" : false , "panel" : "dedicated" , "showReuseMessage" : true }, "tasks" : [ { "label" : "Create terminals" , "dependsOn" : [ "First" , "Second" ], // Mark as the default build task so cmd/ctrl+shift+b will create them "group" : { "kind" : "build" , "isDefault" : true }, // Try start the task on folder open "runOptions" : { "runOn" : "folderOpen" } }, { // The name that shows up in terminal tab "label" : "First" , // The task will launch a shell "type" : "shell" , "command" : "" , // Set the shell type "options" : { "shell" : { "executable" : "cmd.exe" , "args" : [] } }, // Mark as a background task to avoid the spinner animation on the terminal tab "isBackground" : true , "problemMatcher" : [], // Create the tasks in a terminal group "presentation" : { "group" : "my-group" } }, { "label" : "Second" , "type" : "shell" , "command" : "" , "options" : { "shell" : { "executable" : "pwsh.exe" , "args" : [] } }, "isBackground" : true , "problemMatcher" : [], "presentation" : { "group" : "my-group" } } ] } This file could be committed to the repository to share with other developers or created as a user task via the workbench.action.tasks.openUserTasks command. Working directory By default, the terminal will open at the folder that is opened in the Explorer. The terminal.integrated.cwd setting allows specifying a custom path to open instead: { "terminal.integrated.cwd" : "/home/user" } Split terminals on Windows will start in the directory that the parent terminal started with. On macOS and Linux, split terminals will inherit the current working directory of the parent terminal. This behavior can be changed using the terminal.integrated.splitCwd setting: { "terminal.integrated.splitCwd" : "workspaceRoot" } There are also extensions available that give more options such as Terminal Here . Fixed dimension terminals The Terminal: Set Fixed Dimensions command allows changing the number of columns and rows that the terminal and it's backing pseudoterminal uses. This will add scroll bars when necessary, which may lead to an unpleasant UX and is generally not recommended, but it is a common ask on Windows in particular for reading logs or long lines when paging tools aren't available. You can also right-click on a terminal tab and select Toggle Size to Content Width ( ⌥Z (Windows, Linux Alt+Z ) ) to resize the number of terminal columns to the largest wrapped line in the terminal. GitHub Copilot in the terminal If you have access to GitHub Copilot , you can use it to get AI-powered help with terminal commands and shell scripting. There are several ways to use Copilot with the terminal: Terminal inline chat Start an inline chat directly in the terminal to get help with shell commands: Open the terminal ( ⌃` (Windows, Linux Ctrl+` ) ) Press ⌘I (Windows, Linux Ctrl+I ) or run the Terminal Inline Chat command from the Command Palette Enter your question or request in natural language, such as: "How do I find the largest files in this directory?" "Show me how to undo the last git commit" "Create a bash script to analyze log files" When Copilot provides a response, you can select Run to execute the command directly or Insert to add it to the terminal for further editing. For more information about using GitHub Copilot with the terminal, see Use terminal inline chat . Terminal chat participant Use the dedicated @terminal chat participant in ask mode in the Chat view: Open the Chat view ( ⌃⌘I (Windows, Linux Ctrl+Alt+I ) ) Start your question with @terminal to direct it to the terminal participant Ask about terminal commands, shell scripting, or explaining terminal output Examples: @terminal list the 5 largest files in this workspace @terminal /explain top shell command @terminal how to grep for patterns recursively Reference terminal context in chat You can include terminal information as context in your chat prompts: Use #terminalSelection to add selected text from the terminal to your chat prompt Use #terminalLastCommand to include the last command you ran in the terminal Next steps The basics of the terminal have been covered in this document. Read on to find out more about: Terminal inline chat - AI-powered suggestions right in your terminal. Tasks - Tasks let you integrate with external tools and leverage the terminal heavily. Mastering VS Code's Terminal - An external blog with plenty of power user tips for the terminal. Explore terminal commands by browsing the keyboard shortcuts within VS Code ( Preferences: Open Keyboard Shortcuts then search on 'terminal'). Common questions I'm having problems launching the terminal There's a dedicated troubleshooting guide for these sorts of problems. How do I create an Admin terminal? The integrated terminal shell is running with the permissions of VS Code. If you need to run a shell command with elevated (administrator) or different permissions, use platform utilities such as runas.exe within a terminal. You can learn more about customizing terminals via terminal profiles in Configuring Profiles . Can I add a keyboard shortcut for the Explorer's Open in Integrated Terminal command? You can open new terminals for specific folders from the Explorer via the Open in Integrated Terminal context menu command. By default, there is no keyboard shortcut associated with Open in Integrated Terminal but you can add your own via the Keyboard Shortcuts editor ( ⌘K ⌘S (Windows, Linux Ctrl+K Ctrl+S ) ) to add a keyboard shortcut to your keybindings.json . The keybindings.json example below adds the keyboard shortcut Ctrl+T for openInTerminal . { "key" : "ctrl+t" , "command" : "openInTerminal" , "when" : "filesExplorerFocus" } Why is nvm complaining about a prefix option when the integrated terminal is launched? nvm (Node Version Manager) users often see this error for the first time inside VS Code's integrated terminal: nvm is not compatible with the npm config "prefix" option: currently set to "/usr/local" Run ` npm config delete prefix` or ` nvm use --delete-prefix v8.9.1 --silent ` to unset it This is mostly a macOS problem and does not happen in external terminals. The typical reasons for this are the following: npm was globally installed using another instance of node that is somewhere in your path (such as /usr/local/bin/npm ). To get the development tools on the $PATH , VS Code will launch a bash login shell on startup. This means that your ~/.bash_profile has already run and when an integrated terminal launches, it will run another login shell, reordering the $PATH potentially in unexpected ways. To resolve this issue, you need to track down where the old npm is installed and remove both it and its out-of-date node_modules. Find the nvm initialization script and run which npm before it runs, which should print the path when you launch a new terminal. Once you have the path to npm, find the old node_modules by resolving the symlink by running a command something like this: ls -la /usr/local/bin \| grep "np[mx]" This will give you the resolved path at the end: ... npm -> ../lib/node_modules/npm/bin/npm-cli.js ... npx -> ../lib/node_modules/npm/bin/npx-cli.js From there, removing the files and relaunching VS Code should fix the issue: rm /usr/local/bin/npm /usr/local/lib/node_modules/npm/bin/npm-cli.js rm /usr/local/bin/npx /usr/local/lib/node_modules/npm/bin/npx-cli.js Why does macOS make a ding sound when I resize terminal split panes? The keyboard shortcuts ⌃⌘← and ⌃⌘→ are the defaults for resizing individual split panes in the terminal. While they work, they also cause a system "invalid key" sound to play due to an issue in Chromium. The recommended workaround is to tell macOS to no-op for these keyboard shortcuts by running this in your terminal: mkdir -p ~/Library/KeyBindings cat > ~/Library/KeyBindings/DefaultKeyBinding.dict << EOF { "@^\UF700" = "noop:"; "@^\UF701" = "noop:"; "@^\UF702" = "noop:"; "@^\UF703" = "noop:"; "@~^\UF700" = "noop:"; "@~^\UF701" = "noop:"; "@~^\UF702" = "noop:"; "@~^\UF703" = "noop:"; } EOF I'm having problems with the terminal rendering. What can I do? By default, the integrated terminal will render using GPU acceleration on most machines. Typically when there are rendering problems it's an issue of something in your hardware/OS/drivers not playing nicely with the GPU renderer. The first thing to try is to disable GPU acceleration, trading off rendering speed for DOM-based rendering, which is more reliable: { "terminal.integrated.gpuAcceleration" : "off" } See the GPU acceleration section for more information. I see 1~ or [201~ when I paste something This normally means that the program/shell running inside the terminal requested to turn on "bracketed paste mode" but something doesn't support it properly. To work around this, you could run printf "\e[?2004l" to disable it for that session or add the following to your ~/.inputrc file: set enable-bracketed-paste off Alternatively, bracketed paste mode can be forced to ignore the shell's request by turning it off with this setting: { "terminal.integrated.ignoreBracketedPasteMode" : true } Ctrl+A, Ctrl+R output ^A, ^R on zsh This can happen if zsh is in Vim mode instead of Emacs mode, due to setting $EDITOR or $VISUAL to vi / vim in your init scripts. To work around this, you have two options: Ensure that you don't set $EDITOR to vi(m) . However, this isn't an option if you want your Git editor to work. Add bindkey -e to your init script to set Emacs explicitly. How can I configure Cmd+. to map to Ctrl+C like macOS' built-in terminal? The macOS default terminal uses Cmd+. to perform the same as Ctrl+C . To get this behavior in VS Code, add this custom keyboard shortcut : { "key" : "cmd+." , "command" : "workbench.action.terminal.sendSequence" , "when" : "terminalFocus" , "args" : { "text" : " \u0003 " } } Why are the colors in the terminal not correct? One of our accessibility features we enable by default is to ensure a minimum contrast ratio of at least 4.5 is met for the foreground text. This feature ensures that text is readable regardless of the shell and theme used which is not possible otherwise. To disable this feature, you can set: "terminal.integrated.minimumContrastRatio" : 1 See the minimum contrast ratio section for more information. 4/8/2026
Markdown	[Visual Studio Code](https://code.visualstudio.com/) - [Docs](https://code.visualstudio.com/docs) - [Updates](https://code.visualstudio.com/updates) - [Blog](https://code.visualstudio.com/blogs) - [API](https://code.visualstudio.com/api) - [Extensions](https://marketplace.visualstudio.com/VSCode) - [MCP](https://code.visualstudio.com/mcp) - [FAQ](https://code.visualstudio.com/docs/supporting/faq) - [Learn](https://code.visualstudio.com/learn) - [Events](https://aka.ms/vscode/live) - [Download](https://code.visualstudio.com/Download) ![](https://code.visualstudio.com/assets/icons/search-dark.svg) ![](https://code.visualstudio.com/assets/icons/search.svg) Search Ctrl+Shift+P ![Switch to the dark theme](https://code.visualstudio.com/assets/icons/theme-light.svg) ![Switch to the light theme](https://code.visualstudio.com/assets/icons/theme-dark.svg) [Download](https://code.visualstudio.com/Download) Explore Agentic Development - [Join a GitHub Copilot Dev Day near you\!](https://aka.ms/githubcopilotdevdays) Dismiss this update #### Documentation - [Overview](https://code.visualstudio.com/docs) - [Setup](https://code.visualstudio.com/docs/terminal/basics#setup-articles) - [Overview](https://code.visualstudio.com/docs/setup/setup-overview) - [Linux](https://code.visualstudio.com/docs/setup/linux) - [macOS](https://code.visualstudio.com/docs/setup/mac) - [Windows](https://code.visualstudio.com/docs/setup/windows) - [VS Code for the Web](https://code.visualstudio.com/docs/setup/vscode-web) - [Raspberry Pi](https://code.visualstudio.com/docs/setup/raspberry-pi) - [Network](https://code.visualstudio.com/docs/setup/network) - [Additional Components](https://code.visualstudio.com/docs/setup/additional-components) - [Uninstall](https://code.visualstudio.com/docs/setup/uninstall) - [Get Started](https://code.visualstudio.com/docs/terminal/basics#getstarted-articles) - [VS Code Tutorial](https://code.visualstudio.com/docs/getstarted/getting-started) - [Copilot Quickstart](https://code.visualstudio.com/docs/getstarted/copilot-quickstart) - [User Interface](https://code.visualstudio.com/docs/getstarted/userinterface) - [Personalize VS Code](https://code.visualstudio.com/docs/getstarted/personalize-vscode) - [Install Extensions](https://code.visualstudio.com/docs/getstarted/extensions) - [Tips and Tricks](https://code.visualstudio.com/docs/getstarted/tips-and-tricks) - [Intro Videos](https://code.visualstudio.com/docs/getstarted/introvideos) - [GitHub Copilot](https://code.visualstudio.com/docs/terminal/basics#copilot-articles) - [Overview](https://code.visualstudio.com/docs/copilot/overview) - [Setup](https://code.visualstudio.com/docs/copilot/setup) - [Quickstart](https://code.visualstudio.com/docs/copilot/getting-started) - [Concepts](https://code.visualstudio.com/docs/terminal/basics#copilot-concepts-articles) - [Overview](https://code.visualstudio.com/docs/copilot/concepts/overview) - [Language Models](https://code.visualstudio.com/docs/copilot/concepts/language-models) - [Context](https://code.visualstudio.com/docs/copilot/concepts/context) - [Tools](https://code.visualstudio.com/docs/copilot/concepts/tools) - [Agents](https://code.visualstudio.com/docs/copilot/concepts/agents) - [Customization](https://code.visualstudio.com/docs/copilot/concepts/customization) - [Trust & Safety](https://code.visualstudio.com/docs/copilot/concepts/trust-and-safety) - [Agents](https://code.visualstudio.com/docs/terminal/basics#copilot-agents-articles) - [Overview](https://code.visualstudio.com/docs/copilot/agents/overview) - [Agents Tutorial](https://code.visualstudio.com/docs/copilot/agents/agents-tutorial) - [Planning](https://code.visualstudio.com/docs/copilot/agents/planning) - [Memory](https://code.visualstudio.com/docs/copilot/agents/memory) - [Tools](https://code.visualstudio.com/docs/copilot/agents/agent-tools) - [Subagents](https://code.visualstudio.com/docs/copilot/agents/subagents) - [Local Agents](https://code.visualstudio.com/docs/copilot/agents/local-agents) - [Copilot CLI](https://code.visualstudio.com/docs/copilot/agents/copilot-cli) - [Cloud Agents](https://code.visualstudio.com/docs/copilot/agents/cloud-agents) - [Third-Party Agents](https://code.visualstudio.com/docs/copilot/agents/third-party-agents) - [Chat](https://code.visualstudio.com/docs/terminal/basics#copilot-chat-articles) - [Overview](https://code.visualstudio.com/docs/copilot/chat/copilot-chat) - [Chat Sessions](https://code.visualstudio.com/docs/copilot/chat/chat-sessions) - [Add Context](https://code.visualstudio.com/docs/copilot/chat/copilot-chat-context) - [Inline Chat](https://code.visualstudio.com/docs/copilot/chat/inline-chat) - [Review Edits](https://code.visualstudio.com/docs/copilot/chat/review-code-edits) - [Checkpoints](https://code.visualstudio.com/docs/copilot/chat/chat-checkpoints) - [Debug Chat Interactions](https://code.visualstudio.com/docs/copilot/chat/chat-debug-view) - [Prompt Examples](https://code.visualstudio.com/docs/copilot/chat/prompt-examples) - [Customization](https://code.visualstudio.com/docs/terminal/basics#copilot-customization-articles) - [Overview](https://code.visualstudio.com/docs/copilot/customization/overview) - [Instructions](https://code.visualstudio.com/docs/copilot/customization/custom-instructions) - [Prompt Files](https://code.visualstudio.com/docs/copilot/customization/prompt-files) - [Custom Agents](https://code.visualstudio.com/docs/copilot/customization/custom-agents) - [Agent Skills](https://code.visualstudio.com/docs/copilot/customization/agent-skills) - [Language Models](https://code.visualstudio.com/docs/copilot/customization/language-models) - [MCP](https://code.visualstudio.com/docs/copilot/customization/mcp-servers) - [Hooks](https://code.visualstudio.com/docs/copilot/customization/hooks) - [Plugins](https://code.visualstudio.com/docs/copilot/customization/agent-plugins) - [Guides & Tutorials](https://code.visualstudio.com/docs/terminal/basics#copilot-guides-articles) - [Context Engineering](https://code.visualstudio.com/docs/copilot/guides/context-engineering-guide) - [Customize AI](https://code.visualstudio.com/docs/copilot/guides/customize-copilot-guide) - [Test-Driven Development](https://code.visualstudio.com/docs/copilot/guides/test-driven-development-guide) - [Edit Notebooks with AI](https://code.visualstudio.com/docs/copilot/guides/notebooks-with-ai) - [Test with AI](https://code.visualstudio.com/docs/copilot/guides/test-with-copilot) - [Test Web Apps with Browser Tools](https://code.visualstudio.com/docs/copilot/guides/browser-agent-testing-guide) - [Debug with AI](https://code.visualstudio.com/docs/copilot/guides/debug-with-copilot) - [MCP Dev Guide](https://code.visualstudio.com/docs/copilot/guides/mcp-developer-guide) - [Monitoring](https://code.visualstudio.com/docs/copilot/guides/monitoring-agents) - [Inline Suggestions](https://code.visualstudio.com/docs/copilot/ai-powered-suggestions) - [Smart Actions](https://code.visualstudio.com/docs/copilot/copilot-smart-actions) - [Best Practices](https://code.visualstudio.com/docs/copilot/best-practices) - [Security](https://code.visualstudio.com/docs/copilot/security) - [Troubleshooting](https://code.visualstudio.com/docs/copilot/troubleshooting) - [FAQ](https://code.visualstudio.com/docs/copilot/faq) - [Reference](https://code.visualstudio.com/docs/terminal/basics#copilot-reference-articles) - [Cheat Sheet](https://code.visualstudio.com/docs/copilot/reference/copilot-vscode-features) - [Settings Reference](https://code.visualstudio.com/docs/copilot/reference/copilot-settings) - [MCP Configuration](https://code.visualstudio.com/docs/copilot/reference/mcp-configuration) - [Workspace Context](https://code.visualstudio.com/docs/copilot/reference/workspace-context) - [Configure](https://code.visualstudio.com/docs/terminal/basics#configure-articles) - [Display Language](https://code.visualstudio.com/docs/configure/locales) - [Layout](https://code.visualstudio.com/docs/configure/custom-layout) - [Keyboard Shortcuts](https://code.visualstudio.com/docs/configure/keybindings) - [Settings](https://code.visualstudio.com/docs/configure/settings) - [Settings Sync](https://code.visualstudio.com/docs/configure/settings-sync) - [Extensions](https://code.visualstudio.com/docs/terminal/basics#configure-extensions-articles) - [Extension Marketplace](https://code.visualstudio.com/docs/configure/extensions/extension-marketplace) - [Extension Runtime Security](https://code.visualstudio.com/docs/configure/extensions/extension-runtime-security) - [Themes](https://code.visualstudio.com/docs/configure/themes) - [Profiles](https://code.visualstudio.com/docs/configure/profiles) - [Accessibility](https://code.visualstudio.com/docs/terminal/basics#configure-accessibility-articles) - [Overview](https://code.visualstudio.com/docs/configure/accessibility/accessibility) - [Voice Interactions](https://code.visualstudio.com/docs/configure/accessibility/voice) - [Command Line Interface](https://code.visualstudio.com/docs/configure/command-line) - [Telemetry](https://code.visualstudio.com/docs/configure/telemetry) - [Edit Code](https://code.visualstudio.com/docs/terminal/basics#editing-articles) - [Basic Editing](https://code.visualstudio.com/docs/editing/codebasics) - [IntelliSense](https://code.visualstudio.com/docs/editing/intellisense) - [Code Navigation](https://code.visualstudio.com/docs/editing/editingevolved) - [Refactoring](https://code.visualstudio.com/docs/editing/refactoring) - [Snippets](https://code.visualstudio.com/docs/editing/userdefinedsnippets) - [Workspaces](https://code.visualstudio.com/docs/terminal/basics#editing-workspaces-articles) - [Overview](https://code.visualstudio.com/docs/editing/workspaces/workspaces) - [Multi-Root Workspaces](https://code.visualstudio.com/docs/editing/workspaces/multi-root-workspaces) - [Workspace Trust](https://code.visualstudio.com/docs/editing/workspaces/workspace-trust) - [Build, Debug, Test](https://code.visualstudio.com/docs/terminal/basics#debugtest-articles) - [Tasks](https://code.visualstudio.com/docs/debugtest/tasks) - [Debugging](https://code.visualstudio.com/docs/debugtest/debugging) - [Debug Configuration](https://code.visualstudio.com/docs/debugtest/debugging-configuration) - [Testing](https://code.visualstudio.com/docs/debugtest/testing) - [Port Forwarding](https://code.visualstudio.com/docs/debugtest/port-forwarding) - [Integrated Browser](https://code.visualstudio.com/docs/debugtest/integrated-browser) - [Source Control](https://code.visualstudio.com/docs/terminal/basics#sourcecontrol-articles) - [Overview](https://code.visualstudio.com/docs/sourcecontrol/overview) - [Quickstart](https://code.visualstudio.com/docs/sourcecontrol/quickstart) - [Staging & Committing](https://code.visualstudio.com/docs/sourcecontrol/staging-commits) - [Branches & Worktrees](https://code.visualstudio.com/docs/sourcecontrol/branches-worktrees) - [Repositories & Remotes](https://code.visualstudio.com/docs/sourcecontrol/repos-remotes) - [Merge Conflicts](https://code.visualstudio.com/docs/sourcecontrol/merge-conflicts) - [Collaborate on GitHub](https://code.visualstudio.com/docs/sourcecontrol/github) - [Troubleshooting](https://code.visualstudio.com/docs/sourcecontrol/troubleshooting) - [FAQ](https://code.visualstudio.com/docs/sourcecontrol/faq) - [Terminal](https://code.visualstudio.com/docs/terminal/basics#terminal-articles) - [Getting Started Tutorial](https://code.visualstudio.com/docs/terminal/getting-started) - [Terminal Basics](https://code.visualstudio.com/docs/terminal/basics) - [Terminal Profiles](https://code.visualstudio.com/docs/terminal/profiles) - [Shell Integration](https://code.visualstudio.com/docs/terminal/shell-integration) - [Appearance](https://code.visualstudio.com/docs/terminal/appearance) - [Advanced](https://code.visualstudio.com/docs/terminal/advanced) - [Enterprise](https://code.visualstudio.com/docs/terminal/basics#enterprise-articles) - [Overview](https://code.visualstudio.com/docs/enterprise/overview) - [Enterprise Policies](https://code.visualstudio.com/docs/enterprise/policies) - [AI Settings](https://code.visualstudio.com/docs/enterprise/ai-settings) - [Extensions](https://code.visualstudio.com/docs/enterprise/extensions) - [Telemetry](https://code.visualstudio.com/docs/enterprise/telemetry) - [Updates](https://code.visualstudio.com/docs/enterprise/updates) - [Languages](https://code.visualstudio.com/docs/terminal/basics#languages-articles) - [Overview](https://code.visualstudio.com/docs/languages/overview) - [JavaScript](https://code.visualstudio.com/docs/languages/javascript) - [JSON](https://code.visualstudio.com/docs/languages/json) - [HTML](https://code.visualstudio.com/docs/languages/html) - [Emmet](https://code.visualstudio.com/docs/languages/emmet) - [CSS, SCSS and Less](https://code.visualstudio.com/docs/languages/css) - [TypeScript](https://code.visualstudio.com/docs/languages/typescript) - [Markdown](https://code.visualstudio.com/docs/languages/markdown) - [PowerShell](https://code.visualstudio.com/docs/languages/powershell) - [C++](https://code.visualstudio.com/docs/languages/cpp) - [Java](https://code.visualstudio.com/docs/languages/java) - [PHP](https://code.visualstudio.com/docs/languages/php) - [Python](https://code.visualstudio.com/docs/languages/python) - [Julia](https://code.visualstudio.com/docs/languages/julia) - [R](https://code.visualstudio.com/docs/languages/r) - [Ruby](https://code.visualstudio.com/docs/languages/ruby) - [Rust](https://code.visualstudio.com/docs/languages/rust) - [Go](https://code.visualstudio.com/docs/languages/go) - [T-SQL](https://code.visualstudio.com/docs/languages/tsql) - [C\#](https://code.visualstudio.com/docs/languages/csharp) - [.NET](https://code.visualstudio.com/docs/languages/dotnet) - [Swift](https://code.visualstudio.com/docs/languages/swift) - [Node.js / JavaScript](https://code.visualstudio.com/docs/terminal/basics#nodejs-articles) - [Working with JavaScript](https://code.visualstudio.com/docs/nodejs/working-with-javascript) - [Node.js Tutorial](https://code.visualstudio.com/docs/nodejs/nodejs-tutorial) - [Node.js Debugging](https://code.visualstudio.com/docs/nodejs/nodejs-debugging) - [Deploy Node.js Apps](https://code.visualstudio.com/docs/nodejs/nodejs-deployment) - [Browser Debugging](https://code.visualstudio.com/docs/nodejs/browser-debugging) - [Angular Tutorial](https://code.visualstudio.com/docs/nodejs/angular-tutorial) - [React Tutorial](https://code.visualstudio.com/docs/nodejs/reactjs-tutorial) - [Vue Tutorial](https://code.visualstudio.com/docs/nodejs/vuejs-tutorial) - [Debugging Recipes](https://code.visualstudio.com/docs/nodejs/debugging-recipes) - [Performance Profiling](https://code.visualstudio.com/docs/nodejs/profiling) - [Extensions](https://code.visualstudio.com/docs/nodejs/extensions) - [TypeScript](https://code.visualstudio.com/docs/terminal/basics#typescript-articles) - [Tutorial](https://code.visualstudio.com/docs/typescript/typescript-tutorial) - [Transpiling](https://code.visualstudio.com/docs/typescript/typescript-transpiling) - [Editing](https://code.visualstudio.com/docs/typescript/typescript-editing) - [Refactoring](https://code.visualstudio.com/docs/typescript/typescript-refactoring) - [Debugging](https://code.visualstudio.com/docs/typescript/typescript-debugging) - [Python](https://code.visualstudio.com/docs/terminal/basics#python-articles) - [Quick Start](https://code.visualstudio.com/docs/python/python-quick-start) - [Tutorial](https://code.visualstudio.com/docs/python/python-tutorial) - [Run Python Code](https://code.visualstudio.com/docs/python/run) - [Editing](https://code.visualstudio.com/docs/python/editing) - [Linting](https://code.visualstudio.com/docs/python/linting) - [Formatting](https://code.visualstudio.com/docs/python/formatting) - [Debugging](https://code.visualstudio.com/docs/python/debugging) - [Environments](https://code.visualstudio.com/docs/python/environments) - [Testing](https://code.visualstudio.com/docs/python/testing) - [Python Interactive](https://code.visualstudio.com/docs/python/jupyter-support-py) - [Django Tutorial](https://code.visualstudio.com/docs/python/tutorial-django) - [FastAPI Tutorial](https://code.visualstudio.com/docs/python/tutorial-fastapi) - [Flask Tutorial](https://code.visualstudio.com/docs/python/tutorial-flask) - [Create Containers](https://code.visualstudio.com/docs/python/tutorial-create-containers) - [Deploy Python Apps](https://code.visualstudio.com/docs/python/python-on-azure) - [Python in the Web](https://code.visualstudio.com/docs/python/python-web) - [Settings Reference](https://code.visualstudio.com/docs/python/settings-reference) - [Java](https://code.visualstudio.com/docs/terminal/basics#java-articles) - [Getting Started](https://code.visualstudio.com/docs/java/java-tutorial) - [Navigate and Edit](https://code.visualstudio.com/docs/java/java-editing) - [Refactoring](https://code.visualstudio.com/docs/java/java-refactoring) - [Formatting and Linting](https://code.visualstudio.com/docs/java/java-linting) - [Project Management](https://code.visualstudio.com/docs/java/java-project) - [Build Tools](https://code.visualstudio.com/docs/java/java-build) - [Run and Debug](https://code.visualstudio.com/docs/java/java-debugging) - [Testing](https://code.visualstudio.com/docs/java/java-testing) - [Spring Boot](https://code.visualstudio.com/docs/java/java-spring-boot) - [Modernizing Java Apps](https://code.visualstudio.com/docs/java/java-app-mod) - [Application Servers](https://code.visualstudio.com/docs/java/java-tomcat-jetty) - [Deploy Java Apps](https://code.visualstudio.com/docs/java/java-on-azure) - [GUI Applications](https://code.visualstudio.com/docs/java/java-gui) - [Extensions](https://code.visualstudio.com/docs/java/extensions) - [FAQ](https://code.visualstudio.com/docs/java/java-faq) - [C++](https://code.visualstudio.com/docs/terminal/basics#cpp-articles) - [Intro Videos](https://code.visualstudio.com/docs/cpp/introvideos-cpp) - [GCC on Linux](https://code.visualstudio.com/docs/cpp/config-linux) - [GCC on Windows](https://code.visualstudio.com/docs/cpp/config-mingw) - [GCC on Windows Subsystem for Linux](https://code.visualstudio.com/docs/cpp/config-wsl) - [Clang on macOS](https://code.visualstudio.com/docs/cpp/config-clang-mac) - [Microsoft C++ on Windows](https://code.visualstudio.com/docs/cpp/config-msvc) - [Build with CMake](https://code.visualstudio.com/docs/cpp/build-with-cmake) - [CMake Tools on Linux](https://code.visualstudio.com/docs/cpp/cmake-linux) - [CMake Quick Start](https://code.visualstudio.com/docs/cpp/cmake-quickstart) - [C++ Dev Tools for Copilot](https://code.visualstudio.com/docs/cpp/cpp-devtools) - [Editing and Navigating](https://code.visualstudio.com/docs/cpp/cpp-ide) - [Debugging](https://code.visualstudio.com/docs/cpp/cpp-debug) - [Configure Debugging](https://code.visualstudio.com/docs/cpp/launch-json-reference) - [Refactoring](https://code.visualstudio.com/docs/cpp/cpp-refactoring) - [Settings Reference](https://code.visualstudio.com/docs/cpp/customize-cpp-settings) - [Configure IntelliSense](https://code.visualstudio.com/docs/cpp/configure-intellisense) - [Configure IntelliSense for Cross-Compiling](https://code.visualstudio.com/docs/cpp/configure-intellisense-crosscompilation) - [FAQ](https://code.visualstudio.com/docs/cpp/faq-cpp) - [C\#](https://code.visualstudio.com/docs/terminal/basics#csharp-articles) - [Intro Videos](https://code.visualstudio.com/docs/csharp/introvideos-csharp) - [Get Started](https://code.visualstudio.com/docs/csharp/get-started) - [Navigate and Edit](https://code.visualstudio.com/docs/csharp/navigate-edit) - [IntelliCode](https://code.visualstudio.com/docs/csharp/intellicode) - [Refactoring](https://code.visualstudio.com/docs/csharp/refactoring) - [Formatting and Linting](https://code.visualstudio.com/docs/csharp/formatting-linting) - [Project Management](https://code.visualstudio.com/docs/csharp/project-management) - [Build Tools](https://code.visualstudio.com/docs/csharp/build-tools) - [Package Management](https://code.visualstudio.com/docs/csharp/package-management) - [Run and Debug](https://code.visualstudio.com/docs/csharp/debugging) - [Testing](https://code.visualstudio.com/docs/csharp/testing) - [FAQ](https://code.visualstudio.com/docs/csharp/cs-dev-kit-faq) - [Container Tools](https://code.visualstudio.com/docs/terminal/basics#containers-articles) - [Overview](https://code.visualstudio.com/docs/containers/overview) - [Node.js](https://code.visualstudio.com/docs/containers/quickstart-node) - [Python](https://code.visualstudio.com/docs/containers/quickstart-python) - [ASP.NET Core](https://code.visualstudio.com/docs/containers/quickstart-aspnet-core) - [Debug](https://code.visualstudio.com/docs/containers/debug-common) - [Docker Compose](https://code.visualstudio.com/docs/containers/docker-compose) - [Registries](https://code.visualstudio.com/docs/containers/quickstart-container-registries) - [Deploy to Azure](https://code.visualstudio.com/docs/containers/app-service) - [Choose a Dev Environment](https://code.visualstudio.com/docs/containers/choosing-dev-environment) - [Customize](https://code.visualstudio.com/docs/containers/reference) - [Develop with Kubernetes](https://code.visualstudio.com/docs/containers/bridge-to-kubernetes) - [Tips and Tricks](https://code.visualstudio.com/docs/containers/troubleshooting) - [Data Science](https://code.visualstudio.com/docs/terminal/basics#datascience-articles) - [Overview](https://code.visualstudio.com/docs/datascience/overview) - [Jupyter Notebooks](https://code.visualstudio.com/docs/datascience/jupyter-notebooks) - [Data Science Tutorial](https://code.visualstudio.com/docs/datascience/data-science-tutorial) - [Python Interactive](https://code.visualstudio.com/docs/datascience/python-interactive) - [Data Wrangler Quick Start](https://code.visualstudio.com/docs/datascience/data-wrangler-quick-start) - [Data Wrangler](https://code.visualstudio.com/docs/datascience/data-wrangler) - [PyTorch Support](https://code.visualstudio.com/docs/datascience/pytorch-support) - [Azure Machine Learning](https://code.visualstudio.com/docs/datascience/azure-machine-learning) - [Manage Jupyter Kernels](https://code.visualstudio.com/docs/datascience/jupyter-kernel-management) - [Jupyter Notebooks on the Web](https://code.visualstudio.com/docs/datascience/notebooks-web) - [Data Science in Microsoft Fabric](https://code.visualstudio.com/docs/datascience/microsoft-fabric-quickstart) - [Intelligent Apps](https://code.visualstudio.com/docs/terminal/basics#intelligentapps-articles) - [AI Toolkit Overview](https://code.visualstudio.com/docs/intelligentapps/overview) - [AI Toolkit Copilot Tools](https://code.visualstudio.com/docs/intelligentapps/copilot-tools) - [Models](https://code.visualstudio.com/docs/intelligentapps/models) - [Playground](https://code.visualstudio.com/docs/intelligentapps/playground) - [Agent Builder](https://code.visualstudio.com/docs/intelligentapps/agentbuilder) - [Agent Inspector](https://code.visualstudio.com/docs/intelligentapps/agent-inspector) - [Migrating from Visualizer to Agent Inspector](https://code.visualstudio.com/docs/intelligentapps/migrate-from-visualizer) - [Bulk Run](https://code.visualstudio.com/docs/intelligentapps/bulkrun) - [Evaluation](https://code.visualstudio.com/docs/intelligentapps/evaluation) - [Fine-Tuning (Automated Setup)](https://code.visualstudio.com/docs/intelligentapps/finetune) - [Fine-Tuning (Project Template)](https://code.visualstudio.com/docs/intelligentapps/finetune-legacy) - [Model Conversion](https://code.visualstudio.com/docs/intelligentapps/modelconversion) - [Tracing](https://code.visualstudio.com/docs/intelligentapps/tracing) - [Profiling (Windows ML)](https://code.visualstudio.com/docs/intelligentapps/profiling) - [FAQ](https://code.visualstudio.com/docs/intelligentapps/faq) - [Reference](https://code.visualstudio.com/docs/terminal/basics#intelligentapps-reference-articles) - [File Structure](https://code.visualstudio.com/docs/intelligentapps/reference/FileStructure) - [Manual Model Conversion](https://code.visualstudio.com/docs/intelligentapps/reference/ManualModelConversion) - [Manual Model Conversion on GPU](https://code.visualstudio.com/docs/intelligentapps/reference/ManualConversionOnGPU) - [Setup Environment Without AI Toolkit](https://code.visualstudio.com/docs/intelligentapps/reference/SetupWithoutAITK) - [Template Project](https://code.visualstudio.com/docs/intelligentapps/reference/TemplateProject) - [Azure](https://code.visualstudio.com/docs/terminal/basics#azure-articles) - [Overview](https://code.visualstudio.com/docs/azure/overview) - [Getting Started](https://code.visualstudio.com/docs/azure/gettingstarted) - [Resources View](https://code.visualstudio.com/docs/azure/resourcesextension) - [Deployment](https://code.visualstudio.com/docs/azure/deployment) - [VS Code for the Web - Azure](https://code.visualstudio.com/docs/azure/vscodeforweb) - [Containers](https://code.visualstudio.com/docs/azure/containers) - [Azure Kubernetes Service](https://code.visualstudio.com/docs/azure/aksextensions) - [Kubernetes](https://code.visualstudio.com/docs/azure/kubernetes) - [MongoDB](https://code.visualstudio.com/docs/azure/mongodb) - [Remote Debugging for Node.js](https://code.visualstudio.com/docs/azure/remote-debugging) - [Remote](https://code.visualstudio.com/docs/terminal/basics#remote-articles) - [Overview](https://code.visualstudio.com/docs/remote/remote-overview) - [SSH](https://code.visualstudio.com/docs/remote/ssh) - [Dev Containers](https://code.visualstudio.com/docs/remote/dev-containers) - [Windows Subsystem for Linux](https://code.visualstudio.com/docs/remote/wsl) - [GitHub Codespaces](https://code.visualstudio.com/docs/remote/codespaces) - [VS Code Server](https://code.visualstudio.com/docs/remote/vscode-server) - [Tunnels](https://code.visualstudio.com/docs/remote/tunnels) - [SSH Tutorial](https://code.visualstudio.com/docs/remote/ssh-tutorial) - [WSL Tutorial](https://code.visualstudio.com/docs/remote/wsl-tutorial) - [Tips and Tricks](https://code.visualstudio.com/docs/remote/troubleshooting) - [FAQ](https://code.visualstudio.com/docs/remote/faq) - [Dev Containers](https://code.visualstudio.com/docs/terminal/basics#devcontainers-articles) - [Overview](https://code.visualstudio.com/docs/devcontainers/containers) - [Tutorial](https://code.visualstudio.com/docs/devcontainers/tutorial) - [Attach to Container](https://code.visualstudio.com/docs/devcontainers/attach-container) - [Create Dev Container](https://code.visualstudio.com/docs/devcontainers/create-dev-container) - [Advanced Containers](https://code.visualstudio.com/docs/devcontainers/containers-advanced) - [devcontainer.json](https://code.visualstudio.com/docs/devcontainers/devcontainerjson-reference) - [Dev Container CLI](https://code.visualstudio.com/docs/devcontainers/devcontainer-cli) - [Tips and Tricks](https://code.visualstudio.com/docs/devcontainers/tips-and-tricks) - [FAQ](https://code.visualstudio.com/docs/devcontainers/faq) - [Reference](https://code.visualstudio.com/docs/terminal/basics#reference-articles) - [Default Keyboard Shortcuts](https://code.visualstudio.com/docs/reference/default-keybindings) - [Default Settings](https://code.visualstudio.com/docs/reference/default-settings) - [Substitution Variables](https://code.visualstudio.com/docs/reference/variables-reference) - [Tasks Schema](https://code.visualstudio.com/docs/reference/tasks-appendix) Topics Copy as Markdown - Copy as Markdown - View as Markdown #### On this page there are 19 sectionsOn this page - [Terminal shells](https://code.visualstudio.com/docs/terminal/basics#_terminal-shells) - [Managing terminals](https://code.visualstudio.com/docs/terminal/basics#_managing-terminals) - [Terminals in editor area](https://code.visualstudio.com/docs/terminal/basics#_terminals-in-editor-area) - [Terminals in new windows](https://code.visualstudio.com/docs/terminal/basics#_terminals-in-new-windows) - [Navigating the buffer](https://code.visualstudio.com/docs/terminal/basics#_navigating-the-buffer) - [Links](https://code.visualstudio.com/docs/terminal/basics#_links) - [Copy & paste](https://code.visualstudio.com/docs/terminal/basics#_copy-paste) - [Using the mouse](https://code.visualstudio.com/docs/terminal/basics#_using-the-mouse) - [Find](https://code.visualstudio.com/docs/terminal/basics#_find) - [Run selected text](https://code.visualstudio.com/docs/terminal/basics#_run-selected-text) - [Maximizing the terminal](https://code.visualstudio.com/docs/terminal/basics#_maximizing-the-terminal) - [Select all](https://code.visualstudio.com/docs/terminal/basics#_select-all) - [Drag and drop file paths](https://code.visualstudio.com/docs/terminal/basics#_drag-and-drop-file-paths) - [Automating terminals with tasks](https://code.visualstudio.com/docs/terminal/basics#_automating-terminals-with-tasks) - [Working directory](https://code.visualstudio.com/docs/terminal/basics#_working-directory) - [Fixed dimension terminals](https://code.visualstudio.com/docs/terminal/basics#_fixed-dimension-terminals) - [GitHub Copilot in the terminal](https://code.visualstudio.com/docs/terminal/basics#_github-copilot-in-the-terminal) - [Next steps](https://code.visualstudio.com/docs/terminal/basics#_next-steps) - [Common questions](https://code.visualstudio.com/docs/terminal/basics#_common-questions) # Terminal Basics Visual Studio Code includes a full featured integrated terminal that starts at the root of your workspace. It provides integration with the editor to support features like [links](https://code.visualstudio.com/docs/terminal/basics#_links) and [error detection](https://code.visualstudio.com/docs/debugtest/tasks). The integrated terminal can run commands such as mkdir and git just like a standalone terminal. You can open a terminal as follows: - From the menu, use the Terminal \> New Terminal or View \> Terminal menu commands. - From the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)), use the View: Toggle Terminal command. - In the Explorer, you can use the Open in Integrated Terminal context menu command to open a new terminal from a folder. - To toggle the terminal panel, use the ⌃\` (Windows, Linux Ctrl+\`) keyboard shortcut. - To create a new terminal, use the ⌃⇧\` (Windows, Linux Ctrl+Shift+\`) keyboard shortcut. VS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar: ![The integrated terminal can run commands such as mkdir and git just like a standalone terminal. VS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar.](https://code.visualstudio.com/assets/docs/terminal/basics/integrated-terminal.png) Note If you prefer to work outside VS Code, open an external terminal with the ⇧⌘C (Windows, Linux Ctrl+Shift+C) keyboard shortcut ## [Terminal shells](https://code.visualstudio.com/docs/terminal/basics#_terminal-shells) The integrated terminal can use various shells installed on your machine, with the default being pulled from your system defaults. Shells are detected and presented in the terminal profiles dropdown. ![A detected profile can be chosen in the dropdown next to the new terminal button. Some examples on Windows include PowerShell, Command Prompt, Git Bash and WSL](https://code.visualstudio.com/assets/docs/terminal/basics/select-profile-dropdown.png) You can learn more about configuring terminal shells in the [terminal profiles](https://code.visualstudio.com/docs/terminal/profiles) article. ## [Managing terminals](https://code.visualstudio.com/docs/terminal/basics#_managing-terminals) The terminal tabs UI is on the right side of the terminal view. Each terminal has an entry with its name, icon, color, and group decoration (if any). ![Activating the Launch Profile button will show all detected and manually configured profiles](https://code.visualstudio.com/assets/docs/terminal/basics/tabs.png) Add terminal instances by selecting the \+ icon on the top-right of the TERMINAL panel, selecting a profile from the terminal dropdown, or by triggering the ⌃⇧\` (Windows, Linux Ctrl+Shift+\`) command. This action creates another entry in the tab list associated with that terminal. Remove terminal instances by hovering a tab and selecting the Trash Can button, selecting a tab item and pressing Delete, using Terminal: Kill the Active Terminal Instance command, or via the right-click context menu. Navigate between terminal groups using focus next ⇧⌘\] (Windows, Linux Ctrl+PageDown) and focus previous ⇧⌘\[ (Windows, Linux Ctrl+PageUp). Icons may appear to the right of the terminal title on the tab label when a terminal's status changes. Some examples are a bell (macOS) and for tasks, displaying a check mark when there are no errors and an X otherwise. Hover the icon to read status information, which may contain actions. ### [Groups (split panes)](https://code.visualstudio.com/docs/terminal/basics#_groups-split-panes) Place multiple terminals side-by-side and create a group by splitting a terminal: - Hover over an entry in the list of terminals on the right and select the inline split button. - Right-click the context menu and select the Split menu option. - Alt and click on a tab, the \+ button, or the single tab on the terminal panel. - Trigger the ⌘\\ (Windows, Linux Ctrl+Shift+5) command. Tip The working directory for the new terminal depends on the terminal.integrated.splitCwd Open in VS Code Open in VS Code Insiders [setting](https://code.visualstudio.com/docs/configure/settings). Navigate between terminals in a group by focusing the previous pane, ⌥⌘← (Windows, Linux Alt+Left), or the next pane, ⌥⌘→ (Windows, Linux Alt+Right). Dragging and dropping tabs in the list rearranges them. Dragging a tab into the main terminal area allows moving a terminal from one group to another. Moving a terminal into its own group can be done with the Terminal: Unsplit Terminal command through the Command Palette or in the right-click context menu. ## [Terminals in editor area](https://code.visualstudio.com/docs/terminal/basics#_terminals-in-editor-area) You can open terminals in the editor area (terminal editors) with the Terminal: Create New Terminal in Editor Area command, the Terminal: Create New Terminal in Editor Area to the Side command, or by dragging a terminal from the terminal view into the editor area. Terminal editors are presented like regular editor tabs: ![Terminal editors are presented like regular text file tabs](https://code.visualstudio.com/assets/docs/terminal/basics/terminal-editor.png) You can have terminal editors on either side or arranged in multiple dimensions using the editor group layout system, e.g. PowerShell and WSL terminals stacked to the right of file editors: ![Terminal editors are can be laid out using the editor group layout system, for example 2 terminals could sit to the right of a text editor](https://code.visualstudio.com/assets/docs/terminal/basics/terminal-editor-grid.png) The terminal.integrated.defaultLocation Open in VS Code Open in VS Code Insiders setting can change the default `view` or `editor` area terminal location. ## [Terminals in new windows](https://code.visualstudio.com/docs/terminal/basics#_terminals-in-new-windows) Opening a terminal in a new VS Code window is possible in a few different ways: - Use ⌃⇧⌥\` (Windows, Linux Ctrl+Shift+Alt+\`) - Right-click the terminal tab if you have multiple terminals, or left-click the tab if you only have a single terminal opened. Then select Move Terminal to New Window - Select the New Terminal Window entry that's available in several different menus ## [Navigating the buffer](https://code.visualstudio.com/docs/terminal/basics#_navigating-the-buffer) The content in the terminal is called the buffer, with the section right above the bottom viewport being called "scrollback". The amount of scrollback kept is determined by the terminal.integrated.scrollback Open in VS Code Open in VS Code Insiders [setting](https://code.visualstudio.com/docs/configure/settings) and defaults to `1000` lines. There are various commands available to navigate around the terminal buffer: - Scroll up a line - ⌥⌘PageUp (Windows Ctrl+Alt+PageUp, Linux Ctrl+Shift+Up) - Scroll down a line - ⌥⌘PageDown (Windows Ctrl+Alt+PageDown, Linux Ctrl+Shift+Down) - Scroll up a page - PageUp (Windows, Linux Shift+PageUp) - Scroll down a page - PageDown (Windows, Linux Shift+PageDown) - Scroll to the top - ⌘Home (Windows Ctrl+Home, Linux Shift+Home) - Scroll to the bottom - ⌘End (Windows Ctrl+End, Linux Shift+End) Command navigation is also available (see [shell integration](https://code.visualstudio.com/docs/terminal/shell-integration)): - Scroll to the previous command - ⌘↑ (Windows, Linux Ctrl+Up) - Scroll to the next command - ⌘↓ (Windows, Linux Ctrl+Down) Scrolling will happen instantaneously, but can be configured to animate over a short duration with the terminal.integrated.smoothScrolling Open in VS Code Open in VS Code Insiders setting. ## [Links](https://code.visualstudio.com/docs/terminal/basics#_links) The terminal features sophisticated link detection with editor integration and even extension contributed link handlers. Hover over a link to display an underline, then hold the Ctrl/Cmd key and click. These built-in link handlers are used in the following priority order: - URIs/URLs: Links that look like URIs, such as `https://code.visualstudio.com`, `vscode://path/to/file` or `file://path/to/file` will open using the standard handler for the protocol. For example, `https` links will open the browser. ![Opening a URI link will open it in the system browser](https://code.visualstudio.com/assets/docs/terminal/basics/link-uri.png) - File links: Links to files that have been verified to exist on the system. These will open the file in a new editor tab and support many common line/column formats such as `file:1:2`, `file:line 1, column 2`. ![Activating a file link will open it in an editor](https://code.visualstudio.com/assets/docs/terminal/basics/link-file.png) - Folder links: Links to folders are similar to file links but will open a new VS Code window at the folder. ![Activating a folder link will open it in a new window](https://code.visualstudio.com/assets/docs/terminal/basics/link-folder.png) - Word links: Fallback link type that uses the terminal.integrated.wordSeparators Open in VS Code Open in VS Code Insiders setting. The setting defines word boundaries and make nearly all text into words. Activating a word link searches the workspace for the word. If there is a single result it will open, otherwise it will present the search results. Word links are considered "low confidence" and will not show an underline or tooltip unless you hold the Ctrl/Cmd key. They also have limited support for line and column suffixes. ![Activating a word link 'terminal:15' will open a Quick Pick searching the workspace for all files containing 'terminal', choosing an option will open the file at line 15](https://code.visualstudio.com/assets/docs/terminal/basics/link-word.png) The Open Detected Link command (⇧⌘G (Windows, Linux Ctrl+Shift+G)) can be used to access links via the keyboard: ![Open Detected Link opens a quick pick with all links in the viewport, split into categories](https://code.visualstudio.com/assets/docs/terminal/basics/link-open-detected.png) Tip If link verification causes performance issues, like in high latency remote environments, disable it via the terminal.integrated.enableFileLinks Open in VS Code Open in VS Code Insiders [setting](https://code.visualstudio.com/docs/configure/settings). ### [Extensions handling links](https://code.visualstudio.com/docs/terminal/basics#_extensions-handling-links) Extensions can contribute link providers which allow the extension to define what happens when clicked. An example of this is the [GitLens](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens) extension detecting Git branch links. ![When GitLens is installed, hovering a branch name will provide custom behavior to open the branch in the UI](https://code.visualstudio.com/assets/docs/terminal/basics/link-extension.png) ### [Keyboard accessibility](https://code.visualstudio.com/docs/terminal/basics#_keyboard-accessibility) Links are keyboard accessible through several commands that open links based on the type of link. - Terminal: Open Last Local File Link - Opens the most recent local file link. No default keyboard shortcut. - Terminal: Open Last URL link - Opens the most recent URI/URL link. No default keyboard shortcut. - Terminal: Open Detected Link... - Opens a searchable Quick Pick with all detected links, including word links. The default keyboard shortcut is Ctrl/Cmd+Shift+O, which is the same as the Go to Symbol in Editor keyboard shortcut. ## [Copy & paste](https://code.visualstudio.com/docs/terminal/basics#_copy-paste) The keyboard shortcuts for copy and paste follow platform standards: - Linux: Ctrl+Shift+C and Ctrl+Shift+V; selection paste is available with Shift+Insert - macOS: Cmd+C and Cmd+V - Windows: Ctrl+C and Ctrl+V Copying is done automatically on selection when terminal.integrated.copyOnSelection Open in VS Code Open in VS Code Insiders is enabled. By default, there is a warning when pasting multiple lines, which can be disabled with the terminal.integrated.enableMultiLinePasteWarning Open in VS Code Open in VS Code Insiders setting. This is only done when the shell does not support "bracketed paste mode". When that mode is enabled, the shell is indicating that it can handle multiple line pasting. ## [Using the mouse](https://code.visualstudio.com/docs/terminal/basics#_using-the-mouse) ### [Right-click behavior](https://code.visualstudio.com/docs/terminal/basics#_rightclick-behavior) The right-click behavior differs based on the platform: - Linux: Show the context menu. - macOS: Select the word under the cursor and show the context menu. - Windows: Copy and drop selection if there is a selection, otherwise paste. This can be configured using the terminal.integrated.rightClickBehavior Open in VS Code Open in VS Code Insiders setting. The options are: - `default` - Show the context menu. - `copyPaste` - Copy when there is a selection, otherwise paste. - `paste` - Paste on right-click. - `selectWord` - Select the word under the cursor and show the context menu. - `nothing` - Do nothing and pass event to terminal. ### [Column selection](https://code.visualstudio.com/docs/terminal/basics#_column-selection) Press Alt and left-click drag to select a rectangle of text inside the terminal instead of the regular selection of a line. ### [Reposition the cursor with Alt](https://code.visualstudio.com/docs/terminal/basics#_reposition-the-cursor-with-alt) Alt and left-click will reposition the cursor to underneath the mouse. This works by simulating arrow keystrokes, which may not work reliably for some shells or programs. This feature can be disabled with the terminal.integrated.altClickMovesCursor Open in VS Code Open in VS Code Insiders setting. ### [Mouse events mode](https://code.visualstudio.com/docs/terminal/basics#_mouse-events-mode) When applications running in the terminal turn on mouse events mode, such as Vim mouse mode, mouse interaction is sent to the application instead of the terminal. This means that clicking and dragging will no longer create a selection. Terminal selection can be forced by holding the Alt key on Windows and Linux, this can also be done with the Option key on macOS but requires enabling the terminal.integrated.macOptionClickForcesSelection Open in VS Code Open in VS Code Insiders setting first. ## [Find](https://code.visualstudio.com/docs/terminal/basics#_find) The integrated terminal has find functionality that can be triggered with ⌘F (Windows, Linux Ctrl+F). ![Find in the terminal will highlight all text matching the query](https://code.visualstudio.com/assets/docs/terminal/basics/terminal-find.png) Tip Ctrl+F can be sent to the shell by removing the `workbench.action.terminal.focusFind` command from [commands to skip shell](https://code.visualstudio.com/docs/terminal/advanced#_keyboard-shortcuts-and-the-shell). ## [Run selected text](https://code.visualstudio.com/docs/terminal/basics#_run-selected-text) To use the `runSelectedText` command, select text in an editor and run the command Terminal: Run Selected Text in Active Terminal via the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)), the terminal will attempt to run the selected text. If no text is selected in the active editor, the entire line that the cursor is on will run in the terminal. Tip Also run the active file using the command `workbench.action.terminal.runActiveFile`. ## [Maximizing the terminal](https://code.visualstudio.com/docs/terminal/basics#_maximizing-the-terminal) The terminal view can be maximized by clicking the maximize panel size button with the upwards chevron icon. This will temporarily hide the editors and maximize the panel. This is useful to temporarily focus on a large amount of output. Some developers use VS Code as a standalone terminal by opening a new window, maximizing the panel, and hiding the side bar. Note that the panel can only be maximized if its [alignment](https://code.visualstudio.com/docs/configure/custom-layout#_panel-alignment) option is set to Center. ## [Select all](https://code.visualstudio.com/docs/terminal/basics#_select-all) There is a Terminal: Select All command, which is bound to Cmd+A on macOS, but does not have a default keyboard shortcut on Windows and Linux as it may conflict with shell hotkeys. To use Ctrl+A to select all, add this custom keyboard shortcut: JSON ``` { "key": "ctrl+a", "command": "workbench.action.terminal.selectAll", "when": "terminalFocus && !isMac" }, ``` ## [Drag and drop file paths](https://code.visualstudio.com/docs/terminal/basics#_drag-and-drop-file-paths) Dragging a file into the terminal will input the path into the terminal, with escaping to match the active shell. ## [Automating terminals with tasks](https://code.visualstudio.com/docs/terminal/basics#_automating-terminals-with-tasks) The [Tasks](https://code.visualstudio.com/docs/debugtest/tasks) feature can be used to automate the launching of terminals, for example, the following `.vscode/tasks.json` file will launch a Command Prompt and PowerShell terminal in a single terminal group when the window starts: Jsonc ``` { "version": "2.0.0", "presentation": { "echo": false, "reveal": "always", "focus": false, "panel": "dedicated", "showReuseMessage": true }, "tasks": [ { "label": "Create terminals", "dependsOn": [ "First", "Second" ], // Mark as the default build task so cmd/ctrl+shift+b will create them "group": { "kind": "build", "isDefault": true }, // Try start the task on folder open "runOptions": { "runOn": "folderOpen" } }, { // The name that shows up in terminal tab "label": "First", // The task will launch a shell "type": "shell", "command": "", // Set the shell type "options": { "shell": { "executable": "cmd.exe", "args": [] } }, // Mark as a background task to avoid the spinner animation on the terminal tab "isBackground": true, "problemMatcher": [], // Create the tasks in a terminal group "presentation": { "group": "my-group" } }, { "label": "Second", "type": "shell", "command": "", "options": { "shell": { "executable": "pwsh.exe", "args": [] } }, "isBackground": true, "problemMatcher": [], "presentation": { "group": "my-group" } } ] } ``` This file could be committed to the repository to share with other developers or created as a user task via the `workbench.action.tasks.openUserTasks` command. ## [Working directory](https://code.visualstudio.com/docs/terminal/basics#_working-directory) By default, the terminal will open at the folder that is opened in the Explorer. The terminal.integrated.cwd Open in VS Code Open in VS Code Insiders setting allows specifying a custom path to open instead: JSON ``` { "terminal.integrated.cwd": "/home/user" } ``` Split terminals on Windows will start in the directory that the parent terminal started with. On macOS and Linux, split terminals will inherit the current working directory of the parent terminal. This behavior can be changed using the terminal.integrated.splitCwd Open in VS Code Open in VS Code Insiders setting: JSON ``` { "terminal.integrated.splitCwd": "workspaceRoot" } ``` There are also extensions available that give more options such as [Terminal Here](https://marketplace.visualstudio.com/items?itemName=Tyriar.vscode-terminal-here). ## [Fixed dimension terminals](https://code.visualstudio.com/docs/terminal/basics#_fixed-dimension-terminals) The Terminal: Set Fixed Dimensions command allows changing the number of columns and rows that the terminal and it's backing pseudoterminal uses. This will add scroll bars when necessary, which may lead to an unpleasant UX and is generally not recommended, but it is a common ask on Windows in particular for reading logs or long lines when paging tools aren't available. You can also right-click on a terminal tab and select Toggle Size to Content Width (⌥Z (Windows, Linux Alt+Z)) to resize the number of terminal columns to the largest wrapped line in the terminal. ## [GitHub Copilot in the terminal](https://code.visualstudio.com/docs/terminal/basics#_github-copilot-in-the-terminal) If you have access to [GitHub Copilot](https://code.visualstudio.com/docs/copilot/setup), you can use it to get AI-powered help with terminal commands and shell scripting. There are several ways to use Copilot with the terminal: ### [Terminal inline chat](https://code.visualstudio.com/docs/terminal/basics#_terminal-inline-chat) Start an inline chat directly in the terminal to get help with shell commands: 1. Open the terminal (⌃\` (Windows, Linux Ctrl+\`)) 2. Press ⌘I (Windows, Linux Ctrl+I) or run the Terminal Inline Chat command from the Command Palette 3. Enter your question or request in natural language, such as: - "How do I find the largest files in this directory?" - "Show me how to undo the last git commit" - "Create a bash script to analyze log files" ![Terminal inline chat helps you quickly get and run shell commands](https://code.visualstudio.com/assets/docs/terminal/basics/terminal-chat-2.png) When Copilot provides a response, you can select Run to execute the command directly or Insert to add it to the terminal for further editing. For more information about using GitHub Copilot with the terminal, see [Use terminal inline chat](https://code.visualstudio.com/docs/copilot/chat/inline-chat#_use-terminal-inline-chat). ### [Terminal chat participant](https://code.visualstudio.com/docs/terminal/basics#_terminal-chat-participant) Use the dedicated `@terminal` chat participant in ask mode in the Chat view: 1. Open the Chat view (⌃⌘I (Windows, Linux Ctrl+Alt+I)) 2. Start your question with `@terminal` to direct it to the terminal participant 3. Ask about terminal commands, shell scripting, or explaining terminal output Examples: - `@terminal list the 5 largest files in this workspace` - `@terminal /explain top shell command` - `@terminal how to grep for patterns recursively` ### [Reference terminal context in chat](https://code.visualstudio.com/docs/terminal/basics#_reference-terminal-context-in-chat) You can include terminal information as context in your chat prompts: - Use `#terminalSelection` to add selected text from the terminal to your chat prompt - Use `#terminalLastCommand` to include the last command you ran in the terminal ## [Next steps](https://code.visualstudio.com/docs/terminal/basics#_next-steps) The basics of the terminal have been covered in this document. Read on to find out more about: - [Terminal inline chat](https://code.visualstudio.com/docs/copilot/chat/inline-chat#_use-terminal-inline-chat) - AI-powered suggestions right in your terminal. - [Tasks](https://code.visualstudio.com/docs/debugtest/tasks) - Tasks let you integrate with external tools and leverage the terminal heavily. - [Mastering VS Code's Terminal](https://www.growingwiththeweb.com/2017/03/mastering-vscodes-terminal.html) - An external blog with plenty of power user tips for the terminal. - Explore terminal commands by browsing the keyboard shortcuts within VS Code (Preferences: Open Keyboard Shortcuts then search on 'terminal'). ## [Common questions](https://code.visualstudio.com/docs/terminal/basics#_common-questions) ### [I'm having problems launching the terminal](https://code.visualstudio.com/docs/terminal/basics#_im-having-problems-launching-the-terminal) There's a [dedicated troubleshooting guide](https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch) for these sorts of problems. ### [How do I create an Admin terminal?](https://code.visualstudio.com/docs/terminal/basics#_how-do-i-create-an-admin-terminal) The integrated terminal shell is running with the permissions of VS Code. If you need to run a shell command with elevated (administrator) or different permissions, use platform utilities such as `runas.exe` within a terminal. You can learn more about customizing terminals via terminal profiles in [Configuring Profiles](https://code.visualstudio.com/docs/terminal/profiles#_configuring-profiles). ### [Can I add a keyboard shortcut for the Explorer's Open in Integrated Terminal command?](https://code.visualstudio.com/docs/terminal/basics#_can-i-add-a-keyboard-shortcut-for-the-explorers-open-in-integrated-terminal-command) You can open new terminals for specific folders from the Explorer via the Open in Integrated Terminal context menu command. ![A folder selected in the Explorer displaying the context menu with the Open in Integrated Terminal command](https://code.visualstudio.com/assets/docs/terminal/basics/open-in-terminal-command.png) By default, there is no keyboard shortcut associated with Open in Integrated Terminal but you can add your own via the Keyboard Shortcuts editor (⌘K ⌘S (Windows, Linux Ctrl+K Ctrl+S)) to add a keyboard shortcut to your `keybindings.json`. The `keybindings.json` example below adds the keyboard shortcut Ctrl+T for `openInTerminal`. JSON ``` { "key": "ctrl+t", "command": "openInTerminal", "when": "filesExplorerFocus" } ``` ### [Why is nvm complaining about a prefix option when the integrated terminal is launched?](https://code.visualstudio.com/docs/terminal/basics#_why-is-nvm-complaining-about-a-prefix-option-when-the-integrated-terminal-is-launched) nvm (Node Version Manager) users often see this error for the first time inside VS Code's integrated terminal: Bash ``` nvm is not compatible with the npm config "prefix" option: currently set to "/usr/local" Run `npm config delete prefix` or `nvm use --delete-prefix v8.9.1 --silent` to unset it ``` This is mostly a macOS problem and does not happen in external terminals. The typical reasons for this are the following: - `npm` was globally installed using another instance of `node` that is somewhere in your path (such as `/usr/local/bin/npm`). - To get the development tools on the `$PATH`, VS Code will launch a bash login shell on startup. This means that your `~/.bash_profile` has already run and when an integrated terminal launches, it will run another login shell, reordering the `$PATH` potentially in unexpected ways. To resolve this issue, you need to track down where the old `npm` is installed and remove both it and its out-of-date node\_modules. Find the `nvm` initialization script and run `which npm` before it runs, which should print the path when you launch a new terminal. Once you have the path to npm, find the old node\_modules by resolving the symlink by running a command something like this: Bash ``` ls -la /usr/local/bin \| grep "np[mx]" ``` This will give you the resolved path at the end: Bash ``` ... npm -> ../lib/node_modules/npm/bin/npm-cli.js ... npx -> ../lib/node_modules/npm/bin/npx-cli.js ``` From there, removing the files and relaunching VS Code should fix the issue: Bash ``` rm /usr/local/bin/npm /usr/local/lib/node_modules/npm/bin/npm-cli.js rm /usr/local/bin/npx /usr/local/lib/node_modules/npm/bin/npx-cli.js ``` ### [Why does macOS make a ding sound when I resize terminal split panes?](https://code.visualstudio.com/docs/terminal/basics#_why-does-macos-make-a-ding-sound-when-i-resize-terminal-split-panes) The keyboard shortcuts ⌃⌘← and ⌃⌘→ are the defaults for resizing individual split panes in the terminal. While they work, they also cause a system "invalid key" sound to play due to an issue in Chromium. The [recommended workaround](https://github.com/microsoft/vscode/issues/44070#issuecomment-799716362) is to tell macOS to no-op for these keyboard shortcuts by running this in your terminal: Bash ``` mkdir -p ~/Library/KeyBindings cat > ~/Library/KeyBindings/DefaultKeyBinding.dict <<EOF { "@^\UF700" = "noop:"; "@^\UF701" = "noop:"; "@^\UF702" = "noop:"; "@^\UF703" = "noop:"; "@~^\UF700" = "noop:"; "@~^\UF701" = "noop:"; "@~^\UF702" = "noop:"; "@~^\UF703" = "noop:"; } EOF ``` ### [I'm having problems with the terminal rendering. What can I do?](https://code.visualstudio.com/docs/terminal/basics#_im-having-problems-with-the-terminal-rendering-what-can-i-do) By default, the integrated terminal will render using GPU acceleration on most machines. Typically when there are rendering problems it's an issue of something in your hardware/OS/drivers not playing nicely with the GPU renderer. The first thing to try is to disable GPU acceleration, trading off rendering speed for DOM-based rendering, which is more reliable: JSON ``` { "terminal.integrated.gpuAcceleration": "off" } ``` See the [GPU acceleration](https://code.visualstudio.com/docs/terminal/appearance#_gpu-acceleration) section for more information. ### [I see 1~ or \[201~ when I paste something](https://code.visualstudio.com/docs/terminal/basics#_i-see-1-or-201-when-i-paste-something) This normally means that the program/shell running inside the terminal requested to turn on "bracketed paste mode" but something doesn't support it properly. To work around this, you could run `printf "\e[?2004l"` to disable it for that session or add the following to your `~/.inputrc` file: Bash ``` set enable-bracketed-paste off ``` Alternatively, bracketed paste mode can be forced to ignore the shell's request by turning it off with this setting: JSON ``` { "terminal.integrated.ignoreBracketedPasteMode": true } ``` ### [Ctrl+A, Ctrl+R output ^A, ^R on zsh](https://code.visualstudio.com/docs/terminal/basics#_ctrla-ctrlr-output-a-r-on-zsh) This can happen if zsh is in Vim mode instead of Emacs mode, due to setting `$EDITOR` or `$VISUAL` to `vi`/`vim` in your init scripts. To work around this, you have two options: - Ensure that you don't set `$EDITOR` to `vi(m)`. However, this isn't an option if you want your Git editor to work. - Add `bindkey -e` to your init script to set Emacs explicitly. ### [How can I configure Cmd+. to map to Ctrl+C like macOS' built-in terminal?](https://code.visualstudio.com/docs/terminal/basics#_how-can-i-configure-cmd-to-map-to-ctrlc-like-macos-builtin-terminal) The macOS default terminal uses Cmd+. to perform the same as Ctrl+C. To get this behavior in VS Code, add this [custom keyboard shortcut](https://code.visualstudio.com/docs/configure/keybindings): JSON ``` { "key": "cmd+.", "command": "workbench.action.terminal.sendSequence", "when": "terminalFocus", "args": { "text": "\u0003" } } ``` ### [Why are the colors in the terminal not correct?](https://code.visualstudio.com/docs/terminal/basics#_why-are-the-colors-in-the-terminal-not-correct) One of our accessibility features we enable by default is to ensure a minimum contrast ratio of at least 4.5 is met for the foreground text. This feature ensures that text is readable regardless of the shell and theme used which is not possible otherwise. To disable this feature, you can set: JSON ``` "terminal.integrated.minimumContrastRatio": 1 ``` See the [minimum contrast ratio](https://code.visualstudio.com/docs/terminal/appearance#_minimum-contrast-ratio) section for more information. ## Help and support ### Still need help? - [![](https://code.visualstudio.com/assets/community/sidebar/stackoverflow.svg)Ask the community](https://stackoverflow.com/questions/tagged/vscode) - [![](https://code.visualstudio.com/assets/community/sidebar/github.svg)Request features](https://go.microsoft.com/fwlink/?LinkID=533482) - [![](https://code.visualstudio.com/assets/community/sidebar/issue.svg)Report issues](https://www.github.com/Microsoft/vscode/issues) ### Help us improve Edit this page 4/8/2026 - [![RSS](https://code.visualstudio.com/assets/community/sidebar/rss.svg)RSS Feed](https://code.visualstudio.com/feed.xml) - [![Stackoverflow](https://code.visualstudio.com/assets/community/sidebar/stackoverflow.svg)Ask questions](https://stackoverflow.com/questions/tagged/vscode) - [![Twitter](https://code.visualstudio.com/assets/community/sidebar/twitter.svg)Follow @code](https://go.microsoft.com/fwlink/?LinkID=533687) - [![GitHub](https://code.visualstudio.com/assets/community/sidebar/github.svg)Request features](https://go.microsoft.com/fwlink/?LinkID=533482) - [![Issues](https://code.visualstudio.com/assets/community/sidebar/issue.svg)Report issues](https://www.github.com/Microsoft/vscode/issues) - [![YouTube](https://code.visualstudio.com/assets/community/sidebar/youtube.svg)Watch videos](https://www.youtube.com/channel/UCs5Y5_7XK8HLDX0SLNwkd3w) - [![VS Code on Github](https://code.visualstudio.com/assets/icons/github-icon.svg)](https://github.com/microsoft/vscode) - [![Follow us on X](https://code.visualstudio.com/assets/icons/x-icon.svg)](https://go.microsoft.com/fwlink/?LinkID=533687) - [![VS Code on LinkedIn](https://code.visualstudio.com/assets/icons/linkedin-icon.svg)](https://www.linkedin.com/showcase/vs-code) - [![VS Code on Bluesky](https://code.visualstudio.com/assets/icons/bluesky-icon.svg)](https://bsky.app/profile/vscode.dev) - [![Join the VS Code community on Reddit](https://code.visualstudio.com/assets/icons/reddit-icon.svg)](https://www.reddit.com/r/vscode/) - [![The VS Code Insiders Podcast](https://code.visualstudio.com/assets/icons/podcast-icon.svg)](https://www.vscodepodcast.com/) - [![VS Code on TikTok](https://code.visualstudio.com/assets/icons/tiktok-icon.svg)](https://www.tiktok.com/@vscode) - [![VS Code on YouTube](https://code.visualstudio.com/assets/icons/youtube-icon.svg)](https://www.youtube.com/@code) [![Microsoft homepage](https://code.visualstudio.com/assets/icons/microsoft.svg)](https://www.microsoft.com/) - [Support](https://support.serviceshub.microsoft.com/supportforbusiness/create?sapId=d66407ed-3967-b000-4cfb-2c318cad363d "Get support for VS Code") - [Privacy](https://go.microsoft.com/fwlink/?LinkId=521839 "View the Microsoft privacy statement") - [Manage Cookies]() - [Terms of Use](https://www.microsoft.com/legal/terms-of-use "View the Microsoft Terms of Use") - [License](https://code.visualstudio.com/License "View the Visual Studio Code license") - [Your Privacy Choices](https://aka.ms/YourCaliforniaPrivacyChoices "View Your Privacy Choices") - [Consumer Health Privacy](https://go.microsoft.com/fwlink/?linkid=2259814 "View the Microsoft Consumer Health Privacy policy")
Readable Markdown	Visual Studio Code includes a full featured integrated terminal that starts at the root of your workspace. It provides integration with the editor to support features like [links](https://code.visualstudio.com/docs/terminal/basics#_links) and [error detection](https://code.visualstudio.com/docs/debugtest/tasks). The integrated terminal can run commands such as mkdir and git just like a standalone terminal. You can open a terminal as follows: - From the menu, use the Terminal \> New Terminal or View \> Terminal menu commands. - From the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)), use the View: Toggle Terminal command. - In the Explorer, you can use the Open in Integrated Terminal context menu command to open a new terminal from a folder. - To toggle the terminal panel, use the ⌃\` (Windows, Linux Ctrl+\`) keyboard shortcut. - To create a new terminal, use the ⌃⇧\` (Windows, Linux Ctrl+Shift+\`) keyboard shortcut. VS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar: ![The integrated terminal can run commands such as mkdir and git just like a standalone terminal. VS Code's terminal has additional functionality called shell integration that tracks where commands are run with decorations on the left of a command and in the scrollbar.](https://code.visualstudio.com/assets/docs/terminal/basics/integrated-terminal.png) Note If you prefer to work outside VS Code, open an external terminal with the ⇧⌘C (Windows, Linux Ctrl+Shift+C) keyboard shortcut ## [Terminal shells](https://code.visualstudio.com/docs/terminal/basics#_terminal-shells) The integrated terminal can use various shells installed on your machine, with the default being pulled from your system defaults. Shells are detected and presented in the terminal profiles dropdown. ![A detected profile can be chosen in the dropdown next to the new terminal button. Some examples on Windows include PowerShell, Command Prompt, Git Bash and WSL](https://code.visualstudio.com/assets/docs/terminal/basics/select-profile-dropdown.png) You can learn more about configuring terminal shells in the [terminal profiles](https://code.visualstudio.com/docs/terminal/profiles) article. ## [Managing terminals](https://code.visualstudio.com/docs/terminal/basics#_managing-terminals) The terminal tabs UI is on the right side of the terminal view. Each terminal has an entry with its name, icon, color, and group decoration (if any). ![Activating the Launch Profile button will show all detected and manually configured profiles](https://code.visualstudio.com/assets/docs/terminal/basics/tabs.png) Add terminal instances by selecting the \+ icon on the top-right of the TERMINAL panel, selecting a profile from the terminal dropdown, or by triggering the ⌃⇧\` (Windows, Linux Ctrl+Shift+\`) command. This action creates another entry in the tab list associated with that terminal. Remove terminal instances by hovering a tab and selecting the Trash Can button, selecting a tab item and pressing Delete, using Terminal: Kill the Active Terminal Instance command, or via the right-click context menu. Navigate between terminal groups using focus next ⇧⌘\] (Windows, Linux Ctrl+PageDown) and focus previous ⇧⌘\[ (Windows, Linux Ctrl+PageUp). Icons may appear to the right of the terminal title on the tab label when a terminal's status changes. Some examples are a bell (macOS) and for tasks, displaying a check mark when there are no errors and an X otherwise. Hover the icon to read status information, which may contain actions. ### [Groups (split panes)](https://code.visualstudio.com/docs/terminal/basics#_groups-split-panes) Place multiple terminals side-by-side and create a group by splitting a terminal: - Hover over an entry in the list of terminals on the right and select the inline split button. - Right-click the context menu and select the Split menu option. - Alt and click on a tab, the \+ button, or the single tab on the terminal panel. - Trigger the ⌘\\ (Windows, Linux Ctrl+Shift+5) command. Tip The working directory for the new terminal depends on the terminal.integrated.splitCwd [setting](https://code.visualstudio.com/docs/configure/settings). Navigate between terminals in a group by focusing the previous pane, ⌥⌘← (Windows, Linux Alt+Left), or the next pane, ⌥⌘→ (Windows, Linux Alt+Right). Dragging and dropping tabs in the list rearranges them. Dragging a tab into the main terminal area allows moving a terminal from one group to another. Moving a terminal into its own group can be done with the Terminal: Unsplit Terminal command through the Command Palette or in the right-click context menu. ## [Terminals in editor area](https://code.visualstudio.com/docs/terminal/basics#_terminals-in-editor-area) You can open terminals in the editor area (terminal editors) with the Terminal: Create New Terminal in Editor Area command, the Terminal: Create New Terminal in Editor Area to the Side command, or by dragging a terminal from the terminal view into the editor area. Terminal editors are presented like regular editor tabs: ![Terminal editors are presented like regular text file tabs](https://code.visualstudio.com/assets/docs/terminal/basics/terminal-editor.png) You can have terminal editors on either side or arranged in multiple dimensions using the editor group layout system, e.g. PowerShell and WSL terminals stacked to the right of file editors: ![Terminal editors are can be laid out using the editor group layout system, for example 2 terminals could sit to the right of a text editor](https://code.visualstudio.com/assets/docs/terminal/basics/terminal-editor-grid.png) The terminal.integrated.defaultLocation setting can change the default `view` or `editor` area terminal location. ## [Terminals in new windows](https://code.visualstudio.com/docs/terminal/basics#_terminals-in-new-windows) Opening a terminal in a new VS Code window is possible in a few different ways: - Use ⌃⇧⌥\` (Windows, Linux Ctrl+Shift+Alt+\`) - Right-click the terminal tab if you have multiple terminals, or left-click the tab if you only have a single terminal opened. Then select Move Terminal to New Window - Select the New Terminal Window entry that's available in several different menus ## [Navigating the buffer](https://code.visualstudio.com/docs/terminal/basics#_navigating-the-buffer) The content in the terminal is called the buffer, with the section right above the bottom viewport being called "scrollback". The amount of scrollback kept is determined by the terminal.integrated.scrollback [setting](https://code.visualstudio.com/docs/configure/settings) and defaults to `1000` lines. There are various commands available to navigate around the terminal buffer: - Scroll up a line - ⌥⌘PageUp (Windows Ctrl+Alt+PageUp, Linux Ctrl+Shift+Up) - Scroll down a line - ⌥⌘PageDown (Windows Ctrl+Alt+PageDown, Linux Ctrl+Shift+Down) - Scroll up a page - PageUp (Windows, Linux Shift+PageUp) - Scroll down a page - PageDown (Windows, Linux Shift+PageDown) - Scroll to the top - ⌘Home (Windows Ctrl+Home, Linux Shift+Home) - Scroll to the bottom - ⌘End (Windows Ctrl+End, Linux Shift+End) Command navigation is also available (see [shell integration](https://code.visualstudio.com/docs/terminal/shell-integration)): - Scroll to the previous command - ⌘↑ (Windows, Linux Ctrl+Up) - Scroll to the next command - ⌘↓ (Windows, Linux Ctrl+Down) Scrolling will happen instantaneously, but can be configured to animate over a short duration with the terminal.integrated.smoothScrolling setting. ## [Links](https://code.visualstudio.com/docs/terminal/basics#_links) The terminal features sophisticated link detection with editor integration and even extension contributed link handlers. Hover over a link to display an underline, then hold the Ctrl/Cmd key and click. These built-in link handlers are used in the following priority order: - URIs/URLs: Links that look like URIs, such as `https://code.visualstudio.com`, `vscode://path/to/file` or `file://path/to/file` will open using the standard handler for the protocol. For example, `https` links will open the browser. ![Opening a URI link will open it in the system browser](https://code.visualstudio.com/assets/docs/terminal/basics/link-uri.png) - File links: Links to files that have been verified to exist on the system. These will open the file in a new editor tab and support many common line/column formats such as `file:1:2`, `file:line 1, column 2`. ![Activating a file link will open it in an editor](https://code.visualstudio.com/assets/docs/terminal/basics/link-file.png) - Folder links: Links to folders are similar to file links but will open a new VS Code window at the folder. ![Activating a folder link will open it in a new window](https://code.visualstudio.com/assets/docs/terminal/basics/link-folder.png) - Word links: Fallback link type that uses the terminal.integrated.wordSeparators setting. The setting defines word boundaries and make nearly all text into words. Activating a word link searches the workspace for the word. If there is a single result it will open, otherwise it will present the search results. Word links are considered "low confidence" and will not show an underline or tooltip unless you hold the Ctrl/Cmd key. They also have limited support for line and column suffixes. ![Activating a word link 'terminal:15' will open a Quick Pick searching the workspace for all files containing 'terminal', choosing an option will open the file at line 15](https://code.visualstudio.com/assets/docs/terminal/basics/link-word.png) The Open Detected Link command (⇧⌘G (Windows, Linux Ctrl+Shift+G)) can be used to access links via the keyboard: ![Open Detected Link opens a quick pick with all links in the viewport, split into categories](https://code.visualstudio.com/assets/docs/terminal/basics/link-open-detected.png) Tip If link verification causes performance issues, like in high latency remote environments, disable it via the terminal.integrated.enableFileLinks [setting](https://code.visualstudio.com/docs/configure/settings). ### [Extensions handling links](https://code.visualstudio.com/docs/terminal/basics#_extensions-handling-links) Extensions can contribute link providers which allow the extension to define what happens when clicked. An example of this is the [GitLens](https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens) extension detecting Git branch links. ![When GitLens is installed, hovering a branch name will provide custom behavior to open the branch in the UI](https://code.visualstudio.com/assets/docs/terminal/basics/link-extension.png) ### [Keyboard accessibility](https://code.visualstudio.com/docs/terminal/basics#_keyboard-accessibility) Links are keyboard accessible through several commands that open links based on the type of link. - Terminal: Open Last Local File Link - Opens the most recent local file link. No default keyboard shortcut. - Terminal: Open Last URL link - Opens the most recent URI/URL link. No default keyboard shortcut. - Terminal: Open Detected Link... - Opens a searchable Quick Pick with all detected links, including word links. The default keyboard shortcut is Ctrl/Cmd+Shift+O, which is the same as the Go to Symbol in Editor keyboard shortcut. ## [Copy & paste](https://code.visualstudio.com/docs/terminal/basics#_copy-paste) The keyboard shortcuts for copy and paste follow platform standards: - Linux: Ctrl+Shift+C and Ctrl+Shift+V; selection paste is available with Shift+Insert - macOS: Cmd+C and Cmd+V - Windows: Ctrl+C and Ctrl+V Copying is done automatically on selection when terminal.integrated.copyOnSelection is enabled. By default, there is a warning when pasting multiple lines, which can be disabled with the terminal.integrated.enableMultiLinePasteWarning setting. This is only done when the shell does not support "bracketed paste mode". When that mode is enabled, the shell is indicating that it can handle multiple line pasting. ## [Using the mouse](https://code.visualstudio.com/docs/terminal/basics#_using-the-mouse) ### [Right-click behavior](https://code.visualstudio.com/docs/terminal/basics#_rightclick-behavior) The right-click behavior differs based on the platform: - Linux: Show the context menu. - macOS: Select the word under the cursor and show the context menu. - Windows: Copy and drop selection if there is a selection, otherwise paste. This can be configured using the terminal.integrated.rightClickBehavior setting. The options are: - `default` - Show the context menu. - `copyPaste` - Copy when there is a selection, otherwise paste. - `paste` - Paste on right-click. - `selectWord` - Select the word under the cursor and show the context menu. - `nothing` - Do nothing and pass event to terminal. ### [Column selection](https://code.visualstudio.com/docs/terminal/basics#_column-selection) Press Alt and left-click drag to select a rectangle of text inside the terminal instead of the regular selection of a line. ### [Reposition the cursor with Alt](https://code.visualstudio.com/docs/terminal/basics#_reposition-the-cursor-with-alt) Alt and left-click will reposition the cursor to underneath the mouse. This works by simulating arrow keystrokes, which may not work reliably for some shells or programs. This feature can be disabled with the terminal.integrated.altClickMovesCursor setting. ### [Mouse events mode](https://code.visualstudio.com/docs/terminal/basics#_mouse-events-mode) When applications running in the terminal turn on mouse events mode, such as Vim mouse mode, mouse interaction is sent to the application instead of the terminal. This means that clicking and dragging will no longer create a selection. Terminal selection can be forced by holding the Alt key on Windows and Linux, this can also be done with the Option key on macOS but requires enabling the terminal.integrated.macOptionClickForcesSelection setting first. ## [Find](https://code.visualstudio.com/docs/terminal/basics#_find) The integrated terminal has find functionality that can be triggered with ⌘F (Windows, Linux Ctrl+F). ![Find in the terminal will highlight all text matching the query](https://code.visualstudio.com/assets/docs/terminal/basics/terminal-find.png) Tip Ctrl+F can be sent to the shell by removing the `workbench.action.terminal.focusFind` command from [commands to skip shell](https://code.visualstudio.com/docs/terminal/advanced#_keyboard-shortcuts-and-the-shell). ## [Run selected text](https://code.visualstudio.com/docs/terminal/basics#_run-selected-text) To use the `runSelectedText` command, select text in an editor and run the command Terminal: Run Selected Text in Active Terminal via the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)), the terminal will attempt to run the selected text. If no text is selected in the active editor, the entire line that the cursor is on will run in the terminal. Tip Also run the active file using the command `workbench.action.terminal.runActiveFile`. ## [Maximizing the terminal](https://code.visualstudio.com/docs/terminal/basics#_maximizing-the-terminal) The terminal view can be maximized by clicking the maximize panel size button with the upwards chevron icon. This will temporarily hide the editors and maximize the panel. This is useful to temporarily focus on a large amount of output. Some developers use VS Code as a standalone terminal by opening a new window, maximizing the panel, and hiding the side bar. Note that the panel can only be maximized if its [alignment](https://code.visualstudio.com/docs/configure/custom-layout#_panel-alignment) option is set to Center. ## [Select all](https://code.visualstudio.com/docs/terminal/basics#_select-all) There is a Terminal: Select All command, which is bound to Cmd+A on macOS, but does not have a default keyboard shortcut on Windows and Linux as it may conflict with shell hotkeys. To use Ctrl+A to select all, add this custom keyboard shortcut: ``` { "key": "ctrl+a", "command": "workbench.action.terminal.selectAll", "when": "terminalFocus && !isMac" }, ``` ## [Drag and drop file paths](https://code.visualstudio.com/docs/terminal/basics#_drag-and-drop-file-paths) Dragging a file into the terminal will input the path into the terminal, with escaping to match the active shell. ## [Automating terminals with tasks](https://code.visualstudio.com/docs/terminal/basics#_automating-terminals-with-tasks) The [Tasks](https://code.visualstudio.com/docs/debugtest/tasks) feature can be used to automate the launching of terminals, for example, the following `.vscode/tasks.json` file will launch a Command Prompt and PowerShell terminal in a single terminal group when the window starts: ``` { "version": "2.0.0", "presentation": { "echo": false, "reveal": "always", "focus": false, "panel": "dedicated", "showReuseMessage": true }, "tasks": [ { "label": "Create terminals", "dependsOn": [ "First", "Second" ], // Mark as the default build task so cmd/ctrl+shift+b will create them "group": { "kind": "build", "isDefault": true }, // Try start the task on folder open "runOptions": { "runOn": "folderOpen" } }, { // The name that shows up in terminal tab "label": "First", // The task will launch a shell "type": "shell", "command": "", // Set the shell type "options": { "shell": { "executable": "cmd.exe", "args": [] } }, // Mark as a background task to avoid the spinner animation on the terminal tab "isBackground": true, "problemMatcher": [], // Create the tasks in a terminal group "presentation": { "group": "my-group" } }, { "label": "Second", "type": "shell", "command": "", "options": { "shell": { "executable": "pwsh.exe", "args": [] } }, "isBackground": true, "problemMatcher": [], "presentation": { "group": "my-group" } } ] } ``` This file could be committed to the repository to share with other developers or created as a user task via the `workbench.action.tasks.openUserTasks` command. ## [Working directory](https://code.visualstudio.com/docs/terminal/basics#_working-directory) By default, the terminal will open at the folder that is opened in the Explorer. The terminal.integrated.cwd setting allows specifying a custom path to open instead: ``` { "terminal.integrated.cwd": "/home/user" } ``` Split terminals on Windows will start in the directory that the parent terminal started with. On macOS and Linux, split terminals will inherit the current working directory of the parent terminal. This behavior can be changed using the terminal.integrated.splitCwd setting: ``` { "terminal.integrated.splitCwd": "workspaceRoot" } ``` There are also extensions available that give more options such as [Terminal Here](https://marketplace.visualstudio.com/items?itemName=Tyriar.vscode-terminal-here). ## [Fixed dimension terminals](https://code.visualstudio.com/docs/terminal/basics#_fixed-dimension-terminals) The Terminal: Set Fixed Dimensions command allows changing the number of columns and rows that the terminal and it's backing pseudoterminal uses. This will add scroll bars when necessary, which may lead to an unpleasant UX and is generally not recommended, but it is a common ask on Windows in particular for reading logs or long lines when paging tools aren't available. You can also right-click on a terminal tab and select Toggle Size to Content Width (⌥Z (Windows, Linux Alt+Z)) to resize the number of terminal columns to the largest wrapped line in the terminal. ## [GitHub Copilot in the terminal](https://code.visualstudio.com/docs/terminal/basics#_github-copilot-in-the-terminal) If you have access to [GitHub Copilot](https://code.visualstudio.com/docs/copilot/setup), you can use it to get AI-powered help with terminal commands and shell scripting. There are several ways to use Copilot with the terminal: ### [Terminal inline chat](https://code.visualstudio.com/docs/terminal/basics#_terminal-inline-chat) Start an inline chat directly in the terminal to get help with shell commands: 1. Open the terminal (⌃\` (Windows, Linux Ctrl+\`)) 2. Press ⌘I (Windows, Linux Ctrl+I) or run the Terminal Inline Chat command from the Command Palette 3. Enter your question or request in natural language, such as: - "How do I find the largest files in this directory?" - "Show me how to undo the last git commit" - "Create a bash script to analyze log files" ![Terminal inline chat helps you quickly get and run shell commands](https://code.visualstudio.com/assets/docs/terminal/basics/terminal-chat-2.png) When Copilot provides a response, you can select Run to execute the command directly or Insert to add it to the terminal for further editing. For more information about using GitHub Copilot with the terminal, see [Use terminal inline chat](https://code.visualstudio.com/docs/copilot/chat/inline-chat#_use-terminal-inline-chat). ### [Terminal chat participant](https://code.visualstudio.com/docs/terminal/basics#_terminal-chat-participant) Use the dedicated `@terminal` chat participant in ask mode in the Chat view: 1. Open the Chat view (⌃⌘I (Windows, Linux Ctrl+Alt+I)) 2. Start your question with `@terminal` to direct it to the terminal participant 3. Ask about terminal commands, shell scripting, or explaining terminal output Examples: - `@terminal list the 5 largest files in this workspace` - `@terminal /explain top shell command` - `@terminal how to grep for patterns recursively` ### [Reference terminal context in chat](https://code.visualstudio.com/docs/terminal/basics#_reference-terminal-context-in-chat) You can include terminal information as context in your chat prompts: - Use `#terminalSelection` to add selected text from the terminal to your chat prompt - Use `#terminalLastCommand` to include the last command you ran in the terminal ## [Next steps](https://code.visualstudio.com/docs/terminal/basics#_next-steps) The basics of the terminal have been covered in this document. Read on to find out more about: - [Terminal inline chat](https://code.visualstudio.com/docs/copilot/chat/inline-chat#_use-terminal-inline-chat) - AI-powered suggestions right in your terminal. - [Tasks](https://code.visualstudio.com/docs/debugtest/tasks) - Tasks let you integrate with external tools and leverage the terminal heavily. - [Mastering VS Code's Terminal](https://www.growingwiththeweb.com/2017/03/mastering-vscodes-terminal.html) - An external blog with plenty of power user tips for the terminal. - Explore terminal commands by browsing the keyboard shortcuts within VS Code (Preferences: Open Keyboard Shortcuts then search on 'terminal'). ## [Common questions](https://code.visualstudio.com/docs/terminal/basics#_common-questions) ### [I'm having problems launching the terminal](https://code.visualstudio.com/docs/terminal/basics#_im-having-problems-launching-the-terminal) There's a [dedicated troubleshooting guide](https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch) for these sorts of problems. ### [How do I create an Admin terminal?](https://code.visualstudio.com/docs/terminal/basics#_how-do-i-create-an-admin-terminal) The integrated terminal shell is running with the permissions of VS Code. If you need to run a shell command with elevated (administrator) or different permissions, use platform utilities such as `runas.exe` within a terminal. You can learn more about customizing terminals via terminal profiles in [Configuring Profiles](https://code.visualstudio.com/docs/terminal/profiles#_configuring-profiles). ### [Can I add a keyboard shortcut for the Explorer's Open in Integrated Terminal command?](https://code.visualstudio.com/docs/terminal/basics#_can-i-add-a-keyboard-shortcut-for-the-explorers-open-in-integrated-terminal-command) You can open new terminals for specific folders from the Explorer via the Open in Integrated Terminal context menu command. ![A folder selected in the Explorer displaying the context menu with the Open in Integrated Terminal command](https://code.visualstudio.com/assets/docs/terminal/basics/open-in-terminal-command.png) By default, there is no keyboard shortcut associated with Open in Integrated Terminal but you can add your own via the Keyboard Shortcuts editor (⌘K ⌘S (Windows, Linux Ctrl+K Ctrl+S)) to add a keyboard shortcut to your `keybindings.json`. The `keybindings.json` example below adds the keyboard shortcut Ctrl+T for `openInTerminal`. ``` { "key": "ctrl+t", "command": "openInTerminal", "when": "filesExplorerFocus" } ``` ### [Why is nvm complaining about a prefix option when the integrated terminal is launched?](https://code.visualstudio.com/docs/terminal/basics#_why-is-nvm-complaining-about-a-prefix-option-when-the-integrated-terminal-is-launched) nvm (Node Version Manager) users often see this error for the first time inside VS Code's integrated terminal: ``` nvm is not compatible with the npm config "prefix" option: currently set to "/usr/local" Run `npm config delete prefix` or `nvm use --delete-prefix v8.9.1 --silent` to unset it ``` This is mostly a macOS problem and does not happen in external terminals. The typical reasons for this are the following: - `npm` was globally installed using another instance of `node` that is somewhere in your path (such as `/usr/local/bin/npm`). - To get the development tools on the `$PATH`, VS Code will launch a bash login shell on startup. This means that your `~/.bash_profile` has already run and when an integrated terminal launches, it will run another login shell, reordering the `$PATH` potentially in unexpected ways. To resolve this issue, you need to track down where the old `npm` is installed and remove both it and its out-of-date node\_modules. Find the `nvm` initialization script and run `which npm` before it runs, which should print the path when you launch a new terminal. Once you have the path to npm, find the old node\_modules by resolving the symlink by running a command something like this: ``` ls -la /usr/local/bin \| grep "np[mx]" ``` This will give you the resolved path at the end: ``` ... npm -> ../lib/node_modules/npm/bin/npm-cli.js ... npx -> ../lib/node_modules/npm/bin/npx-cli.js ``` From there, removing the files and relaunching VS Code should fix the issue: ``` rm /usr/local/bin/npm /usr/local/lib/node_modules/npm/bin/npm-cli.js rm /usr/local/bin/npx /usr/local/lib/node_modules/npm/bin/npx-cli.js ``` ### [Why does macOS make a ding sound when I resize terminal split panes?](https://code.visualstudio.com/docs/terminal/basics#_why-does-macos-make-a-ding-sound-when-i-resize-terminal-split-panes) The keyboard shortcuts ⌃⌘← and ⌃⌘→ are the defaults for resizing individual split panes in the terminal. While they work, they also cause a system "invalid key" sound to play due to an issue in Chromium. The [recommended workaround](https://github.com/microsoft/vscode/issues/44070#issuecomment-799716362) is to tell macOS to no-op for these keyboard shortcuts by running this in your terminal: ``` mkdir -p ~/Library/KeyBindings cat > ~/Library/KeyBindings/DefaultKeyBinding.dict <<EOF { "@^\UF700" = "noop:"; "@^\UF701" = "noop:"; "@^\UF702" = "noop:"; "@^\UF703" = "noop:"; "@~^\UF700" = "noop:"; "@~^\UF701" = "noop:"; "@~^\UF702" = "noop:"; "@~^\UF703" = "noop:"; } EOF ``` ### [I'm having problems with the terminal rendering. What can I do?](https://code.visualstudio.com/docs/terminal/basics#_im-having-problems-with-the-terminal-rendering-what-can-i-do) By default, the integrated terminal will render using GPU acceleration on most machines. Typically when there are rendering problems it's an issue of something in your hardware/OS/drivers not playing nicely with the GPU renderer. The first thing to try is to disable GPU acceleration, trading off rendering speed for DOM-based rendering, which is more reliable: ``` { "terminal.integrated.gpuAcceleration": "off" } ``` See the [GPU acceleration](https://code.visualstudio.com/docs/terminal/appearance#_gpu-acceleration) section for more information. ### [I see 1~ or \[201~ when I paste something](https://code.visualstudio.com/docs/terminal/basics#_i-see-1-or-201-when-i-paste-something) This normally means that the program/shell running inside the terminal requested to turn on "bracketed paste mode" but something doesn't support it properly. To work around this, you could run `printf "\e[?2004l"` to disable it for that session or add the following to your `~/.inputrc` file: ``` set enable-bracketed-paste off ``` Alternatively, bracketed paste mode can be forced to ignore the shell's request by turning it off with this setting: ``` { "terminal.integrated.ignoreBracketedPasteMode": true } ``` ### [Ctrl+A, Ctrl+R output ^A, ^R on zsh](https://code.visualstudio.com/docs/terminal/basics#_ctrla-ctrlr-output-a-r-on-zsh) This can happen if zsh is in Vim mode instead of Emacs mode, due to setting `$EDITOR` or `$VISUAL` to `vi`/`vim` in your init scripts. To work around this, you have two options: - Ensure that you don't set `$EDITOR` to `vi(m)`. However, this isn't an option if you want your Git editor to work. - Add `bindkey -e` to your init script to set Emacs explicitly. ### [How can I configure Cmd+. to map to Ctrl+C like macOS' built-in terminal?](https://code.visualstudio.com/docs/terminal/basics#_how-can-i-configure-cmd-to-map-to-ctrlc-like-macos-builtin-terminal) The macOS default terminal uses Cmd+. to perform the same as Ctrl+C. To get this behavior in VS Code, add this [custom keyboard shortcut](https://code.visualstudio.com/docs/configure/keybindings): ``` { "key": "cmd+.", "command": "workbench.action.terminal.sendSequence", "when": "terminalFocus", "args": { "text": "\u0003" } } ``` ### [Why are the colors in the terminal not correct?](https://code.visualstudio.com/docs/terminal/basics#_why-are-the-colors-in-the-terminal-not-correct) One of our accessibility features we enable by default is to ensure a minimum contrast ratio of at least 4.5 is met for the foreground text. This feature ensures that text is readable regardless of the shell and theme used which is not possible otherwise. To disable this feature, you can set: ``` "terminal.integrated.minimumContrastRatio": 1 ``` See the [minimum contrast ratio](https://code.visualstudio.com/docs/terminal/appearance#_minimum-contrast-ratio) section for more information. 4/8/2026
Shard	22 (laksa)
Root Hash	11536831065451992222
Unparsed URL	com,visualstudio!code,/docs/terminal/basics s443