Agent windows "Add to Chat" not working

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am using the latest version of Cursor on Windows. While in the new Agent Mode, I noticed that the “Add to Chat” button is missing from the terminal interface. This prevents me from easily adding terminal output or selected text as context to the agent.

Steps to Reproduce

Not sure.

Operating System

Windows 10/11

Version Information

Version: 3.0.13 (user setup)
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report.

In Glass layout, the Add to Chat button in the terminal is context-based, so it’s not always visible. It shows up in two cases:

  1. You select text in the terminal, then the button appears next to the selection.
  2. You hover over a command output block, then the button appears on that block. This needs working shell integration.

If neither works, it’s most likely a shell integration issue on Windows. A couple questions:

  • Which shell are you using? PowerShell, cmd, Git Bash, WSL?
  • Can you share a screenshot of the terminal when you select text? Does the button show up?

Also try the shortcut Ctrl+Shift+L with text selected in the terminal. It should add the selection to chat even if the button isn’t showing.


I’m using PowerShell with the oh-my-posh plugin installed. In both scenarios you mentioned, the button does not appear. Additionally, using Ctrl+Shift+L fails to add the selected content to the chat.

Quick shortcut fix: try Ctrl+L or Ctrl+I with text selected in the terminal, not Ctrl+Shift+L. Those should work.

The bug with the Add to Chat button is confirmed and the team is aware. For now, please use the shortcuts as a workaround. Let me know if it worked.

Ctrl+L and Ctrl+I are working perfectly. Thanks!


Seeing the same issue (on Mac). The shortcut key for Mac seems to be cmd-l but that is not the same as the broken feature. Hope it gets fixed soon.

Hey @sravasti, thanks for flagging this. A separate Mac case is helpful since the original thread was about Windows plus PowerShell with oh-my-posh.

A couple questions to narrow it down:

  • Cursor version Cursor > About?
  • Which shell zsh bash fish, and do you use a custom prompt like starship, oh-my-zsh, powerlevel10k, etc?
  • When exactly should the button show up but doesn’t, when selecting text, when hovering over the command block, or both?

How it works: in Glass the button is context-based. It shows up either when you select text, or when you hover a command output block. The second one needs working shell integration. Custom prompts sometimes break command block detection, and then the hover button won’t show.

We’re tracking the issue, no ETA for a fix yet. For now a workaround is Cmd+L or Cmd+I with text selected. I know it’s not the same as having the button, but it should unblock you.

Version: 3.1.15
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z

zsh and no custom prompt

Both (and it used to work just fine earlier)

Other than the new drop(s), the background is now white which I think is the default as opposed to the earlier dark theme.

@sravasti, thanks for the details. Vanilla zsh with no custom prompt is a helpful signal, so it’s probably not tied to oh-my-posh or oh-my-zsh.

One quick question: if you select some text in the terminal and press Cmd+L (or Cmd+I), does it work, or is it also a no-op? This will help us figure out if it’s just the keybinding that broke, or the whole add-to-chat chain from the terminal.

We’re tracking this issue on our side, but I can’t share an ETA for a fix yet. Once I have an update, I’ll reply in the thread.

About the white background, that’s most likely a separate issue. It might have switched back to the default theme after an update. Can you check and switch it back to dark? If it’s set to dark but still renders as light, please start a separate thread and we’ll take a look.

That is the thing. Cmd-L worked for a bit but not any more. I mentioned the change in the default background color in case that had anything to do with the visibility of the button. There are several other differences (regressions in my view) between the Agent window and the Editor window e.g. I do not see notification when an agent operation finishes or is pending a user action. Of course, none of this is gating like the memory issue (another thread) that made me switch back to the Editor window.

Hey @sravasti, thanks for the update. Cmd+L no longer working on a vanilla zsh is a useful signal.

A couple quick questions to narrow it down:

  • Is your terminal local or Remote SSH? For SSH we have a separate case and the behavior is a bit different.
  • What Cursor version are you on right now? If you’re still on 3.1.15, please update. Recent builds had changes around add-to-chat in Glass.
  • Can you share the Request ID from your latest attempt top right of the chat > Copy Request ID? It’ll help us see what’s reaching the backend when it no-ops.

We’re tracking the issue on our side, but I can’t give an ETA for a fix yet. I’ll post an update in the thread when I have one.

The missing agent finished / awaiting input badges in the Agents window and the white background look like separate regressions. Please file them as a separate report, or add them to this thread Notification badges that don't disappear if the symptoms match. Otherwise they’ll get lost in this add-to-chat thread.