Extract the integrated terminal
"Feature" request. The integrated terminal grows in functionality, to the point that it could soon become very useful standalone, as its *own app*. I'm only a casual VScode user (using vim most of the time), but I would definitely be interested in a well-behaved, consistent, reactively-configurable, multi-platform terminal not tied to the editor. Obviously if such a situation were to unfold, the shared component (not entirely dissimilar to VTE) should be jointly developed and shared with VScode. Both could be able to leverage a common configuration so that whether a terminal leveraging such a theoretical common component is spawned within VScode or standalone, they behave the same. --- Edit from @Tyriar: There is some confusion about the scope of this issue, here is the clarification as the thread is long: - This issue is tracking making the terminal "stand alone", ie. being able to launch `code --term` for example (see https://github.com/microsoft/vscode/issues/34442#issuecomment-901959244 for details) - #10121 tracks being able to pull the terminal _view_/_panel_ out of the window - #10546 tracks adding tabs to the terminal, combined with #10121 this would ideally allow terminal _tabs_ to be pulled into a separate window There is also an existing feature to open "terminal windows" (ctrl/cmd+alt+shift+`), you just need to open them from an existing VS Code instance https://code.visualstudio.com/docs/terminal/basics#_terminals-in-new-windows
Posted by lloeki on Sep 15, 2017, 9:46 AM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
Extract the integrated terminal
"Feature" request. The integrated terminal grows in functionality, to the point that it could soon become very useful standalone, as its *own app*. I'm only a casual VScode user (using vim most of the time), but I would definitely be interested in a well-behaved, consistent, reactively-configurable, multi-platform terminal not tied to the editor. Obviously if such a situation were to unfold, the shared component (not entirely dissimilar to VTE) should be jointly developed and shared with VScode. Both could be able to leverage a common configuration so that whether a terminal leveraging such a theoretical common component is spawned within VScode or standalone, they behave the same. --- Edit from @Tyriar: There is some confusion about the scope of this issue, here is the clarification as the thread is long: - This issue is tracking making the terminal "stand alone", ie. being able to launch `code --term` for example (see https://github.com/microsoft/vscode/issues/34442#issuecomment-901959244 for details) - #10121 tracks being able to pull the terminal _view_/_panel_ out of the window - #10546 tracks adding tabs to the terminal, combined with #10121 this would ideally allow terminal _tabs_ to be pulled into a separate window There is also an existing feature to open "terminal windows" (ctrl/cmd+alt+shift+`), you just need to open them from an existing VS Code instance https://code.visualstudio.com/docs/terminal/basics#_terminals-in-new-windows
Comments (0)
No comments yet. Start the discussion.