microsoft / microsoft/vscode-cpptools

Feedback: External Console Closes Automatically in VS Code C/C++

Open
#13,780 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger enhancement help wanted
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Feature Request

Dear VS Code C/C++ Extension Team,

I'm writing to provide feedback regarding the default behavior of the external console when running C++ programs in VS Code.

My main concern is that when I use Ctrl+F5 (Run Without Debugging), the external console window automatically closes as soon as the program finishes executing. This makes it difficult to see the output of simple programs, especially when I'm just trying to quickly check results without entering debug mode.

Many other IDEs, like Dev-C++, keep the console window open by default until the user presses a key. This "pause" functionality is very helpful for a quick overview of the program's output.

While I understand there are workarounds (like adding system("pause"); to my code or configuring externalConsole: false to use the integrated terminal), it feels counter-intuitive for such a common use case. It would greatly improve the user experience if there was a simple, built-in option in the extension or a more straightforward default behavior that keeps the external console open after execution.

Thank you for considering this feedback.

Sincerely,

A VS Code User

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior by running a simple C++ program with Ctrl+F5 and observe the external console after execution. Review the externalConsole setting and the integrated-terminal alternative, then determine where the external-console completion behavior is controlled. Done means a clear, configurable or default behavior keeps the console visible after a run without debugging.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, typescript, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.