MR: Pending <!-- NOTE: For context on MR heading, see: https://handbook.gitlab.com/handbook/engineering/development/dev/create/remote-development/index.html#relationship-of-issues-to-mrs --> ## Description As a user, I want to be able to configure my workspaces to _not_ auto-open a terminal so that I don't have a 'dead end' terminal open, confusing users. ### Long Description In our use-case, we spin up a workspace with a 'heavy' image that already contains recently cloned projects and other preconfigured items. We copy/move items out of the 'container space' into the 'workspace space' (in `/projects`) and do this through a startup script in `.vscode/tasks.json`. One of the tools inside the container image that handles internal dependencies is `mise`. `mise` operates heavily through some shell prehooks ([more info here](https://mise.jdx.dev/dev-tools/shims.html#path-activation)), but in a nutshell performs some "magic" every time a new shell is created. In our use-case, we want this "magic" to happen _after_ our startup script is complete. By opening a terminal at the first open, some of the commands that would be available later on, are not yet available. This could be confusing to users. Fixing the issue is as simple as creating a new terminal, or even running `exec bash` - but this is a step we could likely remove if the 'default terminal' wasn't opened. <!-- OPTIONAL: Is this a feature/enhancement? - Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole. - Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality. --> <!-- OPTIONAL: Is this a bug? Please uncomment and include the following: - **Current behavior:** - **Expected behavior:** - **Steps to reproduce:** - **Additional information:** please include VSCode version, browser dev tool logs, etc that might be helpful to debug the issue! --> ## Acceptance criteria TODO: Fill out (required) - [ ] [Describe what must be achieved to complete this issue.] - [ ] [If applicable, please provide design specifications for this feature/enhancement.] - [ ] [If applicable, please list any technical requirements (performance, security, database, etc.)] ## Implementation plan TODO: Fill out or delete (optional) [Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.] <!-- NOTE: Feel free to expand with more sections and headers as needed --> <!-- DO NOT TOUCH BELOW -->