[BUG] Missing agents at start of cli, due to using Glob on .Claude/Agents folder starting with a dot

Resolved 💬 1 comment Opened May 26, 2026 by ArcoW2 Closed Jun 26, 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?

When a glob pattern contains a path segment that starts with a dot — such as .claude/agents/*.md — the Glob tool returns zero results and no warning, even when matching files exist at that exact path.

Actual behaviour: Zero results. No error or warning indicating that dotfolders were skipped.

Impact:
Agents that rely on Glob to discover files in .claude/ silently operate on an incomplete view of the workspace. Failures cascade: wrong assumptions get made and acted on.

What Should Happen?

Files at the explicitly named path .claude/agents/*.md are returned. An explicit dot-segment in a pattern is not a wildcard — it should not be subject to the Unix "skip hidden files" convention.

Error Messages/Logs

Steps to Reproduce

  1. Create files at .claude/agents/archie.md (and others) in a project root.
  2. Call Glob with pattern .claude/agents/*.md and the project root as the path.
  3. Result: empty — no files returned, no error.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.139

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Workaround:
Use Read with an explicit absolute path, or PowerShell/Bash with dir /a or ls -la.
For now I ordered the main claude.md to not use Glob for dot-related folder search.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗