[BUG] VS Code extension - ignore current file directive reverted
Resolved 💬 2 comments Opened Jan 12, 2026 by cryptomius Closed Feb 27, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Using the Claude Code for VS Code UI :
- start a new chat
- disable current file from being passed to chat
- submit first message
- current file is re-enabled as being sent for the second message (SHOULD NOT BE RE-ENABLED WITHOUT USER ACTION)
- once current file is specified to be ignored (again) it stays ignored (correct behaviour).
This bug seems to have been introduced in the last week or so.
What Should Happen?
- start a new chat
- disable current file from being passed to chat
- submit first message
- current file REMAINS disabled (EXPECTED BEHAVIOUR)
- subsequent messages sent, current file retains disabled / enabled state as directed by user
Error Messages/Logs
Steps to Reproduce
Using the Claude Code for VS Code UI :
- start a new chat
- disable current file from being passed to chat
- submit first message
- current file is re-enabled as being sent for the second message (SHOULD NOT BE RE-ENABLED WITHOUT USER ACTION)
- once current file is specified to be ignored (again) it stays ignored (correct behaviour).
This bug seems to have been introduced in the last week or so.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.0.75 (estimated)
Claude Code Version
2.1.5 https://marketplace.windsurf.com/extension/Anthropic/claude-code
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
WSL (Windows Subsystem for Linux)
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗