Prompt is not submitted to terminal. Cannot paste directly into terminal.

[neil-gh]

I appreciate your extension. Thanks in advance for any assistance with this issue.

This is a new issue. The extension was working fine until around 2026-04-18.
At the same time I noticed this issue, I also noticed my auto-selected Claude Code model was Opus 4.7 instead of 4.6. So I don't know if this issue is related to a Claude update but thought I would mention.

ISSUES:

1. Prompts no longer make it to the extension's integrated terminal below the prompt when the prompt is submitted.
   • This means my only option for using the extension is to type in the integrated terminal directly, where I quickly noticed:
2. I cannot paste into the integrated terminal
   • i.e. Ctrl+V, Shift+Insert, Ctrl+Shift+V: None of these will paste into the terminal
   • I can't promise you this ever worked because I normally used the prompt field. But I think this worked before, and I think it stopped working at the same time as the prompt issue.

REPRO:

1. Versions of things I'm running:
   • Visual Studio 2026: 18.4.2
   • Claude Code Extension for Visual Studio: 10.13
   • Claude Code: v2.1.117 (I believe I was on v2.1.116 when this started)
2. In Visual Studio > my Claude Code tab is pinned to the right pane, alongside Solution Explorer and Git Changes. Terminal is not detached to separate tab > [x] Send with Enter is enabled
3. Enter some text in the Prompt / Paste Image field > Ctrl+A then Ctrl+C to copy the text, because you're going to lose it
4. Hit Enter
5. The text goes away as if it submitted > then nothing happens in the terminal
6. Focus the integrated terminal prompt > type "Hello?" to see if Claude is alive > Claude is alive and responds
7. Try to paste your copied text into the integrated terminal prompt > observe it does not work; nothing happens

SEVERITY:
The extension is currently almost unusable. I can do very basic things using the extension terminal, but I've been shocked to learn how crippling it is not to be able to paste in a prompt. I am constantly needing to paste in prompts -- file paths, code snippets, PR comments, work item descriptions, etc. A few times I have resorted to composing my prompt in a text doc, then I have to save it, then I can type in extension terminal to read my prompt file, but then I have to type the file path because I can't paste it. I have since learned of Claude Code's Ctrl+G shortcut which opens prompt in text editor -- and eliminates some of those steps (like saving the file and typing the file path), but it's still a lot of friction.

THINGS I'VE TRIED:
I lost count. Relaunched Visual Studio. Rebooted computer. Confirmed regular Claude Code is working normally, and I can paste, in Windows Terminal (PowerShell) in an active Claude Code session. Toggled Send with Enter. Reloaded agent. Updated agent. Confirmed coworker is having the same issues (although I believe he can paste in the extension's terminal using Ctrl+Shift+V only). Combed through VS > Customize > Keyboard looking for keyboard shortcut conflicts with Ctrl+Shift+V > deleted all of those except Terminal.Paste because it sounds like the one I need > still can't paste in extension terminal. Confirmed I can paste in native VS terminal (Developer PowerShell 7) in an active Claude Code session (using all 3 of the keyboard shortcuts). Googled a lot > read a lot of community posts and Anthropic Github issues (to no avail). Asked Claude to help me solve (to no avail). Probably some other stuff I'm forgetting.

[dliedke]

Hello, sorry about the bad experience. I can't reproduce this issue here.

Is the mouse going automatically to the center of the claude code terminal?

Did you cloned code and tried debugging it?

[dliedke]

The extension will do the following:

0. User enter prompt in prompt area

1. Copy to clipboard the content of prompt area

2. Move mouse to middle of terminal area

3. Right-click to paste the content

Try these steps manually to see if it works in your environment. Also check if extension is doing any of that.

Also, you may use CTRL+UP to access prompt history in case prompt is lost and not sent to extension.

[dliedke]

I will ask Claude Code if it has any ideas.

[dliedke]

Got enough context. Ideas below.

Likely causes (ranked)
1. Elevation mismatch (top suspect). VS 2026 running as Admin while clipboard owner (browser/Outlook) isn't — or reverse. UIPI blocks
SendInput/keybd_event/clipboard access across integrity levels. Explains both symptoms: extension paste silently drops AND user's own Ctrl+V can fail if terminal is elevated but keyboard source isn't (or reverse).

2. Windows Terminal multiLinePasteWarning / largePasteWarning. Recent WT versions block multiline paste by default. User sees nothing
   happen. Extension PasteViaCtrlShiftVAsync hits same wall. Check
   %LocalAppData%\Packages\Microsoft.WindowsTerminal_*\LocalState\settings.json.

3. VS 2026 18.4.2 preview regression. Child-window input queue attachment changed. SetParent cross-process reparent may route input
   differently in 18.4. Ask: reproduces in VS 2022?

4. 3rd-party clipboard/keyboard tool holding clipboard or hooking Ctrl+V. Ditto, ClipClip, ClipboardFusion, PowerToys Keyboard Manager,
   AutoHotkey. Globals hooks can swallow Ctrl+V/Ctrl+Shift+V. SaveClipboardContent → Clear → SetText races against clipboard chain
   listeners.

5. Settings file corruption. IsTerminalDetached=true with no visible detached window, or stale SelectedTerminalType. Paste/Enter goes to
   wrong HWND. Fix: delete %LocalAppData%\ClaudeCodeExtension\claudecode-settings.json.

6. AV/EDR synthetic-input block. Defender ASR, Crowdstrike, S1 can block simulated keyboard events from signed VS processes.

7. Claude Code 2.1.117 TUI change. New bracketed-paste or mouse-reporting mode. Extension sends WM_CHAR Enter (line 602 TerminalIO) — if
   CC now needs different delivery, prompt lands but Enter never submits. User wouldn't see input at all though — less likely.

8. Windows 11 Clipboard History (Win+V) lock. Service holds clipboard during snapshot → Clipboard.SetText fails → silent (since
   ClipboardRetry only catches COM 0x800401D0, not timeouts).

Diagnostic asks for reporter

• winver output (Windows build)?
• VS running as admin? Run whoami /groups | findstr S-1-16 or Task Manager → VS row → "Elevated" column.
• Terminal type — CMD or Windows Terminal? (right-click ⋯ menu → Settings). Does switching change behavior?
• All providers broken or only one?
• Happens on fresh VS start or only after N prompts?
• Background tools: PowerToys, AHK, Ditto, Crowdstrike, Defender ASR rules?
• Delete %LocalAppData%\ClaudeCodeExtension\claudecode-settings.json, restart VS — fix?
• Disable "Send with Enter", use button manually — same?
• Reproduces on VS 2022 (not 2026 preview)?
• DebugView++ log filtered on claude while reproducing — any exceptions?
• Does direct paste work if they right-click the terminal with mouse instead of Ctrl+V?

Quickest user workarounds to suggest

• Run VS non-elevated (or fully elevated — match the origin)
• Switch terminal type to Command Prompt
• Disable clipboard managers temporarily
• Delete extension settings file
• Test with VS 2022 to isolate 2026 preview

✻ Cooked for 2m 22s

[dliedke]

I cannot paste into the integrated terminal
i.e. Ctrl+V, Shift+Insert, Ctrl+Shift+V: None of these will paste into the terminal

For me only right-click with mouse will paste in regular Claude Code in cmd outside VS.NET

[neil-gh]

Thanks for the reply. Below I have converted your questions and Claude Code's questions to numbered lists. My responses are indented bullets.

I also checked Windows Update History. I did not find anything relevant. I had 1 .NET 8 security update today (4 days after onset of issue), and the previous update was 2026-03-31 (a couple weeks before onset of issue).

---

Daniel's Questions

1. Is the mouse going automatically to the center of the claude code terminal?
   • The mouse does not appear to be moving. I click in the extension prompt field > I get a prompt cursor > I "park" my mouse pointer 1 inch below the cursor > as soon as I start typing the mouse pointer hides > I type "Hello?" > hit Enter. Then, in this sequence, and with very roughly estimated "how long before this happens" durations: the prompt cursor appears (50ms) > my mouse pointer appears right where I parked it (100ms) > my prompt text disappears (1000ms) > nothing else happens. Note that the 1 second delay before the text disappears is slower than before this issue started happening; it's one of the first anomalies I noticed.
2. Did you cloned code and tried debugging it?
   • I have not. I may be able to explore this at some point if I have time.
3. The extension will do the following: 0. User enter prompt in prompt area, 1. Copy to clipboard the content of prompt area, 2. Move mouse to middle of terminal area, 3. Right-click to paste the content. Try these steps manually to see if it works in your environment.
   • I repro'd these steps > right-click to paste in terminal does nothing.
4. Also check if extension is doing any of that.
   • If by "check" you mean: observe --> then the extension is not doing any of that. If by "check" you mean something else, like check some logs or clone repo and debug + step-through --> then please clarify.
5. For me only right-click with mouse will paste in regular Claude Code in cmd outside VS.NET
   • That's very interesting. I just tested and, for me, it is the exact opposite. Windows Terminal > CMD > Claude Code: Ctrl+V, Ctrl+Shift+V, Shift+Insert will all paste, but right-click will not. Windows Terminal > PowerShell > Claude Code: Exact same results. Note that right-click in CMD and PowerShell without a Claude Code session active will paste.

Claude Code: Likely causes (ranked)

1. Elevation mismatch (top suspect). VS 2026 running as Admin while clipboard owner (browser/Outlook) isn't — or reverse. UIPI blocks SendInput/keybd_event/clipboard access across integrity levels. Explains both symptoms: extension paste silently drops AND user's own Ctrl+V can fail if terminal is elevated but keyboard source isn't (or reverse).
   • Not sure about this one, but I did close all other apps and test my normal path (VS 2026 running as admin). Same failure mode.
2. Windows Terminal multiLinePasteWarning / largePasteWarning. Recent WT versions block multiline paste by default. User sees nothing happen. Extension PasteViaCtrlShiftVAsync hits same wall. Check %LocalAppData%\Packages\Microsoft.WindowsTerminal_*\LocalState\settings.json.
   • I checked my settings.json. I did not find any of the settings keys mentioned. Ctrl+F > paste only yields this one: "id": "Terminal.PasteFromClipboard", "keys": "ctrl+v"
   • Also note that I have done most of my testing with single-line prompts like hello? and test1.
3. VS 2026 18.4.2 preview regression. Child-window input queue attachment changed. SetParent cross-process reparent may route input differently in 18.4. Ask: reproduces in VS 2022?
   • FYI VS 2026 18.4.2 is not a preview release. About VS lists the Channel: as Stable. Yes, the issue repros in VS 2022. Exact same failure mode.
4. 3rd-party clipboard/keyboard tool holding clipboard or hooking Ctrl+V. Ditto, ClipClip, ClipboardFusion, PowerToys Keyboard Manager, AutoHotkey. Globals hooks can swallow Ctrl+V/Ctrl+Shift+V. SaveClipboardContent → Clear → SetText races against clipboard chain listeners.
   • I do not have any 3rd party clipboard managers installed. No PowerToys, no AHK.
5. Settings file corruption. IsTerminalDetached=true with no visible detached window, or stale SelectedTerminalType. Paste/Enter goes to wrong HWND. Fix: delete %LocalAppData%\ClaudeCodeExtension\claudecode-settings.json.
   • I closed VS and Windows Terminal > renamed claudecode-settings.json to _claudecode-settings.json > launched VS 2026 as admin > exact same failure mode > verified a new claudecode-settings.json had been created > closed VS > restored original claudecode-settings.json file.
6. AV/EDR synthetic-input block. Defender ASR, Crowdstrike, S1 can block simulated keyboard events from signed VS processes.
   • Unfamiliar with those, but I don't have any of them installed.
7. Claude Code 2.1.117 TUI change. New bracketed-paste or mouse-reporting mode. Extension sends WM_CHAR Enter (line 602 TerminalIO) — if CC now needs different delivery, prompt lands but Enter never submits. User wouldn't see input at all though — less likely.
   • No actionable request here. I will mention that my Claude Code version has jumped to 2.1.118 since I started testing and have relaunched relevant apps multiple times.
8. Windows 11 Clipboard History (Win+V) lock. Service holds clipboard during snapshot → Clipboard.SetText fails → silent (since ClipboardRetry only catches COM 0x800401D0, not timeouts).
   • No actionable request here.

Claude Code: Diagnostic asks for reporter

1. winver output (Windows build)?
   • W11 Version 25H2 (OS Build 26200.8037)
2. VS running as admin? Run whoami /groups | findstr S-1-16 or Task Manager → VS row → "Elevated" column.
   • Yes, I am running VS as admin. Also tested running non-elevated; as mentioned in workarounds below.
3. Terminal type — CMD or Windows Terminal? (right-click ⋯ menu → Settings). Does switching change behavior?
   • I will try this tomorrow & report back
4. All providers broken or only one?
   • I will try this tomorrow & report back
5. Happens on fresh VS start or only after N prompts?
   • On fresh VS start and all prompts after. Happens always.
6. Background tools: PowerToys, AHK, Ditto, Crowdstrike, Defender ASR rules?
   • No
7. Delete %LocalAppData%\ClaudeCodeExtension\claudecode-settings.json, restart VS — fix?
   • Done. Did not fix.
8. Disable "Send with Enter", use button manually — same?
   • Same failure mode
9. Reproduces on VS 2022 (not 2026 preview)?
   • Yes, same failure mode on VS 2022 and VS 2026. Note that CC is incorrect --> VS 2026 18.4.2 is a stable channel release, not a preview.
10. DebugView++ log filtered on claude while reproducing — any exceptions?
    • Have not tried. Skipping for now. May be able to try later if needed.
11. Does direct paste work if they right-click the terminal with mouse instead of Ctrl+V?
    • In VS > Claude Code Extension terminal: No
    • In Windows Terminal > PowerShell or CMD > CC session: No
    • In Windows Terminal > PowerShell or CMD > not in a CC session: Yes

Claude Code: Quickest user workarounds to suggest

1. Run VS non-elevated (or fully elevated — match the origin)
   • I do run VS as admin (required for our solutions). I ran VS 2022 and VS 2026 non-elevated for testing > same failure mode for both.
2. Switch terminal type to Command Prompt
   • I will try this tomorrow & report back
3. Disable clipboard managers temporarily
   • No 3rd party clipboard managers installed
4. Delete extension settings file
   • Tried this. Same failure mode.
5. Test with VS 2022 to isolate 2026 preview
   • Tested in both. Same failure mode in both.

[dliedke]

I will will need for you to debug more or just give up. I can't reproduce it and no other user reported this issue.

Review from Claude Opus 4.7 Max effort:

Likely Root Cause

Claude Code v2.1.116 activated Kitty keyboard protocol on Windows Terminal. Extension embeds WT via SetParent() →
child-window state breaks Kitty protocol input/paste pipeline.

Evidence Chain

1. Claude Code v2.1.116 changelog: "Fixed Ctrl+- not triggering undo in terminals using the Kitty keyboard protocol
   (iTerm2, Ghostty, kitty, WezTerm, Windows Terminal)" — confirms WT Kitty protocol is actively used.
2. Upstream bug pattern matches — issue [BUG] Kitty keyboard protocol sequences display as literal '<' and '<%' in JetBrains JediTerm (IntelliJ/WebStorm) anthropics/claude-code#48212: same failure in JetBrains
   JediTerm (another IDE-embedded terminal). Kitty init sequences (CSI >0q XTVERSION, CSI c DA1) leak/misbehave in non-host
   terminals.
3. Issue #50531: Windows Terminal + Claude Code, same Kitty protocol + DECCKM state corruption — Claude Code enables CSI
   ? 1 h (DECCKM), CSI = flags ; 1 u (Kitty KP), bracketed paste, alt screen, mouse tracking — and cleanup is incomplete.
   Embedded WT inherits dirty state.
4. User symptoms match: Paste + Enter fail on embedded terminal only. Native WT paste works → state-propagation issue,
   not clipboard/P-Invoke bug in TerminalIO.cs.

Why Extension's Paste Breaks

SendTextToTerminalAsync (ClaudeCodeControl.TerminalIO.cs:60) does: right-click paste → SendEnterKey() via
WM_CHAR(VK_RETURN). When Claude Code enabled Kitty KP:

• Enter must arrive as CSI 13 u or \r is ignored at the input state machine level
• Bracketed paste wraps injected text as \e[200~...\e[201~ — trailing Enter is consumed inside the paste block, never
  submits
• WM_CHAR to embedded WT bypasses its XAML input handler that would produce Kitty sequences

Ask Reporter (diagnostic)

1. Which terminal? Command Prompt or Windows Terminal (Settings menu)?
2. Does npm install -g @anthropic-ai/claude-code@2.1.115 fix it?
3. Does switching extension to Command Prompt mode fix it? (conhost doesn't advertise Kitty support)

Fix Options for Extension

Option A — env var injection in launch command (Terminal.cs command builder):

cmd.exe /k chcp 65001 >nul && set TERM=dumb && set CLAUDE_CODE_DISABLE_KITTY_KEYBOARD=1 && cd /d "{dir}" && ... && claude

Test which env vars actually gate Kitty init in current Claude Code (the JetBrains issue says
CLAUDE_NO_KITTY_KEYBOARD=1/TERM=xterm didn't work as of 2.1.107, but worth re-testing).

Option B — force Command Prompt for Claude Code providers until upstream fix lands. Disable WT selection when
AiProvider.ClaudeCode / ClaudeCodeWSL is active.

Option C — send bracketed-paste-aware Enter: after PasteViaCtrlShiftVAsync, inject \e[201~\r sequence so Enter arrives
outside the paste block. Fragile, terminal-specific.

Option D — file upstream issue referencing #48212/#50531 asking for CLAUDE_FORCE_LEGACY_INPUT or similar kill-switch.
Most durable fix.

Recommend Option A + D in parallel. Option B is the safest immediate mitigation.

✻ Baked for 3m 38s

[neil-gh]

Changing the extension's terminal type to Windows Terminal fixed it 🤦‍♂️.

Solution: Code Agent Selection button > Set Terminal Type... > Windows Terminal

I can now also paste directly into the extension terminal below the prompt with Ctrl+V, Ctrl+Shift+V, and Shift+Ins. Right-click still will not paste (which is consistent with regular PowerShell and CMD behavior for me, outside of Visual Studio and with an active Claude Code session).

All issues resolved. Thanks for your help.