starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Support for Pre-execution Script in Windows Terminal #22941

New Issue
Closed
opened 2026-01-31 08:27:59 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:27:59 +00:00
Owner
Copy Link

Originally created by @marcuwynu23 on GitHub (Feb 19, 2025).

Description of the new feature

🚀 Feature Request: Support for Pre-execution Script in Windows Terminal

✨ Description

It would be beneficial if Windows Terminal supported pre-execution scripts, allowing users to run commands before opening a new terminal session.

🎯 Use Case

  • Users who frequently use doskey for aliasing commands (e.g., doskey gs=git status) have to manually add them to cmd.exe startup scripts.
  • A built-in mechanism to execute predefined scripts when launching Windows Terminal would improve automation and workflow efficiency.

💡 Proposed Solution

  • Add a pre-execution script option in Windows Terminal settings (settings.json).
  • Allow specifying a script (e.g., .cmd, .ps1, .bat) to run before the shell starts.

Example Implementation in settings.json:

{
  "profiles": {
    "defaults": {
      "preExecutionScript": "C:\\path\\to\\myscript.cmd"
    }
  }
}


### Proposed technical implementation details

_No response_
Originally created by @marcuwynu23 on GitHub (Feb 19, 2025). ### Description of the new feature # 🚀 Feature Request: Support for Pre-execution Script in Windows Terminal ## ✨ Description It would be beneficial if Windows Terminal supported **pre-execution scripts**, allowing users to run commands before opening a new terminal session. ## 🎯 Use Case - Users who frequently use `doskey` for aliasing commands (e.g., `doskey gs=git status`) have to manually add them to `cmd.exe` startup scripts. - A built-in mechanism to execute predefined scripts when launching Windows Terminal would improve automation and workflow efficiency. ## 💡 Proposed Solution - Add a **pre-execution script option** in Windows Terminal settings (`settings.json`). - Allow specifying a script (e.g., `.cmd`, `.ps1`, `.bat`) to run **before** the shell starts. ### Example Implementation in `settings.json`: ```json { "profiles": { "defaults": { "preExecutionScript": "C:\\path\\to\\myscript.cmd" } } } ### Proposed technical implementation details _No response_
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 08:27:59 +00:00
claunia commented 2026-01-31 08:28:01 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 19, 2025):

Thanks!

That's actually the purpose of letting you control the commandline of each profile. Because we can't know which shell you're going to use, or whether you're going to be accessing a local or remote machine (like running SSH inside a profile!), there's no way for us to actually run a pre-execution script in the right context in the right scripting language.

For your use case, you should be able to set your commandline to cmd /s /k c:\\path\\to\\myscript.cmd or pwsh -noexit -command c:\\path\\to\\myscript.ps1. :)

@DHowett commented on GitHub (Feb 19, 2025): Thanks! That's actually the purpose of letting you control the commandline of each profile. Because we can't know which shell you're going to use, or whether you're going to be accessing a local or remote machine (like running SSH inside a profile!), there's no way for us to actually _run a pre-execution script_ in the right context in the right scripting language. For your use case, you should be able to set your commandline to `cmd /s /k c:\\path\\to\\myscript.cmd` or `pwsh -noexit -command c:\\path\\to\\myscript.ps1`. :)
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 Issue-Feature Needs-Tag-Fix Needs-Triage
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#22941
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?