jupyterlab_terminal_clipboard_extension
v1.0.7
Published
Jupyterlab extension to handle copy to clipboard actions in a terminal to allow copy to clipboard of the browser/user
Maintainers
Readme
jupyterlab_terminal_clipboard_extension
[!TIP] This extension is part of the stellars_jupyterlab_extensions metapackage. Install all Stellars extensions at once:
pip install stellars_jupyterlab_extensions
Terminal programs running inside JupyterLab normally cannot copy anything to your clipboard. Tools like password managers, vim, tmux, and other TUI applications that rely on xclip or xsel fail silently because there is no X11 display in a browser-based terminal. This extension fixes that - when a terminal program copies something, it lands in your browser clipboard so you can paste it anywhere.
Features
- OSC 52 clipboard interception - captures clipboard escape sequences from terminal output
- Auto-installing shims - deploys
xclip,xsel,wl-copyreplacements to~/.local/bin/on startup when real tools are not functional (no display server) - Non-destructive install - only installs shims when the real tools cannot work, and never overwrites a clipboard tool it did not create
Installation
Requires JupyterLab 4.0.0 or higher.
pip install jupyterlab_terminal_clipboard_extensionEnsure ~/.local/bin is in your PATH for the shims to work:
export PATH="$HOME/.local/bin:$PATH"Uninstall
pip uninstall jupyterlab_terminal_clipboard_extensionTechnical Details
The extension has two components. The frontend plugin registers an OSC 52 parser handler on each terminal's xterm.js instance. When a terminal application writes \033]52;c;<base64>\a, the handler decodes the payload and writes it to the browser clipboard via navigator.clipboard.writeText() with a document.execCommand('copy') fallback for HTTP (non-secure) contexts.
The server plugin runs on JupyterLab startup and installs lightweight POSIX shell shims into ~/.local/bin/. These shims replace xclip, xsel, and wl-copy - the system clipboard tools that terminal programs call. Instead of talking to an X11 display, the shims base64-encode the input and emit an OSC 52 escape sequence to /dev/tty, which the frontend plugin then intercepts.
terminal app -> xclip/xsel (shim) -> OSC 52 escape sequence -> extension -> browser clipboardShims are only installed when the real tools cannot function (no DISPLAY or WAYLAND_DISPLAY environment variable set). If a real X11 or Wayland clipboard is available, the shims are not deployed and the original tools are preserved. An existing file in ~/.local/bin that is not one of our shims is never overwritten - the installer logs a warning and skips it, so a clipboard tool you placed there yourself stays intact.
Because OSC 52 only reaches the browser through the terminal, the shims write the escape sequence exclusively to /dev/tty. When a program calls them without a controlling terminal, they exit non-zero with a message on stderr rather than emitting the sequence to stdout, where it would corrupt the caller's output.
