When including multiple directories, @'ing a directory seems to pull in directories that match in all included directories

[timothyfroehlich]

What happened?

This prompt: Take a good look at @scripts/ and @buildLogic/dependency-analysis/ resulted in Gemini automatically loading 1115 files into context

The majority of these files were built outputs. It reduced my context from 100% to 66%.

What did you expect to happen?

#1: @'ing a directory would give Gemini the list of files in that directory, instead of filling it's context with everything it could find.
#2: @'ing a directory would either only load the files from the main directory, or there would be a mechanism to specify which directory the files should be looked for in.

Client information

• CLI Version: 0.7.0-nightly.20250918.2722473a
• Git Commit: 2722473
• Session ID: ca84ba0a-7dd2-4cd2-9bb5-c2437f9b5f7e
• Operating System: darwin v24.7.0
• Sandbox Environment: no sandbox
• Model Version: auto
• Memory Usage: 595.7 MB

Login information

API Key

Anything else we need to know?

Settings.json snippet:

    "includeDirectories": [
      "../../libs",
      "../../BugReport",
      "../../Calendar",
      "../../Dashcam",
      "../../Dialer",
      "../../DriverUI",
      "../../Media",
      "../../Messenger",
      "../../MultiDisplay",
      "../../Radio",
      "../../SensitiveAppLock",
      "../../tests",
      "../../../../../out/aaos-apps-gradle-build"
    ],
    "loadFromIncludeDirectories": true
  }
}

[gemini-cli]

The user is reporting a bug where mentioning a directory with @ incorrectly pulls in files from all configured 'includeDirectories' that have a matching name, rather than just the specified one. This is a core file resolution issue that significantly degrades a key feature, making it a high priority.

[agmsb]

Thanks for filing, we'll investigate this.