Feedback: File/Folder Discovery Inefficiency in Local Filesystem Navigation

Resolved 💬 3 comments Opened Dec 29, 2025 by chashamm Closed Feb 14, 2026

Summary

Experiencing consistent difficulty with Claude Code's ability to locate files and folders in local filesystem, even when they exist in predictable locations within the current working directory structure.

Environment

  • Platform: Windows 11
  • Claude Code CLI

Issue Description

Over recent sessions, Claude Code has shown a pattern of:

  1. Inefficient search strategies - Using broad system-wide searches (e.g., searching C:\Users\...\Desktop) when the target is within the current working directory tree
  2. Missing obvious paths - Not checking subdirectories of the current working directory first
  3. Requiring explicit paths - User needs to manually provide full paths for folders that are direct children or nearby in the project structure

Example Scenario

  • Working directory: B:\m_Cpp
  • Target folder: B:\m_Cpp\Projects\pyprojects\SpiderScraper
  • Behavior: Searched Desktop on C: drive instead of checking B:\m_Cpp\Projects\

Expected Behavior

When asked to navigate to a folder:

  1. First check current directory and immediate subdirectories
  2. Use recursive search within the current project tree
  3. Only expand search scope if not found locally

Suggested Improvement

Implement a hierarchical search strategy:

  1. Current directory → 2. Child directories → 3. Sibling directories → 4. Parent directory tree → 5. Common locations (Desktop, Documents, etc.)

Impact

  • Slows down workflow
  • Requires user intervention with explicit paths
  • Creates friction in otherwise smooth interactions

---

Submitted via Claude Code on behalf of user

View original on GitHub ↗

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