Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] VSCode extension cannot access workspace files ("No files found") – not related to #8451 [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46278•Fetched 2026-04-11 06:24:31
View on GitHub
Comments
3
Participants
2
Timeline
8
Reactions
2
Author
EversonSoucekEversonSoucek
Participants
EversonSoucekEversonSoucekgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×3mentioned ×1

Error Message

Error Messages/Logs

Code Example

No files found
RAW_BUFFERClick to expand / collapse

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?

The VSCode extension cannot access any files or folders in the current workspace.

@file does not work The extension returns: "No files found" No files from the project can be referenced or attached

Important clarification (not a duplicate)

This issue was previously closed as a duplicate of #8451, but the behavior is fundamentally different.

#8451 describes context synchronization issues: Missing <ide_selection> Stale <ide_opened_file> Context is still partially available but inconsistent This issue describes a complete workspace access failure: No files are accessible @file does not resolve anything The system reports "No files found"

These affect different layers:

#8451 → IDE context synchronization This issue → Workspace resolution / indexing failure

What Should Happen?

@file should resolve and attach files from the workspace

Error Messages/Logs

No files found

Steps to Reproduce

Steps to Reproduce Open a project in VSCode Reload extensions Run /init Try to reference any file using @

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.100

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

This issue appears to be a regression in 2.x versions.

There are reports in #8451 where context is inconsistent but still partially working. In this case, there is no access at all, which suggests a deeper failure in workspace detection or indexing.

extent analysis

TL;DR

The issue can be mitigated by investigating the workspace resolution and indexing functionality in the VSCode extension, potentially involving a fix in the extension's configuration or code.

Guidance

  • Verify that the workspace is properly configured and that the extension has the necessary permissions to access files and folders.
  • Check the extension's documentation for any specific settings or configurations that may be required for workspace resolution and indexing.
  • Investigate the differences in behavior between the current version (2.1.100) and the previous version where the issue was not present, to identify potential regression causes.
  • Consider testing the extension with a minimal workspace setup to isolate the issue and determine if it's related to a specific project or file structure.

Example

No specific code snippet can be provided without further information on the extension's implementation details.

Notes

The issue appears to be a regression in the 2.x versions of the Claude Code extension, and resolving it may require changes to the extension's code or configuration. The fact that the issue is not present in previous versions suggests that a comparison of the changes between versions may help identify the root cause.

Recommendation

Apply workaround: Given the regression nature of the issue, it may be necessary to apply a temporary workaround, such as using a previous version of the extension or modifying the workspace configuration, until a fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#file not found#serialization error#model compatibility#GPU setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING