github / github/copilot-cli

pasting issue

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

Nobody has claimed this yet.

triage
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

Describe the bug

Bug: Pasted multi-line content not sent to model

Environment: WezTerm (Ctrl+V →  PasteFrom "Clipboard" ) on Windows, running Copilot CLI inside WSL (zsh). CLI version 1.0.80.

Expected: The full pasted content (12 lines) is sent to the model as part of the message.

Actual: The model responds as if no content was received — e.g., "I don't see the pasted content — it looks like it didn't come through." The paste token is not being expanded/substituted with the real content before the request is sent.

Notes: Terminal/paste mechanism itself works correctly (bracketed paste, WezTerm config verified clean) — this appears to be a CLI-side bug in how paste tokens are resolved before submission.

Affected version

GitHub Copilot CLI 1.0.80.

Steps to reproduce the behavior

Steps to reproduce:
in wezterm using wsl,

  1. Copy multi-line text (e.g., 12 lines) to clipboard.
  2. Prompt correctly shows a collapsed token:  [Paste #1 - 12 lines] .
  3. Press Enter to submit.
Expected behavior

No response

Additional context

No response

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.

Research direction

Reproduce in WezTerm on Windows with Copilot CLI inside WSL using zsh, copying 12 lines and submitting the collapsed [Paste #1] token. No source file or test is named, so trace the paste-token handling from prompt submission to the model request. Done means the full pasted content is included in the submitted message.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.