[BUG] Additional .claude dir prevents commands from being discovered

Resolved 💬 7 comments Opened May 26, 2025 by tino Closed Jan 4, 2026

Environment

  • Platform (select one): doesn't matter
  • Claude CLI version: 1.0.3 (Claude Code)
  • Operating System: macOS
  • Terminal: iTerm2

Bug Description

Ah .claude directory prevents commands created higher up from being discovered. Quite annoying as if you start claude in a subdir, it will create a .claude/settings.local.json itself...

Steps to Reproduce

mkdir claude-bug
cd claude-bug
mkdir -p {.claude/commands,inner/.claude}
echo 'say hi' > .claude/commands/say_hi.md
claude  # Observe that `/proj` will list the command as autocomplete
cd inner
claude  # Observe that `/proj` will show nothing.

Expected Behavior

Commands should be discovered up, as is with CLAUDE.md files. Or at least if no commands folder is present in .claude the search upwards should continue.

Actual Behavior

See above

View original on GitHub ↗

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