A way to stop the integrated terminal from launching at startup

[CrendKing]

VSCode version: 1.65.2

I use VSCode to develop Rust project. If I run a build task (such as cargo build), it runs in the integrated terminal. If I close VSCode without closing that terminal session, next time I open the same workspace, the integrated terminal will launch at startup. The problem is that it launches with the default profile (with same "pwsh"), which is not reused by the build tasks. Therefore, that session is wasted and stays forever unless I manually close it.

I tested this is not a behavior introduced by any extension. I also tried every existing setting I can find. Nothing (such as terminal.integrated.enablePersistentSessions) works. Also, if I go to delete the workspace state file from data\user-data\User\workspaceStorage<random_string>, the terminal no longer opens, so I think it's from VSCode. Internet shows various way to auto launch terminal at startup, but I need the exact opposite.

Screenshot: The "pwsh" is the auto launched one. The second is the build task I launch.

[pcjmfranken]

You sure you're unable to reproduce this with all extensions disabled?

I've had exactly this happen before and it took me a while to figure out.

Turned out that the language's official extension picked up on build commands I ran through the integrated terminal, and then tried to be helpful by "hijacking" my invocation and running its own VSCode Task instead (which was configured to open a terminal window).

Edit: And that's suspiciously similar to what the official Rust extension says it does 😉

[CrendKing]

This is 100% reproducible with all my installed extensions disabled. It has nothing to do with Rust (I don't have Rust extension). All you need to do is:

1. Create a new directory.
2. Open the directory with VSCode.
3. Open the integrated terminal.
4. Exit VSCode.
5. Open the directory with VSCode again.

I don't want that terminal be opened at startup.

[pcjmfranken]

Thanks for confirming, was

Just recalled there's another setting involving this weird session revival behaviour:

  "terminal.integrated.persistentSessionReviveProcess": "never",
  "terminal.integrated.enablePersistentSessions": false,

To Microsoft: Please kill this feature with fire, or at least disable it by default. The reanimated sessions are unpredictable, confusing, and often lead to conflicts and crashes.

[CrendKing]

You are exactly correct sir! The combination of the two did it. Feel free to close this.

[CrendKing]

Wait. I tried again, and it's no longer working. Was I hallucinating? I even went to clear the workspaceStorage directory and no.

Also, if persistent session is already disabled by terminal.integrated.enablePersistentSessions, why would terminal.integrated.persistentSessionReviveProcess still needed? I'm not sure if this revival thing is linked to persistent sessions, since the terminal is fresh new every time.

[vscodenpa]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[ibehnam]

This is really annoying. Please disable this "feature". VSC is already bloated and slower than some non-Electron IDEs. This weird behavior only makes it worse. There's no reason that terminal cannot start in the background.

[Tyriar]

/duplicate #39137