Glob tool silently fails with absolute paths + wildcards

Description

The Glob tool silently returns "No files found" when using absolute paths combined with wildcards, even when matching files exist.

Steps to Reproduce

1. Have files in a directory, e.g., /Users/username/project/folder/file1.md, file2.md
2. Use Glob with absolute path + wildcard:

• Pattern: /Users/username/project/folder/*.md
• Result: "No files found" (silent failure)

1. Use relative pattern instead:

• Pattern: **/folder/*.md
• Result: Files found correctly ✓

Expected Behavior

Glob should either:

• Work with absolute paths + wildcards, OR
• Return an explicit error explaining the limitation

Actual Behavior

Returns "No files found" with no error or warning, making it appear the files don't exist.

Workaround

Use ls via Bash tool instead:

ls "/Users/username/project/folder/"

Or use relative patterns starting with **.

Impact

This is particularly problematic for startup routines that need to check specific directories (like context/reprises/ for session continuity files). The silent failure causes loss of context between sessions.

Environment

• Claude Code CLI
• macOS (Darwin 24.6.0)