[BUG] VSCode Extension no longer has file/selection context

[bdmayes-ps]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Title:
IDE selection context not being passed to Claude in VSCode extension

Description:
When selecting lines of code in the VSCode editor, the selection context is not being passed to Claude Code. Claude responds that it cannot see any ide_selection tags in the conversation context.

Actual Behavior:
Claude does not receive any IDE selection context and cannot see what lines are selected.

What Should Happen?

Claude should receive the selected code with ide_selection tags in the conversation context and be able to reference the selected lines.

Error Messages/Logs

Steps to Reproduce

• Open a file in VSCode
• Open the Claude code extension
  -Select specific lines of code
• Ask Claude "Can you see which lines I have selected?"
• Claude responds that no selection context is visible

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.0.15

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Environment:
OS: macOS (Darwin 24.5.0)
VSCode Version: 1.105.0
Claude Code Extension: v2.0.15
Architecture: arm64

Additional Context:

• Working in a git repository
• Opening a terminal, launching claude code and then typing /ide works correctly, and knows precisely which lines are selected.

[github-actions]

Found 1 possible duplicate issue:

1. [BUG] missing ide_selection and wrong ide_opened_file in VSCode extension #8451

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.