Workspace-specific settings and profiles #689

Open
opened 2026-01-30 21:59:42 +00:00 by claunia · 2 comments
Owner

Originally created by @jimbuck on GitHub (May 7, 2019).

Is workspace-specific settings on the roadmap for the Windows Terminal? I was chatting with @jongalloway about it and it would really help streamline teams to be able to check in certain settings or profiles with a solution. VS Code has a great model for Workspace settings and User Settings, I would love to see it here as well. (bonus points for auto-switching settings when cd'ing into a workspace directory).

UserVoice recommendation

Originally created by @jimbuck on GitHub (May 7, 2019). Is workspace-specific settings on the roadmap for the Windows Terminal? I was chatting with @jongalloway about it and it would really help streamline teams to be able to check in certain settings or profiles with a solution. VS Code has a great model for Workspace settings and User Settings, I would love to see it here as well. (bonus points for auto-switching settings when `cd`'ing into a workspace directory). [UserVoice recommendation](https://wpdev.uservoice.com/forums/266908-command-prompt-console-windows-subsystem-for-l/suggestions/37567330-workspace-specific-settings-and-profiles)
claunia added the Issue-FeatureArea-SettingsProduct-Terminal labels 2026-01-30 21:59:42 +00:00
Author
Owner

@miniksa commented on GitHub (May 9, 2019):

Can you define what a workspace is?

If you're specifically referring to changing into a specific directory with the shell of your choice and somehow detecting that to change the settings... that's not something that is really feasible because of the separation of concerns between a Terminal and a Command-Line application.

@miniksa commented on GitHub (May 9, 2019): Can you define what a workspace is? If you're specifically referring to changing into a specific directory with the shell of your choice and somehow detecting that to change the settings... that's not something that is really feasible because of the separation of concerns between a Terminal and a Command-Line application.
Author
Owner

@jimbuck commented on GitHub (May 13, 2019):

Workspace is just your current directory. VS Code allows you to have user settings (per user) and workspace settings (per project). Workspace settings override user settings. This allows teams to have the same settings when working on a project in VS Code. I know the first thing that will happen when I switch over is that I will have to send my profile to others, who will the do the same. Having the ability to check in settings and be able to open a terminal with those settings applied would be great.

And I understand dynamically loading settings is probably out of scope. I mostly just meant it for settings that are strictly visual/terminal-related (font, colors, etc.). But it's not important.

@jimbuck commented on GitHub (May 13, 2019): Workspace is just your current directory. VS Code allows you to have user settings (per user) and workspace settings (per project). Workspace settings override user settings. This allows teams to have the same settings when working on a project in VS Code. I know the first thing that will happen when I switch over is that I will have to send my profile to others, who will the do the same. Having the ability to check in settings and be able to open a terminal with those settings applied would be great. And I understand dynamically loading settings is probably out of scope. I mostly just meant it for settings that are strictly visual/terminal-related (font, colors, etc.). But it's not important.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#689