starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Dynamic profiles Automatically run command on open #5363

New Issue
Open
opened 2026-01-31 00:11:32 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 00:11:32 +00:00
Owner
Copy Link

Originally created by @krisavi on GitHub (Dec 3, 2019).

Description of the new feature/enhancement

When I create a WSL profile manually using WSL.exe command then there is a possibility to modify start command and add to it to make it to start for example ssh session to some specific location I frequently use. Of course it would mean of changing the start command instead of having another parameter that will be run upon start of a tab with specific profile.
That functionality is missing for dynamic profiles.

Proposed technical implementation details (optional)

Field in profile.json to be able to set up a command that will be run as soon as profile is started. I have no idea how that could be named, tried to think of many, but they do not seem to be catch or self-explanatory. Some examples I thought of are "autorunCommand", "cmdAtStart".
Of course to make it more usable as you cannot make multiple profiles for dynamic profiles, then #3818 should be fixed as well. Then you could have one WSL that is regular, other one to run "sudo su" as a first command to go to elevated WSL instance, and maybe one that will be used as ssh agent by running something like "ssh user@yourFrequentSite.com"

Same parameter and functionality could be useful for other profiles that are not dynamic ones. I have seen some examples of people having multiple PS configuration with (at least seemed to be) ming64 or sys2 options set for the terminal.

Originally created by @krisavi on GitHub (Dec 3, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement When I create a WSL profile manually using WSL.exe command then there is a possibility to modify start command and add to it to make it to start for example ssh session to some specific location I frequently use. Of course it would mean of changing the start command instead of having another parameter that will be run upon start of a tab with specific profile. That functionality is missing for dynamic profiles. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) Field in profile.json to be able to set up a command that will be run as soon as profile is started. I have no idea how that could be named, tried to think of many, but they do not seem to be catch or self-explanatory. Some examples I thought of are "autorunCommand", "cmdAtStart". Of course to make it more usable as you cannot make multiple profiles for dynamic profiles, then #3818 should be fixed as well. Then you could have one WSL that is regular, other one to run "sudo su" as a first command to go to elevated WSL instance, and maybe one that will be used as ssh agent by running something like "ssh user@yourFrequentSite.com" Same parameter and functionality could be useful for other profiles that are not dynamic ones. I have seen some examples of people having multiple PS configuration with (at least seemed to be) ming64 or sys2 options set for the terminal. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-QuestionArea-SettingsResolution-AnsweredProduct-Terminal labels 2026-01-31 00:11:32 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Settings Issue-Question Product-Terminal Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5363
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?