# Browser Element Selection - Bug

**URL:** <https://forum.cursor.com/t/browser-element-selection-bug/174471>\
**Category:** Bug Reports\
**Tags:** browser, chat\
**Created:** [October 12, 2026, 7:05pm UTC](https://forum.cursor.com/t/browser-element-selection-bug/174471 "2026-10-12T19:05:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sebastien\_Therien](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@Sebastien\_Therien](https://forum.cursor.com/u/Sebastien_Therien)\
**Post date:** [October 12, 2026, 7:05pm UTC](https://forum.cursor.com/t/browser-element-selection-bug/174471/1 "2026-10-12T19:05:37Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Since the new IDE version. The selection of Elements in the browser, which injects them into the chat still works. But now copying them from a chat to another, turns them into raw HTML, instead of their “tag” approach that was perfectly fine. Now my agent is tripping and fails to properly retrieve the exact/specific element i was targetting.

### Steps to Reproduce

Copy a selected Element tag from a chat to another. (Text input)

### Expected Behavior

The tag copies perfectly as in the initial chat input field in which it was injected.

### Screenshots / Screen Recordings

 ![Screenshot 2026-10-12 150237.png](https://us1.discourse-cdn.com/cursor1/original/3X/f/2/f2e43327cbe7634366ffe0d296164a109e35edb7.png)

### Operating System

Windows 10/11

### Version Information

3.24.12 (user setup)

### For AI issues: which model did you use?

Any

### Additional Information

Was perfectly fine before.

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [October 12, 2026, 7:46pm UTC](https://forum.cursor.com/t/browser-element-selection-bug/174471/5 "2026-10-12T19:46:41Z")

</div>

Hey, thanks for the report and screenshot. I can see the difference between the chips in the sent message at the top and the expanded DOM path/HTML that gets pasted into the composer.

This is a known issue we’re already tracking. In the in-editor chat, copying from an already sent message only carries over plain text, so element tags get expanded into the full DOM path and HTML when pasted into another chat. This isn’t related to your setup.

Current workarounds:

1. Copy the tags from the chat input before sending the message. When copying between input fields, the tags stay as tags.
2. Copy and paste in the Agents Window top button in the chat panel. There, tags copied from new chats stay as tags.
3. Or just run Select Element again in the new chat to add the element directly.

Can you confirm whether you copied it from an already sent message and not from the input field? That’ll help us match it exactly to the issue we’re tracking. There’s no timeline yet, but I’ll post here when there’s an update.

---

<div class="post-metadata">

**Author:** ![Sebastien\_Therien](https://avatars.discourse-cdn.com/v4/letter/s/90ced4/32.png) [@Sebastien\_Therien](https://forum.cursor.com/u/Sebastien_Therien)\
**Post date:** [October 12, 2026, 10:06pm UTC](https://forum.cursor.com/t/browser-element-selection-bug/174471/7 "2026-10-12T22:06:58Z")

</div>

Thanks for the clarification!

I can confirm that the issue occurs when copying element references from an already-sent message, regardless of whether they’re pasted into an existing conversation or a newly created Chat/Agent session.

As an additional suggestion, it might be worth considering having **Select Element** always insert the reference at the current caret position in the active chat composer, rather than depending on which message or context was previously targeted. I believe this would make the workflow more predictable and intuitive, particularly when working across multiple conversations.

Of course, that’s more of a usability preference than a requirement for resolving the underlying issue.

Thanks again for the quick response and for tracking this!

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [October 31, 2026, 6:56am UTC](https://forum.cursor.com/t/browser-element-selection-bug/174471/8 "2026-10-31T06:56:43Z")

</div>

Thanks for checking. That means this is the exact issue we’re tracking. I’ve added your details too, including that it happens when pasting into both an existing chat and a new chat. For now, it’s best to copy the tags from the input field before sending, or add the item again with Select Element in a new chat.

About inserting at the caret position, there’s already a feature request for that. Here are similar threads:

- [Browser “Select Element” insert doesn't put element at cursor position](https://forum.cursor.com/t/browser-select-element-insert-doesnt-put-element-at-cursor-position/174067)
- [Insert Browser Tab element selection at cursor in Composer (not always at end)](https://forum.cursor.com/t/insert-browser-tab-element-selection-at-cursor-in-composer-not-always-at-end/167268)

Please leave a like there or describe your multi-chat use case. That’ll help show how much demand there is.

I’ll reply here when there’s an update on the copying issue.
