Copy to Chat button fails in the parallel agent mode (worktree)

[GitandGeek]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When working in the parallel agent mode (worktree), select a code block or some logs in the terminal and then click the copy to chat button wouldn’t copy the select parts to the current chat window but to the first chat window that I start working on.

Steps to Reproduce

1. Start the parallel agent mode to run three agents to generate code simultaneously
2. Work on the code in the Composer 1 chat first and then proceed to the GPT 5.1 Codex High chat
3. Select cod blocks in this chat and try to copy them to the current chat using the Copy to Chat button
4. Nothing is pasted in the current chat but found in the Composer 1 chat as shown in the image.

Expected Behavior

Code blocks and terminal logs should be copied to the current chat I’m working on.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77 (Universal)
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

For AI issues: which model did you use?

Composer 1
GPT 5.1 Codex High
Claude Sonnet 4.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. This looks like a tab targeting issue in the worktree, similar to other worktree bugs we’re tracking (for example, around path handling and UI button state).

I’ll pass this to the engineering team for investigation. Your reproduction steps and screenshot are very helpful.

As a temporary workaround, you can manually copy and paste the content into the correct chat tab instead of using the “Copy to Chat” button.

Let me know if you notice any additional patterns - when it breaks versus when it works correctly.

[GitandGeek]

Thanks for giving your attention to this issue. Another worktree problem I mentioned in a previous report remains unresolved: if I delete a file or the agent delete it in the worktree mode, I won’t be able to apply the worktree to the current branch using the apply or reapply button. I have to ask the agent to execute several git commands to recover the deleted file and make the worktree work again. Hope the Cursor team can spend time investigating this issue as well.