Allow sending Element Screenshot context to claude.ai web chat

Resolved 💬 1 comment Opened Jun 5, 2026 by StaanB Closed Jul 11, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Feature Request

<img width="378" height="144" alt="Image" src="https://github.com/user-attachments/assets/370b95e7-771c-4cc3-84ed-31bcc0ce7824" />

Summary

Currently, the "Element Screenshot" context capture in the VS Code extension
always sends the captured element to the extension's built-in chat panel.
There's no way to redirect this context to the claude.ai web chat.

Motivation

Some users prefer working in the claude.ai web interface for certain tasks
(e.g., design feedback, UI review) while keeping VS Code open for development.
The Element Screenshot feature is only useful if you're already working in the
extension's chat panel.

Proposed Solution

Proposed Solution

Add a configuration option (e.g., in VS Code settings or .claude/settings.json)
to choose the destination for captured context:

  • extension (current default) — sends to the extension's chat panel
  • clipboard — copies the screenshot to clipboard so it can be pasted anywhere

Alternatively, a "Copy to clipboard" button alongside the existing "Send to chat"
behavior would also solve this.

Current Workaround

Manually taking a screenshot and uploading it to claude.ai.

Environment

  • VS Code Version: 1.123.0
  • VS Code extension (Claude Code): 2.1.165
  • OS: Ubuntu 24.04.4 LTS

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Developer tools/SDK

Use Case Example

Use Case

Actor: Developer working with a running web app in VS Code

Goal: Share a captured UI element with claude.ai for design/UX feedback

<img width="222" height="42" alt="Image" src="https://github.com/user-attachments/assets/2dd39b71-6331-4e39-8fa4-a5f572b411d8" />

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗