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

Add MOSH support like in fluent terminal #13709

New Issue
Closed
opened 2026-01-31 03:49:59 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 03:49:59 +00:00
Owner
Copy Link

Originally created by @Luk164 on GitHub (May 2, 2021).

Description of the new feature/enhancement

Simmilar to fluent terminal, support for MOSH (https://mosh.org/) could be useful to some. For example in case of a connection loss it is able to reconnect, which is quite useful for when your connection is spotty. This is already implemented in fluent terminal (https://github.com/felixse/FluentTerminal)

Originally created by @Luk164 on GitHub (May 2, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Simmilar to fluent terminal, support for MOSH (https://mosh.org/) could be useful to some. For example in case of a connection loss it is able to reconnect, which is quite useful for when your connection is spotty. This is already implemented in fluent terminal (https://github.com/felixse/FluentTerminal)
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 03:50:00 +00:00
claunia commented 2026-01-31 03:50:02 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (May 3, 2021):

MOSH and Fluent Terminal are licensed with GNU GPL so I don't think Microsoft is going to copy anything from these existing implementations to Windows Terminal. The MOSH source repository mentions a GPL-specific patent license for OCB encryption so reimplementing the protocol might require paying the patent holder. I think the most feasible way to enable MOSH in Windows Terminal is if somebody ports the MOSH code to Windows and it then runs as a separate process without Windows Terminal explicitly supporting it.

@KalleOlaviNiemitalo commented on GitHub (May 3, 2021): MOSH and Fluent Terminal are licensed with GNU GPL so I don't think Microsoft is going to copy anything from these existing implementations to Windows Terminal. The MOSH source repository mentions a GPL-specific patent license for OCB encryption so reimplementing the protocol might require paying the patent holder. I think the most feasible way to enable MOSH in Windows Terminal is if somebody ports the MOSH code to Windows and it then runs as a separate process without Windows Terminal explicitly supporting it.
claunia commented 2026-01-31 03:50:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 3, 2021):

Also, mosh is just a shell, so I don't see why we'd need to build it directly into the Terminal. I bet you could get it working perfectly fine with WSL.

@zadjii-msft commented on GitHub (May 3, 2021): Also, `mosh` is just a shell, so I don't see why we'd need to build it directly into the Terminal. I bet you could get it working perfectly fine with WSL.
claunia commented 2026-01-31 03:50:02 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 3, 2021):

@zadjii-msft in this case MOSH is actually another terminal emulator like tmux/screen. It should work fine through WSL 😄

@DHowett commented on GitHub (May 3, 2021): @zadjii-msft in this case MOSH is actually _another terminal emulator_ like tmux/screen. It should work fine through WSL :smile:
claunia commented 2026-01-31 03:50:03 +00:00
Author
Owner
Copy Link

@aress31 commented on GitHub (Jul 23, 2021):

+1

@aress31 commented on GitHub (Jul 23, 2021): +1
claunia commented 2026-01-31 03:50:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 23, 2021):

@aress31 If you'd like to "+1" this feature, the best way to do that is by hitting the 👍 button on this issue

image

That way, you avoid unnecessarily pinging everyone following this thread. Thanks!

@zadjii-msft commented on GitHub (Jul 23, 2021): @aress31 If you'd like to "+1" this feature, the best way to do that is by hitting the 👍 button on this issue ![image](https://user-images.githubusercontent.com/18356694/96140789-ef3c8880-0ec5-11eb-82e0-30ce4977b9a7.png) That way, you avoid unnecessarily pinging everyone following this thread. Thanks!
claunia commented 2026-01-31 03:50:03 +00:00
Author
Owner
Copy Link

@altano commented on GitHub (Feb 5, 2022):

I’m sad this got closed. Recommending WSL just to get persistent ssh connections seems like a bit of a heavy hammer. For example, WSL doesn’t by default even share your ssh keys and config so you have to keep the two in sync (https://devblogs.microsoft.com/commandline/sharing-ssh-keys-between-windows-and-wsl-2/).

Is Windows Terminal not going to add things that you can get by using WSL in general or just this case?

@altano commented on GitHub (Feb 5, 2022): I’m sad this got closed. Recommending WSL just to get persistent ssh connections seems like a bit of a heavy hammer. For example, WSL doesn’t by default even share your ssh keys and config so you have to keep the two in sync (https://devblogs.microsoft.com/commandline/sharing-ssh-keys-between-windows-and-wsl-2/). Is Windows Terminal not going to add things that you can get by using WSL in general or just this case?
claunia commented 2026-01-31 03:50:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 6, 2022):

I don't believe there's anything for us to do here. The Terminal is perfectly capable of running mosh. It's not something that needs to be built-in to the Terminal at all. Unless I'm misunderstanding things. It doesn't look like there's a native mosh.exe available for Windows, that's something you should ask the maintainer of mosh to support. The terminal emulation should be more than sufficient by now ☺️

@zadjii-msft commented on GitHub (Feb 6, 2022): I don't believe there's anything for us to do here. The Terminal is perfectly capable of running mosh. It's not something that needs to be built-in to the Terminal at all. Unless I'm misunderstanding things. It doesn't look like there's a native `mosh.exe` available for Windows, that's something you should ask the maintainer of mosh to support. The terminal emulation should be more than sufficient by now ☺️
claunia commented 2026-01-31 03:50:04 +00:00
Author
Owner
Copy Link

@Tamnac commented on GitHub (Dec 21, 2025):

Asking for WSL just to run mosh is absurd. I push to re open this issue

@Tamnac commented on GitHub (Dec 21, 2025): Asking for WSL just to run mosh is absurd. I push to re open this issue
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#13709
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?