Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support copying to system clipboard via OSC52 escape sequence

Open
#4,943 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, powershell
Domain
cli

Research direction

Start by reviewing the CopyOrCancelLine key handler and the existing copy-related implementation; no specific files or tests are named in the issue. Compare the requested behavior with Set-Clipboard's -AsOSC52 implementation. Done means providing an OSC52-based way to copy selected text in the remote scenarios described, either through CopyOrCancelLine or an alternative key handler.

Written by the indexing model from the issue text.

Description

Issue-Enhancement Needs-Triage :mag:
Prerequisites
  • Write a descriptive title.
Description of the new feature/enhancement

It's really useful to be able to copy highlighted text to the system clipboard using ctrl+c (CopyOrCancelLine). This works without a hitch using the shell locally, and when using PowerShell remoting to connect to another computer, but not in certain other circumstances - say, if I remoted into another system using ssh and ran PowerShell there, ctrl+c doesn't copy to my system clipboard, which is really unfortunate.
Some of the situations it doesn't handle could be solved by adding either an option or another key handler that copies the selection using the OSC52 escape sequence.

Proposed technical implementation details (optional)

I would be satisfied with either an option to change Copy and equivalents to copy using OSC52 escape sequences or alternative keyhandlers that function like Copy etc. but use OSC52 copying. Set-Clipboard supports this; its implementation might be a useful reference?

Dominant language
C#
Stars
4.4k
Forks
341
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PowerShell/PSReadLine

All issues in PowerShell/PSReadLine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.