Can I have few '.commands' folders in one repo?

Support Help
1

Hi!
I can’t make a command to be triggered in sub folders. e.g under project_a or project_c
Our repo structure looks like this:
.
├── .cursor/
│ ├── .rules
│ └── .commands
├── project_a/
│ └── .cursor/
│ ├── .rules
│ └── .commands
├── project_b/
├── project_c/
│ ├── .cursor/
│ │ ├── .rules
│ │ └── .commands
│ ├── sub_dir_a/
│ └── sub_dir_b/
└── project_d/

Commands from nested folders are not getting read
2

Hey! Unfortunately, commands are currently supported only in three places:

  1. .cursor/commands at the project root
  2. ~/.cursor/commands in your home directory
  3. The command panel for team commands

Nested .cursor/commands in subfolders (like your project_a and project_c) aren’t supported.

Workaround: Put all commands in the root .cursor/commands and use descriptive file names to distinguish by project, for example:

  • project-a-command.md
  • project-c-command.md

Alternative: If you need contextual info for different subprojects, use .cursor/rules or AGENTS.md - they do support nested directories: Rules | Cursor Docs

1 Like