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

Feature Request: Logging Input and Output for Each Terminal Tab Automatically #22723

New Issue
Closed
opened 2026-01-31 08:21:35 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:21:35 +00:00
Owner
Copy Link

Originally created by @lededev on GitHub (Jan 2, 2025).

Description: I would like to request a feature that allows logging of input and output for each terminal tab in Windows Terminal automatically (Not export text manually, Because I often remember to review the terminal output only after I close the tab or the entire terminal program). This feature would be similar to the logging functionality available in mintty, where logs can be configured in the configuration file (e.g., ~/.minttyrc with Log=/var/log/mintty/%Y%m%d@%H:%M:%S_log%d.txt).

Use Case: This feature would be extremely useful for users who need to keep a record of their terminal sessions for auditing, debugging, or documentation purposes. It would be beneficial for various types of terminals, including PowerShell, CMD, WSL, and MSYS2.

Proposed Solution: Implement a logging feature that can be configured in the Windows Terminal settings, allowing users to specify the log file path and format. The logs should include both input and output for each terminal tab.

Additional Context: Currently, users have to rely on external tools and scripts to achieve this functionality. Having this feature built into Windows Terminal would greatly enhance its usability and convenience.

Originally created by @lededev on GitHub (Jan 2, 2025). Description: I would like to request a feature that allows logging of input and output for each terminal tab in Windows Terminal automatically (Not export text manually, Because I often remember to review the terminal output only after I close the tab or the entire terminal program). This feature would be similar to the logging functionality available in mintty, where logs can be configured in the configuration file (e.g., ~/.minttyrc with Log=/var/log/mintty/%Y%m%d@%H:%M:%S_log%d.txt). Use Case: This feature would be extremely useful for users who need to keep a record of their terminal sessions for auditing, debugging, or documentation purposes. It would be beneficial for various types of terminals, including PowerShell, CMD, WSL, and MSYS2. Proposed Solution: Implement a logging feature that can be configured in the Windows Terminal settings, allowing users to specify the log file path and format. The logs should include both input and output for each terminal tab. Additional Context: Currently, users have to rely on external tools and scripts to achieve this functionality. Having this feature built into Windows Terminal would greatly enhance its usability and convenience.
claunia added the Resolution-Duplicate label 2026-01-31 08:21:35 +00:00
claunia commented 2026-01-31 08:21:36 +00:00
Author
Owner
Copy Link

@83nf15h commented on GitHub (Mar 1, 2025):

#14018 and #9700 are looking for a similar feature but have had no progress in a long time. Would be great to have this included.

@83nf15h commented on GitHub (Mar 1, 2025): #14018 and #9700 are looking for a similar feature but have had no progress in a long time. Would be great to have this included.
claunia commented 2026-01-31 08:21:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 27, 2025):

Yep, those are definitely the right dupes. Thanks!

/dup #14018

@zadjii-msft commented on GitHub (Mar 27, 2025): Yep, those are definitely the right dupes. Thanks! /dup #14018
claunia commented 2026-01-31 08:21:37 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Mar 27, 2025):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Mar 27, 2025): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Resolution-Duplicate
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#22723
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?