Namespaced commands in subdirectories with colon syntax not working
Resolved 💬 3 comments Opened Jan 21, 2026 by glittercowboy Closed Jan 25, 2026
Description
Commands placed in subdirectories under ~/.claude/commands/ with colon-based naming (e.g., name: gsd:help) are not being recognized or executed properly in recent Claude Code versions.
Expected Behavior
According to the documentation, commands organized in subdirectories should support namespacing:
- Commands in
~/.claude/commands/gsd/should be accessible with namespace notation - Commands with
name: gsd:helpin frontmatter should be executable as/gsd:help
Actual Behavior
- Commands with colon syntax in subdirectories (e.g.,
/gsd:help) timeout when invoked - The commands are not appearing in
/helpoutput - Commands exist in
~/.claude/commands/gsd/directory with proper frontmatter but are inaccessible
Reproduction Steps
- Create directory
~/.claude/commands/gsd/ - Add command file
help.mdwith frontmatter:
---
name: gsd:help
description: Show available GSD commands and usage guide
---
- Try to execute
/gsd:help- command times out - Check
/helpoutput - gsd commands not listed
Environment
- Claude Code version: Latest as of January 21, 2025
- Platform: macOS Darwin 24.6.0
- Directory structure:
~/.claude/commands/gsd/contains 29 command files- Each file has frontmatter with
name: gsd:<command-name>format
Additional Context
This appears to be a regression as the documentation still shows support for namespaced directory structures. The same commands worked previously with the /gsd:command-name syntax.
Possible Solutions
- Fix the subdirectory namespacing to recognize colon syntax in frontmatter names
- Or clarify if the naming convention has changed and update documentation accordingly
Impact
This breaks existing command organization patterns for users who have structured their commands in logical namespaces/subdirectories.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗