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

Support xdg-open / open with browser for SSH terminals #18814

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

Originally created by @misterjoshua on GitHub (Nov 3, 2022).

Description of the new feature/enhancement

I want Windows Terminal to support opening a browser over SSH as VS Code does. This is useful for tools that want the user to open a browser to a given website, such as for authorizing a device or authenticating via SSO.

For instance, we use Granted to access our cloud accounts. Granted comes with a tool called assume that helps get access credentials. After running assume, the tool takes me to a device authorization endpoint and my company's SSO where I can authorize the session via my desktop browser. After authorizing by browser, the tool completes the device authorization process and I am logged into the cloud with short-lived credentials.

Example

In Windows Terminal, I get the error output shown and I need to ctrl-click to open the URL:

image

But in VS Code, the browser opens on my desktop right away, saving me some time:

image

The tool above uses FreeDesktop's well-known xdg-open tool. When I run xdg-open manually, I get substantially similar error messages:

image

But the tool works fine in VS Code:

image

Proposed technical implementation details (optional)

I'm not sure how this would be implemented in Windows Terminal, but I suspect that you could look at how VS Code is doing it for some hints on how this could work.

Originally created by @misterjoshua on GitHub (Nov 3, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 I want Windows Terminal to support opening a browser over SSH as VS Code does. This is useful for tools that want the user to open a browser to a given website, such as for authorizing a device or authenticating via SSO. For instance, we use [Granted](https://granted.dev/) to access our cloud accounts. Granted comes with a tool called `assume` that helps get access credentials. After running `assume`, the tool takes me to a device authorization endpoint and my company's SSO where I can authorize the session via my desktop browser. After authorizing by browser, the tool completes the device authorization process and I am logged into the cloud with short-lived credentials. **Example** In Windows Terminal, I get the error output shown and I need to ctrl-click to open the URL: ![image](https://user-images.githubusercontent.com/644092/199789860-4b71e1c3-543e-42ca-8b4f-291711401a83.png) But in VS Code, the browser opens on my desktop right away, saving me some time: ![image](https://user-images.githubusercontent.com/644092/199790071-2ad10925-b03f-4c4c-b8f8-dbd21e67614c.png) The tool above uses FreeDesktop's well-known `xdg-open` tool. When I run xdg-open manually, I get substantially similar error messages: ![image](https://user-images.githubusercontent.com/644092/199790400-95c06561-13d1-42ca-ba06-39a3f88aab05.png) But the tool works fine in VS Code: ![image](https://user-images.githubusercontent.com/644092/199790490-7822ed73-2aeb-4ecd-9368-b9999c9f4ec4.png) <!-- 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) I'm not sure how this would be implemented in Windows Terminal, but I suspect that you could look at how VS Code is doing it for some hints on how this could work. <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureNeeds-Tag-FixProduct-TerminalArea-Extensibility labels 2026-01-31 06:25:14 +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-Extensibility Issue-Feature 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#18814
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?