starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Terminal Chat AI] Allow company wide disabling this feature #20932

New Issue
Closed
opened 2026-01-31 07:28:10 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 07:28:10 +00:00
Owner
Copy Link

Originally created by @htcfreek on GitHub (Nov 30, 2023).

Description of the new feature/enhancement

Some companies don't allow the usage of AI features or software that has AI feature for privacy reasons.

Please implement a way to centrally force disable this feature.

Proposed technical implementation details (optional)

This can be a policy or HKLM registry value/setting that admins can use to easily disabled this feature for all users.

This setting should work for portable, store and manually installed versions and on all chanels.

Originally created by @htcfreek on GitHub (Nov 30, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Some companies don't allow the usage of AI features or software that has AI feature for privacy reasons. Please implement a way to centrally force disable this feature. # Proposed technical implementation details (optional) This can be a policy or HKLM registry value/setting that admins can use to easily disabled this feature for all users. This setting should work for portable, store and manually installed versions and on all chanels.
claunia added the Issue-TaskNeeds-Tag-FixProduct-TerminalArea-Chat labels 2026-01-31 07:28:10 +00:00
claunia commented 2026-01-31 07:28:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 5, 2023):

Perfectly reasonable ask. I'll link it up to #15000, thanks!

My understanding of GPO is that it can be used to set a reg key, so we can easily query that regardless of what distribution method used.

@zadjii-msft commented on GitHub (Dec 5, 2023): Perfectly reasonable ask. I'll link it up to #15000, thanks! My understanding of GPO is that it can be used to set a reg key, so we can easily query that regardless of what distribution method used.
claunia commented 2026-01-31 07:28:12 +00:00
Author
Owner
Copy Link

@htcfreek commented on GitHub (Dec 6, 2023):

@zadjii-msft
I suggest you to implement a common class where you do the registry reading and that return standardized values like we did in PowerToys (https://github.com/microsoft/PowerToys/blob/main/src/common/utils/gpo.h).

Either you evaluate the Policy ones at application startup or every time the settings window and chat window gets opened.

The default expected behavior of policies is that computer scope has a higher priority than user scoope. And that you are able to set it either in user or in computer scope.

I think the category in the ADMX file should be Microsoft\Windows Components\Windows Terminal. The Registry key can be Software\Policies\Microsoft\Windows Terminal or Software\Policies\Microsoft\Windows\Terminal.

@htcfreek commented on GitHub (Dec 6, 2023): @zadjii-msft I suggest you to implement a common class where you do the registry reading and that return standardized values like we did in PowerToys (https://github.com/microsoft/PowerToys/blob/main/src/common/utils/gpo.h). Either you evaluate the Policy ones at application startup or every time the settings window and chat window gets opened. The default expected behavior of policies is that computer scope has a higher priority than user scoope. And that you are able to set it either in user or in computer scope. I think the category in the ADMX file should be `Microsoft\Windows Components\Windows Terminal`. The Registry key can be `Software\Policies\Microsoft\Windows Terminal` or `Software\Policies\Microsoft\Windows\Terminal`.
claunia commented 2026-01-31 07:28:13 +00:00
Author
Owner
Copy Link

@g0t4 commented on GitHub (Dec 7, 2023):

Given the current setup process requires custom azure resources, isn't that sufficient for an approval process at least short term?

@g0t4 commented on GitHub (Dec 7, 2023): Given the current setup process requires custom azure resources, isn't that sufficient for an approval process at least short term?
claunia commented 2026-01-31 07:28:14 +00:00
Author
Owner
Copy Link

@htcfreek commented on GitHub (Dec 7, 2023):

Given the current setup process requires custom azure resources, isn't that sufficient for an approval process at least short term?

I thought everyone is able to create such an required account including private persons. Is that wrong? Don't know about this.

If I require a special company account/license/configuration then it should be enough for short term.

@htcfreek commented on GitHub (Dec 7, 2023): > Given the current setup process requires custom azure resources, isn't that sufficient for an approval process at least short term? I thought everyone is able to create such an required account including private persons. Is that wrong? Don't know about this. If I require a special company account/license/configuration then it should be enough for short term.
claunia commented 2026-01-31 07:28:14 +00:00
Author
Owner
Copy Link

@htcfreek commented on GitHub (Oct 8, 2024):

@DHowett , @lhecker
This is similar to #17964.

@ilhacker, i mistakenly mentioned you.

@htcfreek commented on GitHub (Oct 8, 2024): @DHowett , @lhecker This is similar to #17964. --- _@ilhacker, i mistakenly mentioned you._
claunia commented 2026-01-31 07:28:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 21, 2024):

@PankajBhojwani Double check me - this was resolved by #18095, but since that PR wasn't into main, GitHub just didn't auto-close the issue, yea?

@zadjii-msft commented on GitHub (Nov 21, 2024): @PankajBhojwani Double check me - this was resolved by #18095, but since that PR wasn't into `main`, GitHub just didn't auto-close the issue, yea?
claunia commented 2026-01-31 07:28:15 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Nov 21, 2024):

This was resolved by #18095 yep, not entirely sure why the bot didn't close it but I'll close it manually now

@PankajBhojwani commented on GitHub (Nov 21, 2024): This was resolved by #18095 yep, not entirely sure why the bot didn't close it but I'll close it manually now
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-Chat Issue-Task Needs-Tag-Fix Product-Terminal
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#20932
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?