github / github/copilot-cli

[Bug] Cannot copy Copilot CLI output to clipboard in VSCode Server (browser-based remote environment)

Open
#3,996 0 comments 0 reactions 0 assignees View on GitHub
area:terminal-rendering
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

# [Bug] Cannot copy Copilot CLI output to clipboard in VSCode Server (browser-based remote environment)

## Summary

When using GitHub Copilot CLI inside a **VSCode Server** environment (web-based, accessed via browser), the "copy to clipboard" functionality silently fails. There is no fallback, no error message, and no way to retrieve the output that was supposed to be copied.

---

## Environment

| Item | Value |
|---|---|
| OS | Ubuntu 22.04.4 LTS |
| VSCode Server | Web-based (`--host 0.0.0.0 --port 8080`, no GUI) |
| Terminal | tmux inside VSCode Server integrated terminal |
| `$DISPLAY` | *(empty — no X11 server)* |
| `$WAYLAND_DISPLAY` | *(empty — no Wayland compositor)* |
| `xclip` | not found |
| `xsel` | not found |
| `wl-copy` | not found |
| `pbcopy` | not found (Linux) |
| TTY | `not a tty` |
| Copilot CLI version | 1.0.67 |

Relevant environment variables confirming VSCode Server context:
```
VSCODE_IPC_HOOK_CLI=/tmp/vscode-ipc-*.sock
TERM_PROGRAM=tmux
BROWSER=/usr/lib/vscode-server/bin/helpers/browser.sh
ENTRYPOINT=vscode-server --host 0.0.0.0 --port 8080 --without-connection-token
```

---

## Steps to Reproduce

1. Connect to a remote machine running **VSCode Server** via browser (e.g., `http://:8080`).
2. Open an integrated terminal (which runs inside a tmux/screen session without a display server).
3. Use GitHub Copilot CLI and trigger any action that copies output to clipboard (e.g., accepting a suggested command).
4. Attempt to paste anywhere — clipboard is empty.

---

## Expected Behavior

One of the following should happen:

**make copy avaliable**

In the same env, codex does;

---

## Actual Behavior

The clipboard copy action **silently fails**. No output is printed, no warning is shown. The user has no way to access the content that was supposed to be copied.

---

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the clipboard failure in the documented VSCode Server, integrated-terminal, and tmux environment, then trace the CLI's copy action and its handling when no display or clipboard utility is available. Done means the output is copyable or a clear fallback or error makes it retrievable instead of failing silently.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell, vscode
Domain
cli, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.