[BUG] Persistent File Reference in Claude Code CLI

Resolved 💬 2 comments Opened Jan 27, 2026 by genwebdevelopment Closed Jan 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?

File references persist even after clearing conversation
No way to remove them, only hide

<img width="476" height="150" alt="Image" src="https://github.com/user-attachments/assets/215f26ea-f6b3-4eea-ae01-5c900fecf6d3" />

What Should Happen?

Expected: ability to fully clear file context

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

Open a project in VS Code that contains a package.json file
Open the Claude Code extension panel
Reference a file using @package.json or by dragging a file into the prompt while holding Shift
Send a message that uses that file reference
Complete the conversation or use /clear to clear the conversation
Observe that the file reference (package.json) still appears in the input bar footer
Attempt to start a new conversation using "Open in New Tab" or "Open in New Window" from Command Palette
Observe that the file reference still persists

Expected Behavior:

Clearing a conversation (/clear) should remove all file references from the input bar
Starting a new conversation should provide a clean slate with no file references
There should be an X button or similar control to manually remove file references from context

Actual Behavior:

File reference remains pinned in the input bar footer
Only option available is to "hide" the reference, not remove it
Reference persists across new conversations and cleared sessions
No X button or removal option exists

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.19

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗