I’m running Cursor in agent mode (interactive coding agent). The orchestration workflow expects slash commands like `/test-domain`, `/test-application`, `/test-api`, and `/test-persistence`, but when the agent attempts to run them they are not available as executables (shell reports `no such file or directory`). This blocks automated test generation and coverage analysis workflows.
Reproduction steps
1. Start Cursor in agent mode in a repo that uses these slash commands in its test orchestration spec.
2. Allow the agent to execute the workflow.
3. Observe the agent try to run `./test-domain` (custom slash command).
4. Shell returns exit code 127 (`no such file or directory`), so the workflow fails immediately.
Expected behavior
Cursor slash commands referenced in the project should be exposed in agent mode (e.g., as scripts or accessible commands) so the agent can invoke them like in the normal UI.
Actual behavior
The commands are unavailable, causing the agent’s orchestration to fail.
Impact
Automated test coverage workflows relying on slash commands can’t run in agent mode.
