when i create a command in a nested .cursor folder these are not getting read by cursor IDE thus are not showing up in the chat window or cursor settings, whereas when i create rules these show up in both chat context area and even in the cursor settings
Steps to Reproduce
create a command in a nested folder in .cursor e.g. you are in root which is “TODO_APP” then in nested folder say “TODO_APP/acceptance_tests/.cursor/commands” you create a new command “create-bdd.md” this will not show up in cursor settings rules and commands section and won’t show up in chat window too
Expected Behavior
nested commands should show up in chat window
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
but the problem is some devs open in root some just open at acceptance-tests folder
so if i move the rules to root level then the devs that are opening acceptance tests won’t be able to see the commands
if we can have rules being read from nested folders what is preventing us from reading commands from nested folder?
feels like its a classic its not a bug its a feature…… just kidding
also i noticed these nested commands are eaisly getting read when i open my project as a workspace but i cannot use worktrees in workspace
i know that is an inherent limitation with vscode workspaces → but workspaces from single git repo should be able to support worktrees → i will start a different thread on this though
back to main point so nested commands are working in workspaces i think because workspaces make all nested projects move to root level → i am guessing it correct me if i am wrong please
